Re: [PATCH 7/7] Prefer $NM @file over calculating the cmd line length.

Hi Peter, * Peter Rosin wrote on Sat, Sep 11, 2010 at 02:24:18PM CEST: > Subject: [PATCH 7/7] Prefer $NM @file when the toolchain isn't native to > $build. > > * libltdl/config/ltmain.m4sh (func_mode_link): Avoid calculating > the command line length and take the @file branch *if* the file > nam

Re: [PATCH 0/3]: Another go at LTO support

* Ralf Wildenhues wrote on Sun, Aug 29, 2010 at 06:18:05PM CEST: > OK, so the issues I had with > > was both changing output_verbose_link_cmd to something that might work >

How many spaces after a period? [WAS: Re: [PATCH 7/7] Prefer $NM @file over calculating the cmd line length.]

On 12 Sep 2010, at 15:01, Ralf Wildenhues wrote: > * Peter Rosin wrote on Sat, Sep 11, 2010 at 02:24:18PM CEST: >> * libltdl/config/ltmain.m4sh (func_mode_link): Avoid calculating >> the command line length and take the @file branch *if* the file >> names needs to be converted for the toolchain and

Re: How many spaces after a period? [WAS: Re: [PATCH 7/7] Prefer $NM @file over calculating the cmd line length.]

Hi Gary, * Gary V. Vaughan wrote on Sun, Sep 12, 2010 at 11:23:52AM CEST: > On 12 Sep 2010, at 15:01, Ralf Wildenhues wrote: > > * Peter Rosin wrote on Sat, Sep 11, 2010 at 02:24:18PM CEST: > >> * libltdl/config/ltmain.m4sh (func_mode_link): Avoid calculating > >> the command line length and take

Re: getopt-m4sh tests failures with autom4te 2.61

* Ralf Wildenhues wrote on Thu, Sep 02, 2010 at 10:36:54PM CEST: > Hi Gary, > > I get testsuite failures of the first six tests with autom4te 2.61 early > in PATH (the testsuite itself has been created with 2.67). See below > for an example failure. Maybe getopt-m4sh.at really relies on >= 2.62?

Re: getopt-m4sh tests failures with autom4te 2.61

On 12 Sep 2010, at 16:42, Ralf Wildenhues wrote: > * Ralf Wildenhues wrote on Thu, Sep 02, 2010 at 10:36:54PM CEST: >> Hi Gary, Hallo Ralf, Sorry I didn't see the original yet... I still have 400 emails backed up in my Inbox. :( >> I get testsuite failures of the first six tests with autom4te 2.

Re: static FORTRAN compilation set-up in libtool.m4

* Ralf Wildenhues wrote on Thu, Sep 02, 2010 at 07:41:25PM CEST: > That's fine. Any support for nagfor is an improvement over no support. I've pushed the patch below to git master of Libtool now. Please test as described before, if at all possible. I changed the pic flag to -PIC so also large co

test with old autotools (was: [PATCH 1/6] Require Automake 1.11.1 for Libtool, enable color-tests.)

Hello Gary, you wanted a way to test old Autoconf and Automake with a git Libtool tree: * Gary V. Vaughan wrote on Sun, Aug 22, 2010 at 05:41:52PM CEST: > On 22 Aug 2010, at 22:30, Ralf Wildenhues wrote: > > * Gary V. Vaughan wrote on Sun, Aug 22, 2010 at 05:24:05PM CEST: > >> Of course, that doe

Re: test with old autotools (was: [PATCH 1/6] Require Automake 1.11.1 for Libtool, enable color-tests.)

On 12 Sep 2010, at 17:47, Ralf Wildenhues wrote: > you wanted a way to test old Autoconf and Automake with a git Libtool > tree: Awesome, thanks :) > [[snip]] > At this point, I'm not actually asking to commit this now. Consider it > a test balloon that you could use in your git tree to test thi

Re: test with old autotools

* Gary V. Vaughan wrote on Sun, Sep 12, 2010 at 12:58:23PM CEST: > On 12 Sep 2010, at 17:47, Ralf Wildenhues wrote: > > <0001-Try-out-new-testsuite-with-old-Autoconf-and-Automake.patch> > > You forgot to `git add tests/old-autoconf.at' before you generated the > patch though... D'oh. That's what

Fix AC_NO_EXECUTABLES test failure on IRIX 6.5.

I'm pushing this bugfix to fix this failure on IRIX with GCC (log already expired; Simon bumped the timeout to 24 days now): ../../libtool/tests/no-executables.at:75: : ${CONFIG_SHELL=/bin/sh}; export CONF IG_SHELL; $CONFIG_SHELL ./configure $configure_options stderr: configure: WARNING:

[PATCH] [cygwin|mingw] Correct static lib symbol extraction failure.

* libltdl/config/ltmain.m4sh (func_mode_link): When prefer_static_libs, ensure old_library name is used as linklib when possible. --- This patch corrects the (long-standing?) failure of mdemo-exec.test on mingw, but also some non-fatal anomalies in cygwin on the same tests. Basically, when dlopen'i

doc: wrapping, categorizing, and indexing improvements.

I paged through the PDF version of the manual looking for long lines, and went through the index looking for markup errors and wrong entries like '(void)' stemming from wrong number of arguments to @deftypefun and the like: there must be a space after } in @deftypefun {const char *}lt_dlgetsearch

Re: [PATCH] [cygwin|mingw] Correct static lib symbol extraction failure.

Hi Charles, * Charles Wilson wrote on Sun, Sep 12, 2010 at 03:19:51PM CEST: > * libltdl/config/ltmain.m4sh (func_mode_link): When prefer_static_libs, > ensure old_library name is used as linklib when possible. > --- > This patch corrects the (long-standing?) failure of mdemo-exec.test on > mingw,

Re: [PATCH] [cygwin|mingw] Correct static lib symbol extraction failure.

* Ralf Wildenhues wrote on Sun, Sep 12, 2010 at 04:20:13PM CEST: > * Charles Wilson wrote on Sun, Sep 12, 2010 at 03:19:51PM CEST: > > * libltdl/config/ltmain.m4sh (func_mode_link): When prefer_static_libs, > > ensure old_library name is used as linklib when possible. > Why does the patch have "[c

tests: work around zsh use of $options variable.

../../libtool/tests/getopt-m4sh.at:93: $SHELL ./options -fvi + /usr/local/bin/zsh ./options -fvi --- /dev/null 2010-09-12 14:28:42.575801479 + +++ /tmp/build/tests/testsuite.dir/at-groups/1/stderr 2010-09-12 14:28:42.634930285 + @@ -0,0 +1,2 @@ +./options:950: options: attempt to set ass

Re: [PATCH] [cygwin|mingw] Correct static lib symbol extraction failure.

On 9/12/2010 10:20 AM, Ralf Wildenhues wrote: > Hi Charles, > > * Charles Wilson wrote on Sun, Sep 12, 2010 at 03:19:51PM CEST: >> * libltdl/config/ltmain.m4sh (func_mode_link): When prefer_static_libs, >> ensure old_library name is used as linklib when possible. >> --- >> This patch corrects the

Re: [PATCH] [cygwin|mingw] Correct static lib symbol extraction failure.

On 9/12/2010 10:25 AM, Ralf Wildenhues wrote: > Also, $linklib is used for several other things. It would seem prudent > to make sure it is clear that this is a very intrusive patch, or use > another helper variable to make it less intrusive. Oh, I think linklib was *wrong* no matter what. If yo

Re: [PATCH] [cygwin|mingw] Correct static lib symbol extraction failure.

On 9/12/2010 10:20 AM, Ralf Wildenhues wrote: > I suggest you commit it so that it can be included > in the testing. Pushed as: When assigning $linklib value, honor [-all]-static[-libtool-libs] * libltdl/config/ltmain.m4sh (func_mode_link): When prefer_static_libs and static library exists, ensu

tests: avoid empty AT_DATA contents, for zsh.

This fixes the remaining testsuite failures with zsh 4.3.10 on FreeBSD. cat >file

Re: [PATCH] * HACKING (Maintenance Notes): Adjust to moved files.

Den 2010-09-11 23:18 skrev Ralf Wildenhues: > * Peter Rosin wrote on Sat, Sep 11, 2010 at 09:02:54PM CEST: >> I noticed that HACKING referred to files that have been moved. >> >> Should I also add libltdl/config/compile? > > Yes, plase. > >> But that one does not >> appear to be handled by "make

[PATCH] * .gitignore: Ignore *.obj files for MSVC (and w32 in general).

Hi! I have pushed this as obvious. Cheers, Peter >From 52e86c62786b95f91f32e7020f7eaf3c1be9a59b Mon Sep 17 00:00:00 2001 From: Peter Rosin Date: Sun, 12 Sep 2010 18:43:11 +0200 Subject: [PATCH] * .gitignore: Ignore *.obj files for MSVC (and w32 in general). --- .gitignore |1 + ChangeLog

Re: How many spaces after a period? [WAS: Re: [PATCH 7/7] Prefer $NM @file over calculating the cmd line length.]

Baffled on several fronts ... declaring `...@frenchspacing on' conversely indicates the use of a single space at the end of a sentence - the exact opposite of how the term is normally used: No, it is not the opposite, it is the normal meaning. Turning on "French" spacing means precis

Re: doc: wrapping, categorizing, and indexing improvements.

Hallo Ralf, On 12 Sep 2010, at 21:12, Ralf Wildenhues wrote: > I paged through the PDF version of the manual looking for long lines, > and went through the index looking for markup errors and wrong entries > like '(void)' stemming from wrong number of arguments to @deftypefun > and the like: there

Re: How many spaces after a period?

Hi Karl, Thanks for the swift response. On 13 Sep 2010, at 05:01, Karl Berry wrote: > Baffled on several fronts ... > >declaring `...@frenchspacing on' conversely indicates the use of a >single space at the end of a sentence - the exact opposite of how >the term is normally used: >