GNU bug report logs -
#33779
Wrong lib-list in install-%DIR%LTLIBRARIES
Previous Next
To reply to this bug, email your comments to 33779 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-automake <at> gnu.org
:
bug#33779
; Package
automake
.
(Mon, 17 Dec 2018 19:13:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Bert Wesarg <bert.wesarg <at> googlemail.com>
:
New bug report received and forwarded. Copy sent to
bug-automake <at> gnu.org
.
(Mon, 17 Dec 2018 19:13:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
All,
looking at lib/am/ltlib.am, the rule for installing libraries looks
weird for the !LIBTOOL case. Though I have the impression that this
file should not be used at all, if libtool is not used. Nevertheless,
the install command in this cases uses the $list variable, not the
sanitized $list2 variable. A simple patch looks like:
diff --git i/lib/am/ltlib.am w/lib/am/ltlib.am
index 1cbf7192e..2ac157472 100644
--- i/lib/am/ltlib.am
+++ w/lib/am/ltlib.am
@@ -49,8 +49,8 @@ if %?BASE%
## permissions to use.
?LIBTOOL? echo " $(LIBTOOL) $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS)
--mode=install $(INSTALL) $(INSTALL_STRIP_FLAG) $$list2
'$(DESTDIR)$(%NDIR%dir)'"; \
?LIBTOOL? $(LIBTOOL) $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS)
--mode=install $(INSTALL) $(INSTALL_STRIP_FLAG) $$list2
"$(DESTDIR)$(%NDIR%dir)"; \
-?!LIBTOOL? echo " $(INSTALL) $(INSTALL_STRIP_FLAG) $$list
'$(DESTDIR)$(%NDIR%dir)'"; \
-?!LIBTOOL? $(INSTALL) $(INSTALL_STRIP_FLAG) $$list
"$(DESTDIR)$(%NDIR%dir)"; \
+?!LIBTOOL? echo " $(INSTALL) $(INSTALL_STRIP_FLAG) $$list2
'$(DESTDIR)$(%NDIR%dir)'"; \
+?!LIBTOOL? $(INSTALL) $(INSTALL_STRIP_FLAG) $$list2
"$(DESTDIR)$(%NDIR%dir)"; \
}
else !%?BASE%
@list='$(%DIR%_LTLIBRARIES)'; test -n "$(%NDIR%dir)" || list=; \
Best,
Bert
Information forwarded
to
bug-automake <at> gnu.org
:
bug#33779
; Package
automake
.
(Fri, 13 Jan 2023 05:58:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 33779 <at> debbugs.gnu.org (full text, mbox):
On Mon, 17 Dec 2018 20:11:48 +0100, Bert Wesarg wrote:
> looking at lib/am/ltlib.am, the rule for installing libraries looks
> weird for the !LIBTOOL case. Though I have the impression that this
> file should not be used at all, if libtool is not used. Nevertheless,
> the install command in this cases uses the $list variable, not the
> sanitized $list2 variable. A simple patch looks like:
i agree it looks funky. do you have an example of where this fails ?
how did you discover the bug ? we'd want to write a test for it so we
can be sure it doesn't fail again.
-mike
Information forwarded
to
bug-automake <at> gnu.org
:
bug#33779
; Package
automake
.
(Mon, 23 Jan 2023 09:40:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 33779 <at> debbugs.gnu.org (full text, mbox):
On Fri, Jan 13, 2023 at 6:58 AM Mike Frysinger <vapier <at> gentoo.org> wrote:
>
> On Mon, 17 Dec 2018 20:11:48 +0100, Bert Wesarg wrote:
> > looking at lib/am/ltlib.am, the rule for installing libraries looks
> > weird for the !LIBTOOL case. Though I have the impression that this
> > file should not be used at all, if libtool is not used. Nevertheless,
> > the install command in this cases uses the $list variable, not the
> > sanitized $list2 variable. A simple patch looks like:
>
> i agree it looks funky. do you have an example of where this fails ?
> how did you discover the bug ? we'd want to write a test for it so we
> can be sure it doesn't fail again.
No, I don't have one. It just crossed my eyes while working on more
silent rules in Automake. I made Ben recently aware of these changes,
which are availalbe here:
https://github.com/bertwesarg/automake/commits/more-and-colorful-silence
and also Autoconf is now more colorful:
https://github.com/bertwesarg/autoconf/commits/color
Bert
> -mike
>
>
>
Information forwarded
to
bug-automake <at> gnu.org
:
bug#33779
; Package
automake
.
(Mon, 23 Jan 2023 14:29:01 GMT)
Full text and
rfc822 format available.
Message #14 received at submit <at> debbugs.gnu.org (full text, mbox):
On Mon, Jan 23, 2023, at 4:38 AM, Bert Wesarg via Bug reports for Automake wrote:
> On Fri, Jan 13, 2023 at 6:58 AM Mike Frysinger <vapier <at> gentoo.org> wrote:
> No, I don't have one. It just crossed my eyes while working on more
> silent rules in Automake. I made Ben recently aware of these changes,
> which are availalbe here:
>
> https://github.com/bertwesarg/automake/commits/more-and-colorful-silence
>
> and also Autoconf is now more colorful:
>
> https://github.com/bertwesarg/autoconf/commits/color
Both of those URLs are 404 for me.
FYI, with my Autoconf hat on, I will not be inclined to take patches that hardcode "ANSI" terminal control codes. $TERM must be honored in detail. The easiest way to do that is probably to probe for the existence of the `tput` command and then use that to set shell variables with all the necessary control codes. When working on patches for Automake, also keep in mind that $TERM might change between "./configure" and "make".
zw
Information forwarded
to
bug-automake <at> gnu.org
:
bug#33779
; Package
automake
.
(Tue, 24 Jan 2023 06:08:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 33779 <at> debbugs.gnu.org (full text, mbox):
On Mon, Jan 23, 2023 at 3:29 PM Zack Weinberg <zack <at> owlfolio.org> wrote:
>
> On Mon, Jan 23, 2023, at 4:38 AM, Bert Wesarg via Bug reports for Automake wrote:
> > On Fri, Jan 13, 2023 at 6:58 AM Mike Frysinger <vapier <at> gentoo.org> wrote:
> > No, I don't have one. It just crossed my eyes while working on more
> > silent rules in Automake. I made Ben recently aware of these changes,
> > which are availalbe here:
> >
> > https://github.com/bertwesarg/automake/commits/more-and-colorful-silence
> >
> > and also Autoconf is now more colorful:
> >
> > https://github.com/bertwesarg/autoconf/commits/color
>
> Both of those URLs are 404 for me.
Its now public.
>
> FYI, with my Autoconf hat on, I will not be inclined to take patches that hardcode "ANSI" terminal control codes. $TERM must be honored in detail. The easiest way to do that is probably to probe for the existence of the `tput` command and then use that to set shell variables with all the necessary control codes. When working on patches for Automake, also keep in mind that $TERM might change between "./configure" and "make".
It reuses the color setting code from lib/am/check.am, which is
already in use. And autoconf has its own logic copied into m4sh.m4. So
the decision is independent
Bert
Information forwarded
to
bug-automake <at> gnu.org
:
bug#33779
; Package
automake
.
(Tue, 24 Jan 2023 06:15:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 33779 <at> debbugs.gnu.org (full text, mbox):
Full disclosure: the most controversial change in behavior is probably
the removal of batch processing files at install time, or maybe also
other times, to get for each file a colored silent rule output.. JAVAC
is the exception, as all .java files needs to passed at once to the
compiler.
On Tue, Jan 24, 2023 at 7:06 AM Bert Wesarg <bert.wesarg <at> googlemail.com> wrote:
>
> On Mon, Jan 23, 2023 at 3:29 PM Zack Weinberg <zack <at> owlfolio.org> wrote:
> >
> > On Mon, Jan 23, 2023, at 4:38 AM, Bert Wesarg via Bug reports for Automake wrote:
> > > On Fri, Jan 13, 2023 at 6:58 AM Mike Frysinger <vapier <at> gentoo.org> wrote:
> > > No, I don't have one. It just crossed my eyes while working on more
> > > silent rules in Automake. I made Ben recently aware of these changes,
> > > which are availalbe here:
> > >
> > > https://github.com/bertwesarg/automake/commits/more-and-colorful-silence
> > >
> > > and also Autoconf is now more colorful:
> > >
> > > https://github.com/bertwesarg/autoconf/commits/color
> >
> > Both of those URLs are 404 for me.
>
> Its now public.
>
> >
> > FYI, with my Autoconf hat on, I will not be inclined to take patches that hardcode "ANSI" terminal control codes. $TERM must be honored in detail. The easiest way to do that is probably to probe for the existence of the `tput` command and then use that to set shell variables with all the necessary control codes. When working on patches for Automake, also keep in mind that $TERM might change between "./configure" and "make".
>
> It reuses the color setting code from lib/am/check.am, which is
> already in use. And autoconf has its own logic copied into m4sh.m4. So
> the decision is independent
>
> Bert
Information forwarded
to
bug-automake <at> gnu.org
:
bug#33779
; Package
automake
.
(Tue, 24 Jan 2023 13:06:01 GMT)
Full text and
rfc822 format available.
Message #23 received at 33779 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 24 Jan 2023 07:06, Bert Wesarg via Bug reports for Automake wrote:
> On Mon, Jan 23, 2023 at 3:29 PM Zack Weinberg <zack <at> owlfolio.org> wrote:
> > On Mon, Jan 23, 2023, at 4:38 AM, Bert Wesarg via Bug reports for Automake wrote:
> > > On Fri, Jan 13, 2023 at 6:58 AM Mike Frysinger <vapier <at> gentoo.org> wrote:
> > > No, I don't have one. It just crossed my eyes while working on more
> > > silent rules in Automake. I made Ben recently aware of these changes,
> > > which are availalbe here:
> > >
> > > https://github.com/bertwesarg/automake/commits/more-and-colorful-silence
> > >
> > > and also Autoconf is now more colorful:
> > >
> > > https://github.com/bertwesarg/autoconf/commits/color
> >
> > Both of those URLs are 404 for me.
>
> Its now public.
feel free to send commits to automake-patches <at> gnu.org via `git am` for review.
although if you haven't signed FSF copyright papers, we'll want that first.
-mike
[signature.asc (application/pgp-signature, inline)]
This bug report was last modified 2 years and 140 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.