Summary: | app-shells/quoter: Please pass CC environment variable. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Yuta SATOH <nigoro.dev> |
Component: | Current packages | Assignee: | Michał Górny <mgorny> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | axs, martin, xmw |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | sample patch for quoter-2.0_p2.ebuild |
Description
Yuta SATOH
2016-11-05 08:07:33 UTC
Created attachment 452406 [details, diff]
sample patch for quoter-2.0_p2.ebuild
I am surprised to learn that CC is different than e.g. CFLAGS or LDFLAGS here, i.e., that the mere default of portage is not already doing the right thing for CC automatically, but that an eclass must might used. Thanks for the patch! (I already put it in the mv overlay). CFLAGS work automatically because it can be accessed via the environment - but CC is not automagically defined anywhere. tc-getCC determines CC based on CHOST, something that some build systems can do automatically. Can't cross-compile :
> cc -DAVOID_BUILTIN_EXPECT -DAVOID_ATTRIBUTE_NORETURN \
> -O2 -pipe -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=hard -Wl,-O1 \
> -Wl,--as-needed -o bin/quoter src/quoter.c
> gcc: error: unrecognized command line option '-mfpu=vfpv3-d16'
> gcc: error: unrecognized command line option '-mfloat-abi=hard'
> gcc: error: unrecognized command line option '-mfpu=vfpv3-d16'
> gcc: error: unrecognized command line option '-mfloat-abi=hard'
> gcc: error: unrecognized command line option '-mfpu=vfpv3-d16'
> gcc: error: unrecognized command line option '-mfloat-abi=hard'
> gcc: error: unrecognized command line option '-mfpu=vfpv3-d16'
> gcc: error: unrecognized command line option '-mfloat-abi=hard'
> make: *** [Makefile:10: bin/quoter] Error 1
> * ERROR: app-shells/quoter-3.0_p2-r1::gentoo failed (compile phase):
> * emake failed
|