Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 829890 - dev-lang/spidermonkey-78.15.0 build fails with 'collect2: error: ld returned 1 exit status' on POWERPC64 during build
Summary: dev-lang/spidermonkey-78.15.0 build fails with 'collect2: error: ld returned ...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: PPC64 Linux
: Normal normal
Assignee: Mozilla Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-24 02:00 UTC by Peter Easton
Modified: 2021-12-24 02:39 UTC (History)
1 user (show)

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


Attachments
Compressed build log of spidermonkey-78.15.0 (build.log.xz,29.59 KB, application/x-xz)
2021-12-24 02:00 UTC, Peter Easton
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Easton 2021-12-24 02:00:50 UTC
Created attachment 760162 [details]
Compressed build log of spidermonkey-78.15.0

Hello everybody,

I found this error while rebuilding Spidermonkey 78.15.0 during a routine upgrade. on POWERPC64 (Little Endian). The build gets off to a good start but then hits "collect2: error: ld returned 1 exit status" and halts.

I'm attaching the full build.log file.

Thank you very much,
Peter.
Comment 1 Georgy Yakovlev archtester gentoo-dev 2021-12-24 02:21:42 UTC
as discussed on IRC, user-set flags most likely a problem

rebuild with
__COMMON_FLAGS="-O2 -mcpu=power9 -pipe"                                                                                                     
CFLAGS="${__COMMON_FLAGS}"                                                                                                                                                                                                              
CXXFLAGS="${__COMMON_FLAGS}"

and if it still fails - reopen the bug.
Comment 2 Peter Easton 2021-12-24 02:39:31 UTC
Whew! Thank you so much! It's fixed! 

Lesson learned! I'm making a note to myself to never try to apply strange compiler flags, no matter how cool they look if I don't know exactly what they'll do or what kind of hell they will play with the rest of the system. 

Thank you guys so much, I could have just made a terrible mistake.