Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 647866 - dev-haskell/semigroups-0.18.2: error: unrecognized command line option ‘-nopie’; did you mean ‘-no-pie’
Summary: dev-haskell/semigroups-0.18.2: error: unrecognized command line option ‘-nopi...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo's Haskell Language team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-16 16:25 UTC by kballou
Modified: 2018-08-30 15:55 UTC (History)
0 users

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

Attachments
build.log (build.log,3.11 KB, text/x-log)
2018-02-16 16:25 UTC, kballou 		Details
emerge --info (file_647866.txt,7.62 KB, text/plain)
2018-02-16 16:25 UTC, kballou 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description kballou 2018-02-16 16:25:07 UTC 
Created attachment 519716 [details]
build.log

I'm currently unable to compile dev-haskell/semigroups-0.18.2, nor am I able to compile 0.18.4 from the gentoo-haskell overlay.

The error appears to be with the use of the `-nopie` option:

Linking setup ...
x86_64-pc-linux-gnu-gcc: error: unrecognized command line option ‘-nopie’; did you mean ‘-no-pie’?
`x86_64-pc-linux-gnu-gcc' failed in phase `C Compiler'. (Exit code: 1)
 * ERROR: dev-haskell/semigroups-0.18.2::gentoo failed (configure phase):
 *   compiling /var/tmp/portage/dev-haskell/semigroups-0.18.2/work/semigroups-0.18.2/Setup.lhs failed

It is possible this is related to https://bugs.gentoo.org/644004.
Comment 1 kballou 2018-02-16 16:25:43 UTC 
Created attachment 519718 [details]
emerge --info
Comment 2 kballou 2018-02-19 18:50:11 UTC 
This turns out to be a user error with a messed up dev-lang/ghc build.  Recompiling ghc with the new version of gcc 6.4.0-r1 (pie enabled) resolves the issue.
Comment 3 Philippe Chaintreuil 2018-08-30 15:55:22 UTC 
Thanks @kballou, I had the same issue with dev-haskell/base-compat-0.9.1, reinstalling ghc fixed it.