Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 266314 - Failed to emerge dev-lang/fpc , make compiler_cycle failed!
Summary: Failed to emerge dev-lang/fpc , make compiler_cycle failed!
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-15 23:00 UTC by Jake Magee
Modified: 2009-04-18 16:22 UTC (History)
1 user (show)

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


Attachments
emerge info (info,4.04 KB, text/plain)
2009-04-16 15:15 UTC, Jake Magee
Details
emerge fpc (fpc,210 bytes, text/plain)
2009-04-16 15:16 UTC, Jake Magee
Details
build.log (build.log,1.89 KB, text/plain)
2009-04-16 15:16 UTC, Jake Magee
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jake Magee 2009-04-15 23:00:20 UTC
When trying to emerge hedgewars, dev-lang/fpc fails to emerge.  Both the stable 2.2.0 and testing 2.2.2-r1 fail the same way.

Reproducible: Always

Steps to Reproduce:
1. emerge fpc

Actual Results:  
>>> Emerging (1 of 2) dev-lang/fpc-2.2.2-r1
 * fpcbuild-2.2.2.tar.gz RMD160 SHA1 SHA256 size ;-) ...                 [ ok ]
 * fpc-2.2.2.i386-linux.tar RMD160 SHA1 SHA256 size ;-) ...              [ ok ]
 * checking ebuild checksums ;-) ...                                     [ ok ]
 * checking auxfile checksums ;-) ...                                    [ ok ]
 * checking miscfile checksums ;-) ...                                   [ ok ]
>>> Unpacking source...
>>> Unpacking fpcbuild-2.2.2.tar.gz to /var/tmp/portage/dev-lang/fpc-2.2.2-r1/wo
rk
>>> Unpacking fpc-2.2.2.i386-linux.tar to /var/tmp/portage/dev-lang/fpc-2.2.2-r1
/work
 * Applying fpc-2.2.2-unneeded-symbols.patch ...                          [ ok ]
 * Applying fpc-2.2.2-execstack.patch ...                                 [ ok ]
>>> Source unpacked in /var/tmp/portage/dev-lang/fpc-2.2.2-r1/work
>>> Compiling source in /var/tmp/portage/dev-lang/fpc-2.2.2-r1/work/fpcbuild-2.2
.2/fpcsrc ...
make -j2 -j1 PP=/var/tmp/portage/dev-lang/fpc-2.2.2-r1/work/lib/fpc/2.2.2/ppc386
 compiler_cycle 
ISE opendir(./packages): No such file or directory
        abs_path: (null)
        res_path: (null)
/usr/lib/libsandbox.so[0xb7f553ab]
/usr/lib/libsandbox.so[0xb7f553ec]
/usr/lib/libsandbox.so[0xb7f56b98]
/usr/lib/libsandbox.so(opendir+0x62)[0xb7f59602]
make[0x804c276]
make[0x804c372]
make[0x804cb01]
make[0x80503b0]
make[0x804fae5]
make[0x8051711]
/var/tmp/portage/dev-lang/fpc-2.2.2-r1/temp/environment: line 2181:  6076 Aborte
d                 emake -j1 PP="${pp}" compiler_cycle
 * 
 * ERROR: dev-lang/fpc-2.2.2-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2184:  Called die
 * The specific snippet of code:
 *       emake -j1 PP="${pp}" compiler_cycle || die "make compiler_cycle failed!
";
 *  The die message:
 *   make compiler_cycle failed!
 * 
 * If you need support, post the topmost build error, and the call stack if rele
vant.
 * A complete build log is located at '/var/tmp/portage/dev-lang/fpc-2.2.2-r1/te
mp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-lang/fpc-2.2.
2-r1/temp/environment'.
 * 

>>> Failed to emerge dev-lang/fpc-2.2.2-r1, Log file:

>>>  '/var/tmp/portage/dev-lang/fpc-2.2.2-r1/temp/build.log'

 * Messages for package dev-lang/fpc-2.2.2-r1:

 * 
 * ERROR: dev-lang/fpc-2.2.2-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2184:  Called die
 * The specific snippet of code:
 *       emake -j1 PP="${pp}" compiler_cycle || die "make compiler_cycle failed!
";
 *  The die message:
 *   make compiler_cycle failed!
 * 
 * If you need support, post the topmost build error, and the call stack if rele
vant.
 * A complete build log is located at '/var/tmp/portage/dev-lang/fpc-2.2.2-r1/te
mp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-lang/fpc-2.2.
2-r1/temp/environment'.
 * 


Expected Results:  
Completed the emerge fine.
Comment 1 David Sveningsson 2009-04-16 10:53:19 UTC
I cannot reproduce this on my machine. Can you attach "emerge --info", "emerge -pv dev-lang/fpc" and build.log?
Comment 2 Jake Magee 2009-04-16 15:15:41 UTC
Created attachment 188586 [details]
emerge info
Comment 3 Jake Magee 2009-04-16 15:16:12 UTC
Created attachment 188588 [details]
emerge fpc
Comment 4 Jake Magee 2009-04-16 15:16:49 UTC
Created attachment 188589 [details]
build.log
Comment 5 Paul Mulders 2009-04-16 15:31:12 UTC
emerge -1 sandbox should fix it
Comment 6 Jake Magee 2009-04-16 17:32:33 UTC
Thanks!

This fixed the issue for fpc 2.2.2-r1 (updating sandbox).  I assume it would also fix the issue for other versions of fpc.

Before closing the case, should the official fix be to update fpc dependencies?