Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 642798 - x11-libs/motif-2.3.7 fail compile segmentation fault
Summary: x11-libs/motif-2.3.7 fail compile segmentation fault
Status: RESOLVED DUPLICATE of bug 583842
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Ulrich Müller
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-31 05:54 UTC by Geoff Madden
Modified: 2018-03-21 18:46 UTC (History)
3 users (show)

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


Attachments
build log (build_log.tar.gz,20.97 KB, application/x-tar)
2017-12-31 05:54 UTC, Geoff Madden
Details
emerge info profile17.1 motif-3.2.7 (emerg.inf,5.39 KB, text/plain)
2017-12-31 05:57 UTC, Geoff Madden
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Geoff Madden 2017-12-31 05:54:48 UTC
Created attachment 512140 [details]
build log

compiling tools dir fails with a segmentation fault
Comment 1 Geoff Madden 2017-12-31 05:57:41 UTC
Created attachment 512142 [details]
emerge info profile17.1 motif-3.2.7
Comment 2 Thomas Petersen 2018-01-03 12:32:15 UTC
I have been battling a bit with this problem too.
Now after finally looking into it I realize that wmluiltok is linked with libfl.a (flex) and I have "forgotten" to recompile flex after switching to profile 17.0.

Did you "emerge -e @world" after switching to the 17.0 profile? I was lazy and skipped that part...

Re-emerge flex "emerge -1 flex" and motif should compile again.
Comment 3 Dirk Olmes 2018-01-03 14:02:04 UTC
(In reply to Thomas Petersen from comment #2)
> Did you "emerge -e @world" after switching to the 17.0 profile? I was lazy
> and skipped that part...
> 
> Re-emerge flex "emerge -1 flex" and motif should compile again.

Thanks for digging into that, Thomas. Re-merging flex fixed it for me.
Comment 4 Ulrich Müller gentoo-dev 2018-01-03 16:44:00 UTC

*** This bug has been marked as a duplicate of bug 583842 ***