Bug 155546 - devel/libtool doesn't work properly if not using built in compiler
Summary: devel/libtool doesn't work properly if not using built in compiler
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: autotools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-14 00:50 UTC by Stephen Montgomery-Smith
Modified: 2015-08-06 08:32 UTC (History)
2 users (show)

See Also:

Attachments
file.diff (866 bytes, patch)
2011-03-14 00:50 UTC, Stephen Montgomery-Smith 		no flags Details | Diff
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 Stephen Montgomery-Smith 2011-03-14 00:50:06 UTC 
	

If you are using a compiler, like gcc45, in a port, then libtool doesn't always work properly.

Fix: Here is one suggestion.  It causes libtool to respect $CC and $CXX.  But you would have to do this for the other tools used for linking.

This will add a new file called patch-configure.
How-To-Repeat: Try to build the vis5d+ port.

You will get an error like this

multiple definition of `__i686.get_pc_thunk.bx
Comment 1 Martin Wilke freebsd_committer freebsd_triage 2011-03-14 16:48:19 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->ade

can u please take a look?
Comment 2 Ade Lovett freebsd_committer freebsd_triage 2011-10-10 12:16:11 UTC 
Responsible Changed
From-To: ade->autotools

Reassign appropriately.
Comment 3 Bryan Drewery 2012-05-05 01:49:26 UTC 
Thank you for this patch. It helped me.

This also fixes a situation when compiling ports with ccache [1] where
libtool thinks that ccache is the system compiler and proceeds to
conflict with other ports that are trying to use ccache, such as
security/libgpg-error

[1] http://forums.freebsd.org/showthread.php?t=3908

Regards,
Bryan Drewery
Comment 4 Bryan Drewery 2012-05-06 21:50:11 UTC 
I tested this patch further. It at least breaks compiling
print/freetype2 by causing the linking stage to use
"/usr/ports/print/freetype2/work/gnome-libtool --mode=compile cc ..."
instead of "cc ..." directly without this patch applied to libtool.

Regards,
Bryan Drewery
Comment 5 Bryan Drewery freebsd_committer freebsd_triage 2013-04-15 18:29:06 UTC 
science/libctl is another case of this.
Comment 7 Carlo Strub freebsd_committer freebsd_triage 2014-09-14 10:21:50 UTC 
Is this PR still relevant?
Comment 8 Tijl Coosemans freebsd_committer freebsd_triage 2015-08-06 08:32:29 UTC 
We used to build ports with /usr/local/bin/libtool which uses the compiler/linker used to build devel/libtool.  Now we build ports with libtool generated from their configure script so the correct compiler/linker is used.