Bug#353346: libtool_1.9+20051221-1(hppa/experimental): FTBFS: segv in test

Hi Frank, * Frank Lichtenheld wrote on Fri, Feb 17, 2006 at 05:19:37PM CET: > Package: libtool > Version: 1.9+20051221-1 > Severity: serious This looks like the test suite failed, but not like the source failed to build. Is a successful `make check' prerequisite for a successful build? If yes:

Bug#347650: libtool: Incorrect argument reordering

* Loïc Minier wrote on Sat, Feb 18, 2006 at 09:07:19PM CET: > On mer, jan 11, 2006, Kurt Roeckx wrote: > > I suggest if you create a convience library, you don't link any > > libraries to it at that time. Instead, when you are linking in > > the convience libraries to something, at that point you

Bug#348558: libtool: No such file or directory when linking 2 .la files with the same name but from different directories

Hi Carlo, * Carlo Contavalli wrote on Tue, Jan 17, 2006 at 07:04:55PM CET: > > With something like: > libtool --mode=link gcc -g -O2 -std=c99 -Wall -pedantic > -D_POSIX_C_SOURCE=200112L \ > -Wall -export-dynamic -module -avoid-version -rpath /test -o test.la > file.lo ../lib1/libtest.la ../li

Bug#348558: libtool: No such file or directory when linking 2 .la files with the same name but from different directories

Hi Carlo, * Carlo Contavalli wrote on Wed, Jan 18, 2006 at 02:26:27PM CET: > On Wed, Jan 18, 2006 at 09:26:26AM +0100, Ralf Wildenhues wrote: > > Thanks for the concise bug report. Two comments: your libtest.la > > libraries are convenience archives, so this usage should probably

Bug#348558: libtool: No such file or directory when linking 2 .la files with the same name but from different directories

[ this is http://bugs.debian.org/348558 ] * Carlo Contavalli wrote on Wed, Jan 18, 2006 at 05:01:29PM CET: > On Wed, Jan 18, 2006 at 03:52:33PM +0100, Ralf Wildenhues wrote: > > > Try the patch at the end (not yet tested very much); it should not be > > system-specific. >

Bug#348558: libtool: No such file or directory when linking 2 .la files with the same name but from different directories

Thinking about this again: * Ralf Wildenhues wrote on Wed, Jan 18, 2006 at 03:52:33PM CET: > * Carlo Contavalli wrote on Wed, Jan 18, 2006 at 02:26:27PM CET: > > > If there's something not allowed/portable/..., I'd expect something > > like: "moron don't d

Bug#348558: libtool: No such file or directory when linking 2 .la files with the same name but from different directories

Hi Bob, * Bob Friesenhahn wrote on Sat, Jan 21, 2006 at 07:12:55PM CET: > On Sat, 21 Jan 2006, Ralf Wildenhues wrote: > >[ this is http://bugs.debian.org/348558 ] > > > >* Carlo Contavalli wrote on Wed, Jan 18, 2006 at 05:01:29PM CET: > >>On Wed, Jan 18, 2006 at 03:

Bug#343629: autoconf2.13: make autoconf wrapper aware that --force is 2.53+

Package: autoconf2.13 Version: 2.13-54 Severity: normal Tags: patch autoconf --force works only with 2.50+. Kurt Roeckx uncovered this while testing unreleased libtool: http://lists.gnu.org/archive/html/bug-libtool/2005-12/msg2.html I'm putting a fix into libtool's test suite (give the arch

Bug#320698: Debian-specific binary deps patch

Hi there, Sorry for the long latency. * Philip Martin wrote on Fri, Oct 07, 2005 at 01:38:48AM CEST: > Kurt Roeckx <[EMAIL PROTECTED]> writes: > > > After reading bug #291641, I'd have to agree this is a problem > > with the linker. > > It's not quite so clear to me. Here's the script I've bee

Bug#297726: link_all_deplibs=no in libtool.m4 assumes non-crosscompiling link er

Hi Manuel, Huge latency, sorry. :-/ * Klimek Manuel wrote on Wed, Mar 02, 2005 at 04:12:30PM CET: > > The libtool.m4 file which comes in this release differs > from the upstream libtool.m4 for libtool-1.5.6. > > Especially the diff > 5009,5011d5004 > < linux*) > < _LT_AC_TAGVAR(link_all_

Bug#320698: Debian-specific binary deps patch

* Ralf Wildenhues wrote on Wed, Nov 30, 2005 at 11:07:47PM CET: > > Hmm. Sounds like quite a bit of work. And pretty dangerous, too. We'd > need lots of good tests. One thing to always keep in mind (for upstream > GNU Libtool) is that this change of operation must not cha

Bug#341978: libtool: prune unused libs from the linker line on GNU/kFreeBSD

Hi Kurt, Aurelien, * Kurt Roeckx wrote on Sun, Dec 04, 2005 at 05:10:47PM CET: > On Sun, Dec 04, 2005 at 04:59:12PM +0100, Aurelien Jarno wrote: > > > > The patch you added to libtool to prune unused libs from the linker line > > is a very nice thing and will probably ease the next transitions.

Bug#341978: libtool: prune unused libs from the linker line on GNU/kFreeBSD

* Kurt Roeckx wrote on Sun, Dec 04, 2005 at 07:47:32PM CET: > On Sun, Dec 04, 2005 at 05:54:48PM +0100, Ralf Wildenhues wrote: > > > > By the way, why don't you submit the patches regarding the BSD changes > > Mainly because I have no idea if: > - It's complet

Bug#347650: libtool: Incorrect argument reordering

Hi Josselin, * Josselin Mouette wrote on Wed, Jan 11, 2006 at 09:59:57PM CET: > > It looks like libtool likes, when building libraries, to reorder > arguments: Well, yes. It move all the options away from the libraries + library flags. GNU libtool plans to lift this restriction, but it unfort

Bug#348029: can't relibtoolize due to configure.ac in a subdir

Hi Paul * Paul Wise wrote on Sat, Jan 14, 2006 at 09:35:08AM CET: > Package: libtool > Version: 1.5.22-2 > Severity: normal > > I tried to relibtoolize[1] a package[2] I am packaging, and libtoolize > failed because configure.ac is in a subdirectory of the source tree. > libtoolizing from that di

Bug#348029: can't relibtoolize due to configure.ac in a subdir

* Ralf Wildenhues wrote on Sat, Jan 14, 2006 at 10:36:05AM CET: > > Below is a patch for a completely independent error in configure.ac -- > it would be nice if you could report it upstream. You know, I wasn't awake yet.. Patch in right direction below. Sorry. Cheers, Ra

Bug#348029: can't relibtoolize due to configure.ac in a subdir

* Paul Wise wrote on Sat, Jan 14, 2006 at 11:09:55AM CET: > On Sat, 2006-01-14 at 10:36 +0100, Ralf Wildenhues wrote: > > > > I tried to relibtoolize[1] a package[2] I am packaging, and libtoolize > > > failed because configure.ac is in a subdirectory of the source tree.

Bug#350989: libtool on alpha causes linking errors when run on AFS

Hi Juha, Sorry in advance if my mailer messes up your name. :-( * Juha JÀykkÀ wrote on Thu, Feb 02, 2006 at 09:36:49AM CET: > > Building shared libraries on Debian/Alpha does not work when the source is > on AFS, but instead causes a linking error: Can you definitely rule out that it does not

Bug#350989: libtool on alpha causes linking errors when run on AFS

Hi Juha, * Juha Jäykkä wrote on Fri, Feb 03, 2006 at 08:12:12AM CET: > > Can you definitely rule out that it does not happen when the source is > > not on AFS (but otherwise the same system)? > > I can. I built 0.7.1-1 on both AFS and xfs, AFS fails, xfs works; then I > tried 0.7.1-3 on AFS, stil

Bug#344662: libtool: gentoo patch breaking on Debian amd64.

Hi Kurt, * Kurt Roeckx wrote on Wed, Dec 28, 2005 at 02:36:07PM CET: > On Wed, Dec 28, 2005 at 10:03:55AM +0100, Ralf Wildenhues wrote: > > > > Since I don't have a Debian amd64 system for testing, please rerun > > the build, post the > > ./libtool --mode=

Bug#345607: libtool: "line 606: --: command not found" message for --mode=link

Hi John, * John V. Belmonte wrote on Mon, Jan 02, 2006 at 08:22:34AM CET: > > In a clean sid environment, running libtool with "--mode=link" causes the > following message to be output on sterr: > > /usr/bin/libtool: line 606: --: command not found Could you please rerun the command line wi

Bug#321689: automake1.9: "make dist" distributes too many files (dist-info)

[ this is http://bugs.debian.org/321689 ] * Vincent Lefevre wrote on Sun, Aug 07, 2005 at 12:00:21AM CEST: > > In addition to the file .info, I had a .info.bak > in the source directory, and when I did a "make dist", both files > were included in the distribution. Only .info should have > been in

Bug#345607: libtool: "line 606: --: command not found" message for --mode=link

* Kurt Roeckx wrote on Mon, Jan 02, 2006 at 01:48:24PM CET: > On Mon, Jan 02, 2006 at 09:39:44AM +0100, Ralf Wildenhues wrote: > > * John V. Belmonte wrote on Mon, Jan 02, 2006 at 08:22:34AM CET: > > > > > > In a clean sid environment, running libtool with "--mode=

Bug#345607: libtool: "line 606: --: command not found" message for --mode=link

* Kurt Roeckx wrote on Mon, Jan 02, 2006 at 02:35:23PM CET: > > I noticed that it had that "--" in it before, I just never saw it > generate any problems. I don't think it does now. > On Mon, Jan 02, 2006 at 02:10:52PM +0100, Ralf Wildenhues wrote: > > You cou

Bug#219490: libtool: Completely dumb assumption can make -fPIC test fail

package libtool tags 219490 fixed-upstream thanks * Bob Friesenhahn wrote on Fri, Nov 07, 2003 at 05:27:38PM CET: > On Fri, 7 Nov 2003, Josselin Mouette wrote: > > Le ven 07/11/2003 à 04:03, Scott James Remnant a écrit : > > > > The comments says all. Of course there can be other warnings! Especia

Bug#304400: /usr/share/info/libtool.info.gz: wrong names for structure members

* Hans Ulrich Niedermann wrote on Tue, Apr 12, 2005 at 11:31:59PM CEST: > > Contrary to the info page, the names of the structure members > are all in lower case in reality. > > Excerpt from the wrong info page: > - Type: struct lt_dlinfo { char *FILENAME; char *NAME; int REF_COUNT; } Unfortun

Bug#300926: dietlibc-dev: /usr/lib/diet/lib-powerpc, not lib-ppc

Hi Gerrit, Lars, * Gerrit Pape wrote on Fri, Mar 25, 2005 at 09:48:25AM CET: > > there's no need for other packages to know about the location of the > diet libc libraries, I don't know why libtool is used here; looks like > it complicates things. Simply use CC='diet -v -Os gcc' and LD='diet -v

Bug#372179: AC_CANONICAL_SYSTEM overwrites $@

Hello Justin, Tollef, everyone, * Justin Erenkrantz wrote on Fri, Jun 16, 2006 at 09:12:11PM CEST: > > The point of our autoconf macro is to allow 'shortcuts', such that the > argument > > --with-layout=Foo > > rewrites prefix/libexec/etc to a specific set of values (dictated by > our file con

Bug#372179: AC_CANONICAL_SYSTEM overwrites $@

Hello Justin, Tollef, * Justin Erenkrantz wrote on Sun, Jun 18, 2006 at 11:40:12PM CEST: > On 6/18/06, Tollef Fog Heen <[EMAIL PROTECTED]> wrote: > >Currently, if configure is passed --sbindir=, it just overrides > >$sbindir without flagging that at all. If it, in addition to changing > >$sbindir

Bug#372179: AC_CANONICAL_SYSTEM overwrites $@

* Justin Erenkrantz wrote on Mon, Jun 19, 2006 at 06:17:49PM CEST: > On 6/19/06, Tollef Fog Heen <[EMAIL PROTECTED]> wrote: > >| > On 6/18/06, Tollef Fog Heen <[EMAIL PROTECTED]> wrote: > >| > >Currently, if configure is passed --sbindir=, it just overrides > >| > >$sbindir without flagging that at

Bug#373953: ruby1.9: FTBFS: Error in ext/bigdecimal Makefile

Hello, * Steinar H. Gunderson wrote on Sun, Jun 25, 2006 at 02:11:12PM CEST: > On Fri, Jun 16, 2006 at 01:03:43PM -0400, Daniel Schepler wrote: > >> Does the line 143 contain "|#_!!_#|"? > > > > Yes, it does: > > > > .cc.|#_!!_#|o: > > For those interested in squashing this bug, it looks like s

Bug#375349: autoconf: puts |#_!!_#| in output files

[ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375349 ] Hi Steinar, Thanks much for reporting this. * Steinar H. Gunderson wrote on Sun, Jun 25, 2006 at 02:31:21PM CEST: > Package: autoconf > Version: 2.59.cvs.2006.05.13-1 > Severity: important > > Newer autoconf versions seem to use |#_!!_

Bug#372517: libtool builds non-PIC shared libraries with AC_DISABLE_STATIC and --enable-static

Hello Rémi, * Rémi Denis-Courmont wrote on Fri, Jun 09, 2006 at 10:34:43PM CEST: > > When passing the --enable-static option to the configure script of a > package that has disabled static libraries by default using > AC_DISABLE_STATIC in its configure.ac, both static and *shared* > libraries tha

Bug#372241: Bug#372179: marked as done (autoconf: AC_CANONICAL_SYSTEM overwrites $@)

Getting bug-autoconf into play: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=372241 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=372179 > Date: Thu, 8 Jun 2006 20:09:30 +0200 > From: Julien Danjou <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: apr-util: FTBFS: cannot stat `./debian

Bug#372241: Bug#372179: marked as done (autoconf: AC_CANONICAL_SYSTEM overwrites $@)

Hi Stepan, * Stepan Kasal wrote on Thu, Jun 15, 2006 at 06:12:51PM CEST: > > [...] several macros in Autoconf overwrite the positional > > parameters, not just AC_CANONICAL_SYSTEM. For example, > > AC_CHECK_PROG does, so do some others. [...] > > I agree that we should document this limitation.

Bug#407079: libtool: All GNU targets support -Wl,--version-script

Hello Samuel, * Samuel Thibault wrote on Tue, Jan 16, 2007 at 01:31:21AM CET: > > unixodbc currently FTBFS at least on hurd-i386 and kfreebsd-i386 when > performing its manifest check because libtool doesn't make it use the > --version-script option. Indeed, it is only set on $host_os ~= linux*)

Bug#407079: libtool: All GNU targets support -Wl,--version-script

* Samuel Thibault wrote on Tue, Jan 16, 2007 at 10:10:43AM CET: > Ralf Wildenhues, le Tue 16 Jan 2007 09:18:18 +0100, a écrit : > > > > What would gnu* be good for? > > For hurd-i386. What's the complete host string (or possible strings) for Hurd? I'm asking

Bug#368012: mingw crosscompilation broken with autoconf-2.59.cvs.2006.05.13-1

Hi Eric, Paul, * Eric Blake wrote on Thu, May 25, 2006 at 02:49:17PM CEST: > According to Ralf Wildenhues on 5/25/2006 4:49 AM: > > +# in a Makefile. Because we should not override ac_cv_exeext if it was > > +# cached, so that the user can short-circuit this test for compilers &g

Bug#179086: AC_DEFINE_UNQUOTED and autoheader

> @@ -2889,9 +2889,12 @@ > @code{AC_DEFINE} or one @code{AC_DEFINE_UNQUOTED} call with a third > argument for each symbol (@pxref{Defining Symbols}). An additional > constraint is that the first argument of @code{AC_DEFINE} > -or @code{AC_DEFINE_UNQUOTED} must be a > -literal. Note that all sy

Bug#179086: AC_DEFINE_UNQUOTED and autoheader

* Ben Pfaff wrote on Thu, May 25, 2006 at 08:42:30PM CEST: > Debian Bug #179086 (CC'd) states the following: > > I have code like > > ac_tr_lib=HAVE_LIB`echo $1 | sed -e 's/[^a-zA-Z0-9_]/_/g' \ > -e 'y/abcdefghijklmnopqrstuvwxyz/ABCDEFGHIJKLMNOPQRSTUVWXYZ/'` > AC_DEFIN

Bug#369396: Regression: problems with macro calling AC_PROG_CC and AC_C_BIGENDIAN

[ Cc:ing bug-autoconf ] Hi Mikael, * Mikael Magnusson wrote on Mon, May 29, 2006 at 05:06:13PM CEST: > > If you call AC_PROG_CC and AC_C_BIGENDIAN in a macro, the checks for > unistd.h and some other headers will fail. See attached test case. Interesting. This looks like a genuine bug in Autoc

Bug#369396: Regression: problems with macro calling AC_PROG_CC and AC_C_BIGENDIAN

* Ralf Wildenhues wrote on Mon, May 29, 2006 at 05:38:12PM CEST: > * Mikael Magnusson wrote on Mon, May 29, 2006 at 05:06:13PM CEST: > > > > If you call AC_PROG_CC and AC_C_BIGENDIAN in a macro, the checks for > > unistd.h and some other headers will fail. See attached te

Bug#369396: Regression: problems with macro calling AC_PROG_CC and AC_C_BIGENDIAN

* quoting myself: > > AC_C_BIGENDIAN requires (through some indirect macro chain) both > AC_PROG_CC and AC_LANG_PREPROC(C). Now, since you've explicitly called > AC_PROG_CC before, that requirement is already deemed fulfilled by the > stacking algorithm. The AC_LANG_PREPROC(C) requirement is not

Bug#369396: Regression: problems with macro calling AC_PROG_CC and AC_C_BIGENDIAN

Hi Stepan, * Stepan Kasal wrote on Wed, May 31, 2006 at 11:14:50AM CEST: > On Tue, May 30, 2006 at 08:19:14AM +0200, Ralf Wildenhues wrote: > > I guess you could instead also m4_define TEST_INIT, so that it will not > > take part in the requirement-diversion game. That shou

Bug#370282: Worth mentioning that Gnome needs a fix for newer Autoconf?

* Ben Pfaff wrote on Sun, Jun 04, 2006 at 08:36:17PM CEST: > Loïc Minier reported in the Debian package's bug system that > Gnome packages will break with the introduction of > ${datarootdir}. It looks to me like the real problem is really > in the macro used by Gnome, and I've suggested that they

Bug#370282: Worth mentioning that Gnome needs a fix for newer Autoconf?

Hi Ben, * Ben Pfaff wrote on Mon, Jun 05, 2006 at 12:10:32AM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > I wonder what's necessary to make the NEWS item explicit enough: > You sound a little frustrated. I hope I'm not causing that. No, you are no

Bug#370282: Worth mentioning that Gnome needs a fix for newer Autoconf?

Hello Paul, Ben, * Paul Eggert wrote on Sun, Jun 04, 2006 at 11:05:31PM CEST: > Ben Pfaff <[EMAIL PROTECTED]> writes: > > > The problem is in AM_GLIB_DEFINE_LOCALEDIR from > > m4macros/glib-gettext.m4 which hardcodes a double shell expansion: > >localedir=`eval echo "${datadir}/locale"` >

Bug#370282: Worth mentioning that Gnome needs a fix for newer Autoconf?

* Loïc Minier wrote on Mon, Jun 05, 2006 at 10:51:03AM CEST: > On Sun, Jun 04, 2006, Paul Eggert wrote: > > > First, Autoconf is supposed to warn about the suspicious usage of > > datadir without defining datarootdir. Did the warning not work for > > you? If so, can you show us how to reproduce

Bug#370282: Worth mentioning that Gnome needs a fix for newer Autoconf?

Hi Loïc, * Loïc Minier wrote on Mon, Jun 05, 2006 at 10:43:06AM CEST: > > I also had the feeling you were frustrated that I didn't see the NEWS > document prior to reporting this bug. I'm sorry that you spent extra > effort in properly documenting this, I should have checked NEWS and > reque

Bug#400636: posh: double-quotes within double-quoted backquote are expanded wrongly

Package: posh Version: 0.5.3 Severity: normal posh shares the following POSIX compliance bug with pdksh, quoting: http://www.gnu.org/software/autoconf/manual/html_node/Shellology.html#index-g_t_0040samp_007bpdksh_007d-1173 | Unfortunately, with pdksh 5.2.14 (the latest stable version as of | Febr

Bug#400637: posh: double-quotes within double-quoted backquote are expanded wrongly

Package: posh Version: 0.5.3 Severity: normal posh shares the following POSIX compliance bug with pdksh, quoting: http://www.gnu.org/software/autoconf/manual/html_node/Shellology.html#index-g_t_0040samp_007bpdksh_007d-1173 | Unfortunately, with pdksh 5.2.14 (the latest stable version as of | Febr

Bug#400636: posh: double-quotes within double-quoted backquote are expanded wrongly

* Clint Adams wrote on Mon, Nov 27, 2006 at 10:18:11PM CET: > > posh shares the following POSIX compliance bug with pdksh, quoting: > > http://www.gnu.org/software/autoconf/manual/html_node/Shellology.html#index-g_t_0040samp_007bpdksh_007d-1173 > > Can you explain why this is incorrect I think th

Bug#400636: posh: double-quotes within double-quoted backquote are expanded wrongly

* Clint Adams wrote on Mon, Nov 27, 2006 at 11:16:52PM CET: > > I think this message explains it fairly well: > > http://lists.gnu.org/archive/html/autoconf-patches/2004-07/msg00010.html > > I'm not sure how this meshes with 2.6.3: > http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap

Bug#401377: autoconf: AC_FUNC_FSEEKO does not make fseeko()/ftello() visible

Hello Peter, On Sun, Dec 03, 2006 at 01:41:44AM +0100, Peter Palfrader wrote: Starting with 2.61-1 autoconf's AC_FUNC_FSEEKO no longer makes fseeko() or ftello() visible on sid. It still worked with 2.60a4-1. Please post the parts of config.log that belong to the fseeko tests (both old and

Bug#367115: Libtool sets rpath when cross-compiling for default location

Hi Bas, * Bas Wijnen wrote on Sat, May 13, 2006 at 10:46:37PM CEST: > > Debian libtool does not set rpath for libraries and binaries which are > going to be installed in the standard locations ($prefix/lib, > $prefix/bin). It does set it when cross compiling, though, to > "/usr/$arch/{lib,bin}".

Bug#367501: autoconf: checking for vsnprintf fails with cross-compilation error, while cross-compilation is not the case

Hi Krzysztof, * Krzysztof Witkowski wrote on Tue, May 16, 2006 at 03:18:05PM CEST: > Package: autoconf > Version: 2.59.cvs.2006.05.13-1 > Severity: normal > > I'm using autoconf for my own project. Generated ./configure fails with error: > checking for C99-compatible vsnprintf()... configure: err

Bug#347650: hackish patch

Hi Josselin, * Josselin Mouette wrote on Wed, May 17, 2006 at 01:54:30AM CEST: > The attached patch is applied to libgnome, to avoid argument reordering > for -Wl,--as-needed. > > It is only a hack, but it works. With it, libgnome has reduced > dependencies as expected. It's not bad, but it's mi

Bug#368012: mingw crosscompilation broken with autoconf-2.59.cvs.2006.05.13-1

[ Cc:ing bug-autoconf as this is a genuine bug IMHO. ] Hi Tim, Thanks for reporting this! * Tim Kosse wrote on Fri, May 19, 2006 at 10:56:01AM CEST: > Package: autoconf > Version: 2.59.cvs.2006.05.13-1 > Severity: important > > If crosscompiling an autotools based package with mingw for Windows

Bug#368502: autoconf: breaks existing build systems that use ${datadir}

[ Cc:ing bug-autoconf ] Hi Blake, * Blake Barnett wrote on Mon, May 22, 2006 at 08:21:19PM CEST: > Package: autoconf > Version: 2.59.cvs.2006.05.13-1 > Severity: important > > If configure.in uses ${datadir} for some reason this version of > autoconf tries to replace it with ${datarootdir}, the

Bug#368012: mingw crosscompilation broken with autoconf-2.59.cvs.2006.05.13-1

* Stepan Kasal wrote on Sat, May 20, 2006 at 04:08:38PM CEST: > > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > > > I'm still wondering whether we should just simply revert both patches, > > I have talked with Ralf by phone, and I agree with him tha

Bug#368502: autoconf: breaks existing build systems that use ${datadir}

[ better keep the debian bug address in Cc: ] * Ben Pfaff wrote on Tue, May 23, 2006 at 01:34:18AM CEST: > > The "configure" script from the CVS autoconf did report warnings > for the lack of datarootdir. This appears to be harmless. The > two versions of "configure" generated identical config.

Bug#368012: mingw crosscompilation broken with autoconf-2.59.cvs.2006.05.13-1

> * lib/autoconf/lang.m4 (_AC_COMPILER_EXEEXT_DEFAULT): Drop the > initialization of `ac_cv_exeext', do not override it if it was > already set. Add comment about this potential backward > incompatibility. Do not export `ac_cv_exeext', Libtool hasn't > needed this fo

Bug#368712: fails with svn avahi

Hi Frederic, * Frederic Peters wrote on Wed, May 24, 2006 at 01:55:50PM CEST: > Package: autoconf > Version: 2.59.cvs.2006.05.13-1 > Severity: normal > > autoconf went upgraded in one of the chroot running jhautobuild[1] and > avahi started no longer to compile, failing in autom4te. > > This may

Bug#368712: fails with svn avahi

This patch is correct, and also fixes things for Autoconf-2.59. That version just didn't expose the bug. I'd be grateful if you could report this to the Doxygen people -- thanks! Cheers, Ralf > --- avahi-0.6.10/common/doxygen.m42005-08-04 02:45:33.0 +0200 > +++ avahi-0.6.10/common/do

Bug#368502: autoconf: breaks existing build systems that use ${datadir}

* Blake Barnett wrote on Wed, May 24, 2006 at 07:53:57PM CEST: > > I don't believe EET actually installs anything as data. So it's not > using ${datadir}. Things that do, such as embryo and/or edje, appear > to install things correctly but the binaries actually reference > (literally) ${da

Bug#368012: mingw crosscompilation broken with autoconf-2.59.cvs.2006.05.13-1

* Ralf Wildenhues wrote on Tue, May 23, 2006 at 11:05:53AM CEST: > > * lib/autoconf/lang.m4 (_AC_COMPILER_EXEEXT_DEFAULT): Drop the > > initialization of `ac_cv_exeext', do not override it if it was > > already set. Add comment about this potential backward

Bug#368877: Regression in the way strings are quoted

Hi Loïc, * Loïc Minier wrote on Thu, May 25, 2006 at 06:22:52PM CEST: > > totem's configure.in uses: apt-get -t unstable source totem gives me 1.2.1-4. So how do I get the one you're looking at? > When I run autoconf 2.59.cvs.2006.05.13-1, and then ./configure, the > resulting #define VE

Bug#368877: Regression in the way strings are quoted

Hi Loïc, * Loïc Minier wrote on Thu, May 25, 2006 at 06:22:52PM CEST: > > When I run autoconf 2.59.cvs.2006.05.13-1, and then ./configure, the > resulting #define VERSION in config.h is not quoted in the same way. > It now ends up with: > #define VERSION 1.4.1 > while with autoconf 2.59a-

Bug#306190: [David Jarvie] Bug#306190: autoconf wrapper fails to run autoheader

Hi David, * Ben Pfaff wrote on Thu, May 25, 2006 at 06:58:30PM CEST: > Forwarding info that doesn't appear in online log. Well, the URL cited in the BTS, http://www.astrojar.org.uk/linux/download/kalarm-1.2.6.kde2.tar.bz2 doesn't work for me. The message that stated it is about a year old. If t

Bug#357378: [gmane.comp.sysutils.autoconf.general] autoconf will accept a nonexistent compiler as the second one checked

* Ben Pfaff wrote on Thu, May 25, 2006 at 07:21:35PM CEST: > Passing along my report of this bug to the autoconf mailing list. > The full discussion there can be conveniently viewed via gmane: > http://comments.gmane.org/gmane.comp.sysutils.autoconf.general/7563 Thanks for this. I should

Bug#368012: mingw crosscompilation broken with autoconf-2.59.cvs.2006.05.13-1

Hi Paul, * Paul Eggert wrote on Fri, May 26, 2006 at 12:04:40AM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > OK to commit first the reversal patch posted in an earlier > > message, then this one? > > Sorry, I've lost context. Can you please give

Bug#377284: autoconf: source build fails with dependency on previous testing version

* Michael Moss wrote on Fri, Jul 07, 2006 at 11:39:50PM CEST: > Package: autoconf > Version: 2.59.cvs.2006.06.05-1 > Severity: important > Justification: fails to build from source > dpkg-checkbuilddeps: Unmet build dependencies: autoconf (>= > 2.59.cvs.2006.05.13) > > Is it normal to depend on

Bug#384322: libtool: wrong test semantics make relinking fail on empty $libdir

Hello Sam, Thanks for the bug report. * Sam Hocevar (Debian packages) wrote on Wed, Aug 23, 2006 at 03:50:06PM CEST: > >Relinking fails when $libdir is detected as being empty. This is due > to the following code: > > # Determine the prefix the user has applied to our future dir. > i

Bug#389558: autoconf: AC_PROG_GCC_TRADITIONAL throws error in comparision

Hello IOhannes, Thanks for the report. * IOhannes m zmoelnig wrote on Tue, Sep 26, 2006 at 02:22:07PM CEST: > Package: autoconf > Version: 2.60a-3 > Severity: normal > > AC_PROG_GCC_TRADITIONAL tests if $ac_cv_prog_gcc_traditional is set to > "yes" or "no"; if ac_cv_prog_gcc_traditional is not s

Bug#391427: Debian's version of libtool breaks correct link order

* Carlo Wood wrote on Fri, Oct 06, 2006 at 04:03:42PM CEST: > /bin/sh ../libtool --tag=CXX --mode=link g++ -g -DCWDEBUG > -I/usr/local/install/4.1.2-20060901/include -W -Wall -Wundef -DDEBUG > -I"/usr/include/boost-1_33_1" -export-dynamic -o edragon -export-dynamic > -no-undefined -Wl,--whole

Bug#391427: Debian's version of libtool breaks correct link order

Oops. My previous comment was correct, but unrelated to the issue at hand, which I haven't been able to analyze yet. Can try to do next week (unless beaten to, of course ;-) Cheers, Ralf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PRO

Bug#389558: autoconf: AC_PROG_GCC_TRADITIONAL throws error in comparision

[ this is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389558 ] Hello, * IOhannes m zmoelnig wrote on Wed, Sep 27, 2006 at 12:14:01PM CEST: > Ralf Wildenhues wrote: > > >Could you show the package, configure invocation and output where you > >are experiencing this with

Bug#389558: autoconf: AC_PROG_GCC_TRADITIONAL throws error in comparision

[ apologies for the resend ] [ this is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389558 ] Hello, * IOhannes m zmoelnig wrote on Wed, Sep 27, 2006 at 12:14:01PM CEST: > Ralf Wildenhues wrote: > > >Could you show the package, configure invocation and output where you > &g

Bug#389558: autoconf: AC_PROG_GCC_TRADITIONAL throws error in comparision

* Paul Eggert wrote on Thu, Oct 12, 2006 at 09:45:56AM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > Autoconf folks: OK to apply? Alternatively, [...] > > For now I'd rather that you just apply the patch you sent; thanks. Done. Thanks! Ralf -- To

Bug#431414: libtool generates incorrect option for Solaris ld

tags: upstream thanks * Vincent Lefevre wrote on Mon, Jul 02, 2007 at 02:07:36PM CEST: > > I've done a "make dist" on the MPFR library under Debian, and with this > tarball, when I do a "./configure --enable-shared" under Solaris, "make" > fails: See

Bug#382893: EGREP not exported

Hello Zinx, * Zinx Verituse wrote on Mon, Aug 14, 2006 at 03:27:02AM CEST: > Package: libtool > Version: 1.5.22-4 > > The XMMS package is suffering problems on amd64 due to a libtool problem. > Bug #380318 is being caused by libtool not having EGREP defined anywhere > meaningful. EGREP's already

Bug#382893: acinclude.m4

* Zinx Verituse wrote on Mon, Aug 14, 2006 at 04:52:34PM CEST: > Sorry; I should have paid more attention to which file I was reading. > That came from acinclude.m4, from the debian XMMS package (the m4 is > probably included with xmms), not aclocal.m4. Then the acinclude.m4 file likely contains m

Bug#391427: Link order

is a problem with this change, there have been some reports. Before we release 2.0, we intend to add functionality to choose the desired behavior (with non- global being the default). Cheers, Ralf 2006-10-21 Ralf Wildenhues <[EMAIL PROTECTED]> * tests/link-order2.at: New test.

Bug#418431: libtool: provided m4 files produce autoconf warnings

Hello Guillem, * Guillem Jover wrote on Mon, Apr 09, 2007 at 08:02:29PM CEST: > > When using «autoreconf -fi -Wall» the m4 provided files trigger > autoconf warnings, which is quite annoying as it makes it more > difficult to see what are the warnings on your configure.ac or m4 > files. > > The

Bug#435846: libtool: please support both pgCC and pgcpp alias for the Portland Group C++ compiler

tags: fixed-upstream thanks * Tilman Koschnick wrote on Fri, Aug 03, 2007 at 05:51:29PM CEST: > > the Portland Group C++ compiler has two equivalent names that do the > same: pgCC and pgcpp. libtool currently only supports the former one; it > would be good if you could add support for both versi

Bug#431464: autoconf: files are rebuilt several times on vfat (because "cp -p" can't preserve time?)

Hello Vincent, * Vincent Lefevre wrote on Mon, Jul 09, 2007 at 02:37:19PM CEST: > > On my Zaurus, GCC and some of header files are in a directory mounted > with CRAMFS. The timestamps of these files are meaningless, e.g. > [...] > > As such headers are listed in the .deps/*.Plo files, I probably

Bug#431464: autoconf: files are rebuilt several times on vfat (because "cp -p" can't preserve time?)

* Vincent Lefevre wrote on Mon, Jul 09, 2007 at 09:24:36PM CEST: > On 2007-07-09 18:50:46 +0200, Ralf Wildenhues wrote: > > Why don't you simply > > configure --disable-dependency-tracking > > ? > > Yes, I could do that on the Zaurus (I didn't know this feat

Bug#431464: autoconf: files are rebuilt several times on vfat (because "cp -p" can't preserve time?)

Hello Vincent, * Vincent Lefevre wrote on Tue, Jul 10, 2007 at 08:57:42AM CEST: > > I agree concerning the problems I've reported. But concerning the > "cp -p", is the "-p" useful or just cosmetic? It's useful, as it resembles the functionality it emulates more closely: with symlinked files, 'ma

Bug#407079: libtool: All GNU targets support -Wl, --version-script

* Kurt Roeckx wrote on Mon, Jan 29, 2007 at 09:46:51PM CET: > > I was waiting for a new upstream version of libtool, but I guess I'll > backport some of the fixes. I'm in the process of what will hopefully be the last few patches on the way to 1.5.24. I've got 3 more in the queue, pending more i

Bug#366248: man_MANS without effect

Hi Daniel, * Daniel Leidert wrote on Sat, May 06, 2006 at 03:26:06PM CEST: > Package: automake1.9 > Version: 1.9.6-4 > I may be wrong, but only using man_MANS has no effect on the resulting > Makefile. The related targets are not created. When I instead use > > manx_MANS (x=0-9) > > the resulti

Bug#366248: man_MANS without effect

* Daniel Leidert wrote on Sat, May 06, 2006 at 05:13:27PM CEST: > Am Samstag, den 06.05.2006, 17:09 +0200 schrieb Daniel Leidert: > > > > As a small example for what I tried: > > > > man_src = \ > > foo.1.xml \ > > bar.1.xml \ > > lib.3.cml > > > > man_MANS = $(patsubst %.xml,%,$(man

Bug#347650: libtool: Incorrect argument reordering

* Josselin Mouette wrote on Tue, Mar 28, 2006 at 12:37:52PM CEST: > Le mercredi 11 janvier 2006 à 22:38 +0100, Ralf Wildenhues a écrit : > > > It looks like libtool likes, when building libraries, to reorder > > > arguments: > > > > Well, yes. It move all th

Bug#347650: libtool: Incorrect argument reordering

* Josselin Mouette wrote on Tue, Mar 28, 2006 at 12:37:52PM CEST: > Le mercredi 11 janvier 2006 à 22:38 +0100, Ralf Wildenhues a écrit : > > > It looks like libtool likes, when building libraries, to reorder > > > arguments: > > > > Well, yes. It move all th

Bug#350989: libtool on alpha causes linking errors when run on AFS

* Juha Jäykkä wrote a while ago: > Building shared libraries on Debian/Alpha does not work when the source is > on AFS, but instead causes a linking error: Erm, could this be what Alexandre is hinting at here: http://gcc.gnu.org/ml/gcc-patches/2006-03/msg01602.html continuing this thread: http://g

Bug#357369: autoconf will accept a nonexistent compiler as the second one checked

Hi Stepan, * Stepan Kasal wrote on Sun, Apr 02, 2006 at 12:04:28AM CEST: > On Mon, Mar 20, 2006 at 05:02:52PM +0100, Ralf Wildenhues wrote: > > * Martin Michlmayr wrote on Mon, Mar 20, 2006 at 02:15:34PM CET: > > > Well, I think in this case some more sanity checks are justified

Bug#161654: autoconf: AC_HELP_STRING get length wrong

* Ben Pfaff wrote on Sat, Sep 21, 2002 at 05:41:02AM CEST: > The following bug was reported against the Debian package for > Autoconf 2.53. Based on a diff between 2.53 and 2.54, it appears > that the bug (which I have not personally verified) is also > present in 2.54, so I am forwarding it to th

Bug#281364: [Elrond] Bug#281364: autoconf: configure doesn't show version for --version

* Paul Eggert wrote on Tue, Nov 16, 2004 at 06:58:07PM CET: > Ben Pfaff <[EMAIL PROTECTED]> writes: > > > When the old style of AC_INIT is used (with a single argument > > that indicates a file to check for) recent Autoconf omits > > Autoconf version info from the generated configure's --version >

Bug#222163: autoconf: quoting strings with AC_HELP_STRING

* Roland Illig wrote on Sun, Nov 23, 2003 at 07:25:48PM CET: > Package: autoconf > Version: 2.58-7 > Severity: minor > > When I type > > AC_HELP_STRING([--enable-foo[=value]], [enable foo (default: def)]), > > I expect that a line > > --enable-foo[=value] enable foo (default: def) >

Bug#299860: autoconf: configure scripts fail when path contains a comma

* Will Aoki wrote on Thu, Mar 17, 2005 at 12:49:37AM CET: > Package: autoconf > Version: 2.59a-3 > Severity: normal > > The configure scripts generated by autoconf do not work on paths containing > commas. 'configure' gets almost to the end, then spews: > > sed: -e expression #1, char 322: Unkno

Bug#325866: [Vincent Lefevre] Bug#325866: autoconf: AC_COMPILE_IFELSE generates a test that doesn't work on IRIX64

* Noah Misch wrote on Wed, Sep 07, 2005 at 11:41:42PM CEST: > On Fri, Sep 02, 2005 at 08:17:51AM +0200, Vincent Lefevre wrote: > > > > Would grepping "^ #error directive:" break anything elsewhere? > > That is probably safe, but it adds a fork to every AC_COMPILE_IFELSE. Cygwin > would suffer e

  1   2   >