Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 377191 - =app-office/libreoffice-3.3.3 does not build (amd64)
Summary: =app-office/libreoffice-3.3.3 does not build (amd64)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Office Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-31 18:07 UTC by David Carlos Manuelda
Modified: 2011-08-06 10:08 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Compile output with MAKEOPTS="-j3" (compressed) (app-office:libreoffice-3.3.3:20110731-160351.log.bz2,80.51 KB, application/octet-stream)
2011-07-31 18:10 UTC, David Carlos Manuelda
Details
Compile output with MAKEOPTS="-j1" (compressed) (app-office:libreoffice-3.3.3:20110731-175620.log.bz2,80.46 KB, application/octet-stream)
2011-07-31 18:11 UTC, David Carlos Manuelda
Details
emerge --info (emergeinfo.txt,14.39 KB, text/plain)
2011-08-02 14:35 UTC, David Carlos Manuelda
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Carlos Manuelda 2011-07-31 18:07:17 UTC
I'll attach the full build log with MAKEOPTS -j3 and MAKEOPTS -j1 just in case.

Reproducible: Always
Comment 1 David Carlos Manuelda 2011-07-31 18:10:21 UTC
Created attachment 281655 [details]
Compile output with MAKEOPTS="-j3" (compressed)
Comment 2 David Carlos Manuelda 2011-07-31 18:11:00 UTC
Created attachment 281657 [details]
Compile output with MAKEOPTS="-j1" (compressed)
Comment 3 Agostino Sarubbo gentoo-dev 2011-08-02 13:03:13 UTC
emerge --info is always appreciated
Comment 4 David Carlos Manuelda 2011-08-02 14:34:55 UTC
I'm sorry, completelly forgot :D
Comment 5 David Carlos Manuelda 2011-08-02 14:35:43 UTC
Created attachment 281839 [details]
emerge --info
Comment 6 David Carlos Manuelda 2011-08-02 16:21:15 UTC
Is it possible to be caused by glibc 2.14? In that case, could you make this bug blocks glibc 2.14 one?
Comment 7 Tomáš Chvátal (RETIRED) gentoo-dev 2011-08-03 10:55:54 UTC
David if you are using glibc-2.14 could you test 3.4.2.3 which is currently masked?
Comment 8 David Carlos Manuelda 2011-08-03 19:51:53 UTC
Can't test since it fails with a patch:
* Applying libreoffice-32b-qt4-libdir.patch ...

 * Failed Patch: libreoffice-32b-qt4-libdir.patch !
 *  ( /usr/portage/app-office/libreoffice/files/libreoffice-32b-qt4-libdir.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/app-office/libreoffice-3.4.2.3/temp/libreoffice-32b-qt4-libdir.patch.out

 * ERROR: app-office/libreoffice-3.4.2.3 failed (prepare phase):
 *   Failed Patch: libreoffice-32b-qt4-libdir.patch!
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_prepare
 *   environment, line 8906:  Called base_src_prepare
 *   environment, line 1988:  Called epatch '/usr/portage/app-office/libreoffice/files/libreoffice-32b-qt4-libdir.patch'
 *   environment, line 3554:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 * 
 * If you need support, post the output of 'emerge --info =app-office/libreoffice-3.4.2.3',
 * the complete build log and the output of 'emerge -pqv =app-office/libreoffice-3.4.2.3'.
!!! When you file a bug report, please include the following information:
GENTOO_VM=icedtea6-bin  CLASSPATH="" JAVA_HOME="/opt/icedtea6-bin-1.10.3"
JAVACFLAGS="-source 1.5 -target 1.5" COMPILER=""
and of course, the output of emerge --info
 * The complete build log is located at '/var/log/portage/app-office:libreoffice-3.4.2.3:20110803-193817.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-office/libreoffice-3.4.2.3/temp/environment'.
 * S: '/var/tmp/portage/app-office/libreoffice-3.4.2.3/work/libreoffice-bootstrap-3.4.2.3'
Comment 9 Steffen Schaumburg 2011-08-05 01:21:53 UTC
Having the same problem with and without parallel build.
I have recently updated from a ~amd64/amd64 mixture to proper ~amd64 and gcc-4.6.1 and have remerged world twice.
I tried the new 3.4.2.3 as well, and though the patch applied I got another error. I'm just trying again to get the error message ;)
Comment 10 Steffen Schaumburg 2011-08-05 01:24:34 UTC
Seems I wasn't the first one with that either - my 3.4.2.3 failed with #376379
Comment 11 David Carlos Manuelda 2011-08-05 02:22:25 UTC
Finally I built 3.4.2.3 WITHOUT the last conflicting patch and glibc 2.14 and it builds (and runs) fine.
Comment 12 Tomáš Chvátal (RETIRED) gentoo-dev 2011-08-06 10:08:23 UTC
I am closing this bug as fixed by version 3.4.2.3 as per latest comment.
Thanks for all the testing.