diff options
| author | Koop Mast <kwm@FreeBSD.org> | 2013-11-19 19:54:16 +0000 |
|---|---|---|
| committer | Koop Mast <kwm@FreeBSD.org> | 2013-11-19 19:54:16 +0000 |
| commit | 5d020c831fc7a6635780e7611c7ca7a500684757 (patch) | |
| tree | 8c5ccb665f8d67a9ab5ef81d7922d6d6da61d261 /CHANGES | |
| parent | Indent 20131031 entry like the rest of the file. (diff) | |
Remove ltverhack's hard depend on USE_AUTOTOOLS=libtool.
The problem with the old method is that the libtool is configured to look
first in LOCALBASE for libraries to link to. Normaly this wouldn't cause
a problem. However if a port that builds a library with new API also builds
introspection files or say gtk bindings, then libtool will look first into
LOCALBASE and find the old library version for linking the introspection
files or gtk bindings. Due to the missing new API in old library the build
will fail with unresolved symbols.
The new ltverhack will patch the ltmain.sh and/or libtool files that where
bundled with the port. This libtool is correctly configured to first look
in for the just build libraries.
If the port bundled version of ltmain.sh and/or libtool aren't in ${WRKSRC}
then ltverhack_PATCH_FILES can be overwritten with there location in ${WRKSRC}.
As a bonus when using the new ltverhack configure will honor --disable-static
again. So please check your plist after converting.
While here shorten the number of tabs in the lthacks, ltverhack and
ltasneededhack PRE_PATCH components so they are just over 80 chars long.
Exp-run by: bdrewery@
PR: ports/183936
Obtained from: gnome dev repo
Diffstat (limited to 'CHANGES')
| -rw-r--r-- | CHANGES | 15 |
1 files changed, 15 insertions, 0 deletions
@@ -10,6 +10,21 @@ in the release notes and/or placed into UPDATING. All ports committers are allowed to commit to this file. +20131119: +AUTHOR: kwm@FreeBSD.org + + The USE_GNOME component ltverhack no longer has a hard dependancy on + libtool. + + If USE_AUTOTOOLS=libtool isn't defined it will try to patch ltmain.sh + and or libtool in ${WRKSRC}. If those files are located somewhere else + in ${WRKSRC} then it is possible to overwrite ltverhack_PATCH_FILES + with there new locations. configure script --distable-static will work also + after using the "new" ltverhack. + + Please keep in mind that USE_AUTOTOOLS implies GNU_CONFIGURE so you might + need to add that back for the port to work. + 20131031: AUTHOR: rene@FreeBSD.org |