Hi Bruno,
Bruno Haible wrote:
Roumen Petrov wrote:
Android and Microsoft windows must not encode any paths.
You probably mean to say: Shared libraries packaged in Android .apk
files are mentioned in the Android manifest file (elements
and ) [1] and therefore don't need a RUNPATH.
But shared
On Tue, 2024-01-16 at 20:47 -0500, Mike Frysinger wrote:
> On 16 Jan 2024 15:14, Richard Purdie wrote:
> > --- a/build-aux/ltmain.in
> > +++ b/build-aux/ltmain.in
> > @@ -7,7 +7,6 @@
> > # Copyright (C) 1996-2019, 2021-2024 Free Software Foundation, Inc.
> > # This is free software; see the sourc
If $CC has --sysroot=/, it is a valid configuration however libtool will
then set lt_sysroot to "/".
This means references like $lt_sysroot$libdir become //usr/lib instead
of the more normally expected /usr/lib. This may or may not break something
but certainly is confusing to the user and gives c
If lto is enabled, we need the prefix-map variables to be passed to the linker
to correctly link the objects using correctly mapped paths.
Add these to the list of options libtool passes through.
* build-aux/ltmain.in: Handle prefix-map compiler options
---
build-aux/ltmain.in | 2 ++
1 file cha
clang uses -rtlib and --unwindlib to select proper compiler runtime in
some cases. Therefore pass these options to linker when found in
ldflags
* build-aux/ltmain.in: Handle clang linker options
---
build-aux/ltmain.in | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/build-a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Frysinger wrote:
> On 16 Jan 2024 23:44, KO Myung-Hun wrote:
>> Some OSes such as OS/2, uses ';' as a path separator. So using
>> $PATH_SEPARATOR instead of hard-coded ':' is more proper.
>
> so we're on the same page, we're talking about the
On Wed, 17 Jan 2024, Roumen Petrov wrote:
Hi All
Mike Frysinger wrote:
On 16 Jan 2024 21:11, Brad Smith wrote:
libtool: remove OpenBSD support for non-shared and a.out archs
OpenBSD stopped supporting the last non-shared arch 8 years ago
and stopped supporting a.out 10.5 years ago.
This can
[original post:
https://lists.gnu.org/archive/html/libtool-patches/2017-06/msg0.html]
With all the flurry of commits I'm hoping this gets included.
[And gives me a chance to correct all the embarrassing typos
in the body of the original message]
Thanks.
On Sun, 18 Jun 2017, Tim Rice wrote:
On 18 Jun 2017 19:43, Tim Rice wrote:
> Here is a small patch to correct builds on svr5.
> When the freebsd-elf target was changed, this got missed.
>
> Symptoms were, build newer lib ened up with libfo.nn a loser number
> than the previous version. And building libpng-1.6.29 produced
> libtool:
On 17 Jan 2024, Mike Frysinger told this:
> this should be fixed in git now. i merged the one posted previously:
> https://savannah.gnu.org/patch/?9086
Truly, the dead walk!
(Thank you.)
(There are a few related problems on other architectures I've fixed in
the binutils copy of libtool.m4 too
On 17 Jan 2024 12:39, Richard Purdie wrote:
> If lto is enabled, we need the prefix-map variables to be passed to the linker
> to correctly link the objects using correctly mapped paths.
>
> Add these to the list of options libtool passes through.
merged, thanks
-mike
signature.asc
Description:
On 17 Jan 2024 12:39, Richard Purdie wrote:
> If $CC has --sysroot=/, it is a valid configuration however libtool will
> then set lt_sysroot to "/".
>
> This means references like $lt_sysroot$libdir become //usr/lib instead
> of the more normally expected /usr/lib. This may or may not break someth
On 17 Jan 2024 12:39, Richard Purdie wrote:
> clang uses -rtlib and --unwindlib to select proper compiler runtime in
> some cases. Therefore pass these options to linker when found in
> ldflags
merged, thanks
-mike
signature.asc
Description: PGP signature
* HACKING: Document syntax-check & distcheck & parallel testing.
---
HACKING | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/HACKING b/HACKING
index 664251e680a9..38401c9cd732 100644
--- a/HACKING
+++ b/HACKING
@@ -24,6 +24,14 @@ and is not part of a release d
When running `libtoolize --ltdl`, a symlink to the source config-h.in
is used rather than a copy of the file. This causes the build system
to look at its old timestamp relative to the other generated files
that are copied in, and then try to regenerate things, and update the
config-h.in timestamp
Various autotools rules will compare the timestamps of config-h.in
and configure, and if config-h.in is newer than configure, attempt
to regenerate it. This breaks `make distcheck` which we need to
produce new releases. So update config-h.in timestamp, but only
up to the configure file.
The brea
16 matches
Mail list logo