Summary: | devel/libtool doesn't work properly if not using built in compiler | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Stephen Montgomery-Smith <stephen> | ||||
Component: | Individual Port(s) | Assignee: | autotools | ||||
Status: | Closed Overcome By Events | ||||||
Severity: | Affects Only Me | CC: | cs, tijl | ||||
Priority: | Normal | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Stephen Montgomery-Smith
2011-03-14 00:50:06 UTC
Responsible Changed From-To: freebsd-ports-bugs->ade can u please take a look? Responsible Changed From-To: ade->autotools Reassign appropriately. 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 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 science/libctl is another case of this. Is this PR still relevant? 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. |