decision making in libtool. This was lost during the update and broke
the build of shared C++ libraries with SunPro on Solaris. Bump revision
of libtool-base.
Noticed by salo and dmcmahill, tested by dmcmahill.
to make decisions about which compiler is being used (gcc, SunPro, etc).
To make this function "correctly" in the presence of the compiler wrapper
scripts, we need to extract the actual compiler command from the wrapper
frame work. So adapt the section in the configure script which already
attempts to deal with some other compiler wrappers to deal with the pkgsrc
wrappers.
This should address PR pkg/33467 and PR pkg/34581.
Bump PKGREVISION.
of postgresql80-client. According to Ralf Wildenhues from libtool,
this fragment is just broken and the pre-1.5.21 was effectively a NOP.
Bump libtool-base revision.
some highlighted changes:
* Fixes minor /tmp race condition bug.
* Integrated Interix support; no longer requires pkgsrc hackery.
* shlibtool is a wrapper using the (now working) "--tag=disable-static".
* Several other bugs fixed, removing some pkgsrc-local changes.
Fix major problem brought to the surface by buildlink3 on Interix. For C++
or F77 libraries only, the soname did not always make it into the final
binary, resulting in runtime link failures in some cases and runtime linking
with a missing major version in others.
This is unfortunately a flag day for Interix + pkgsrc. Identifying all the
PKGREVISIONs normally requiring a bump is a little too unwieldy. However,
existing binaries not experiencing the runtime link failure will continue
to run, but will be linking against the unversioned ".so" at runtime until
the binaries have been rebuilt.
While here, fix a couple wrong assumptions in the libtool config for
Interix. shlibvar_overrides_runpath should have been "no", and
hardcode_direct should have been "yes".
makes -avoid-version work properly on platforms using $versuffix2 (e.g., OpenBSD,
FreeBSD, DragonFly). Bump PKGREVISION (and will bump LIBTOOL_REQD shortly).
MirOS change by Benny Siegert <bsiegert@mirbsd.org>.
Noted in private mail by Thorsten Glaser <tg@66h.42h.de>.
it. This value is embedded into the libtool script. This was okay
on NetBSD, but was breaking on Solaris. We now pass it the path to
the real echo via CONFIGURE_ENV, which on Solaris is a more featureful
echo. Problem noted by Mark Davies in private mail.
While here, since those instructions are still not being heeded, make the
warning comment extremely loud and obnoxious, and put it in both
libtool/Makefile.common and libtool-base/Makefile.
* Fix regression in 1.5.16 to not install libtldl data files from
`libtoolize --ltdl'ed software packages.
* Bug Fixes.
Changes 1.5.16:
* Allow shell special characters like `$' in source file names, but not
in object names, to enhance GCJ support.
* Detection of compiler wrappers like distcc/ccache and $host_alias prefix.
* More robust tests for PIC flag, `-c -o', in presence of warnings.
* Bug Fixes, among others for convenience archives regression on Solaris
and timestamp-preserving `libtoolize --copy --ltdl'.
Change summary since 1.5.10:
* ltmain.in: Add -pthread like flags when linking executables too.
* ltmain.in (func_extract_archives) [darwin]: This didn't actually
work on a real fat archive, should do now.
* tests/func_extract_archives.test: remove darwin fat tests which
did not actually work.
* ltmain.in (link mode): Allow five digits in version-info
* ltmain.in (link mode): With piecewise (partial) linking, fix
intermediate output name for subdir-objects.
* ltmain.in [darwin]: Don't add installed libs to temp_rpath when
building executables on darwin, or other systems which use
hardcode_automatic. It may break our wrapper scripts.
* ltmain.in [darwin]: Allow -framework foo through when given on
the command line.
* ltmain.in [irix]: Preserve processor option for SGI Compiler
(-r[0-9][0-9]*).
* ltmain.in: Don't pass through compiler-like thread flags when
using $LD to do the linking. Use compiler_flags instead.
Reported by Mark_Andrews@isc.org.
* libtool.m4 (AC_LIBTOOL_SYS_DYNAMIC_LINKER) [linux]: While "parsing"
/etc/ld.so.conf, skip comments.
* ltmain.in (func_extract_archives): Not all shells grok
`read -r' (unnecessary in this case).
Reported by Ralf Menzel <menzel@ls6.cs.uni-dortmund.de>.
* libtool.m4 [solaris] (AC_LIBTOOL_PROG_LD_SHLIBS): Use ${wl} for
whole_archive_flag_spec. Missing backport reported by Ralf Menzel
* libtool.m4 [linux] (AC_LIBTOOL_PROG_COMPILER_PIC): match
$cc_basename, not $CC against icc. Also, for symmetry match
icpc* and ecpc* (ia64 version of icpc).
* m4/libtool.m4 (_LT_SYS_DYNAMIC_LINKER) [linux]: Interpret
`include' statements in toplevel ld.so.conf file.
* config/ltmain.in (func_mode_link): When linking an installed
libtool library on the command line using -lfoo we need to find
the library in the search paths and add it's dependency_libs to
the link in the conv pass so that any libtool libs listed are
correctly expanded in the link pass.
ensure there is no whitespace on the command line when passing
-install_name to the linker, as this breaks the build.
this fixes the build of audio/libaudiofile and other packages using
-export-symbols on Darwin with xlc.
bump PKGREVISION.
specify (hardcoded) compilers from which we can infer the correct tag
(CC, CXX, F77). Use the following patterns to match compilers to
tags:
CC: *cc *xlc
CXX: *++ *CC
F77: *77 *fort
Bump the PKGREVISION to 1.5.10nb7 since we now infer the F77 tag from
likely Fortran compilers. Also require at least this version of
libtool when building packages that set USE_FORTRAN. This should fix
PR pkg/28661.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
* In libtool-base, generate shlibtool with a simple sed script; no full
build is actually needed.
Changelog:
New in 1.5.6: 2004-04-11; CVS version 1.5.5a, Libtool team:
* Installs libltdl files properly in $prefix/share/libtool/libltdl. 1.5.4
did not install them at all.
* libltdl correctly guesses the extension for loadable modules again.
New in 1.5.4: 2004-04-03; CVS version 1.5.3a, Libtool team:
* Bug fixes.
