Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 474534 - app-text/liblangtag : does not respect CC
Summary: app-text/liblangtag : does not respect CC
Status: RESOLVED DUPLICATE of bug 463846
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal QA (vote)
Assignee: Gentoo Office Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: tc-directly
  Show dependency tree
 
Reported: 2013-06-23 21:15 UTC by Agostino Sarubbo
Modified: 2013-06-24 13:05 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2013-06-23 21:15:45 UTC
You receive this bug because this package does not respect my system's CC (x86_64-pc-linux-gnu-gcc) and calls directly /usr/bin/gcc(or similar)
The possible solutions to fix this issue are:
1)Fix the buildsystem, if you can;
2)inherit toolchain-funcs and use tc-export CC
3)inherit toolchain-funcs and use emake CC="$(tc-getCC)"


From the build log:

libtool: link: gcc -o /var/tmp/portage/app-text/liblangtag-0.5.1/work/liblangtag-0.5.1_build/liblangtag-gobject/tmp-introspect_3XGJF/.libs/LangTag-0.5 -march=native -O2 -g0 
-pipe -Wall -Wmissing-prototypes /var/tmp/portage/app-text/liblangtag-0.5.1/work/liblangtag-0.5.1_build/liblangtag-gobject/tmp-introspect_3XGJF/LangTag-0.5.o 
-Wl,--export-dynamic -pthread -Wl,--export-dynamic  -L. ./.libs/liblangtag-gobject.so 
/var/tmp/portage/app-text/liblangtag-0.5.1/work/liblangtag-0.5.1_build/liblangtag/.libs/liblangtag.so -ldl -lxml2 -lgio-2.0 -lgobject-2.0 -lgthread-2.0 -lgmodule-2.0 -lrt 
-lglib-2.0 -pthread
Comment 1 Tomáš Chvátal (RETIRED) gentoo-dev 2013-06-24 08:36:22 UTC
Its taking only on introspection, no clue how that thing works. Lets ask gnome.
Comment 2 Alexandre Rostovtsev (RETIRED) gentoo-dev 2013-06-24 13:05:14 UTC

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