After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 732319 - Use of /usr/bin/libtool results in mixing two different compilers
Use of /usr/bin/libtool results in mixing two different compilers
Status: RESOLVED OBSOLETE
Product: gexiv2
Classification: Other
Component: build
0.10.x
Other Linux
: Normal normal
: ---
Assigned To: Gexiv2 Maintainers
Gexiv2 Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-06-27 10:07 UTC by Michał Górny
Modified: 2014-10-28 21:31 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Build log (15.50 KB, text/x-log)
2014-06-27 10:07 UTC, Michał Górny 		Details

Description Michał Górny 2014-06-27 10:07:28 UTC 
Created attachment 279370 [details]
Build log

After upgrading my gcc (and updating value of CXX) I'm unable to upgrade gexiv2:

  libtool --mode=link --tag=CC x86_64-pc-linux-gnu-g++-4.8.3 [...]
  libtool: link: x86_64-pc-linux-gnu-gcc-4.8.2 -shared [...]
  /usr/bin/libtool: line 8979: x86_64-pc-linux-gnu-gcc-4.8.2: command not found

The issue is that installed libtool hardcodes some random compiler used at install time. The result is, CXX used during the build is not used but the old compiler which may no longer be available. And since you're using '--tag=CC' instead of '--tag=CXX', it tries to use the C compiler rather than C++.

As far as upstream is concerned, packages are not allowed to use that and should create their own 'local' libtool copies instead. I don't know if it's possible without using whole autotools bundle though.
Comment 1 Michał Górny 2014-10-28 21:31:11 UTC 
Oh, I just noticed that 0.10 uses autotools now and doesn't suffer this issue.