Public bug reported:
Hi,
My "libtool" script in a random project (gtk+) was full of "^A" chars
(\001); examining the build log, I could see that some Makefile.in.in
would call: $(SHELL) ./config.status
I confirmed that after ./configure, libtool was ok (no ^A), but after
"/bin/sh config.status" it was broken (with ^A). /bin/dash gives the
same result, /bin/bash and /bin/zsh work fine.
I'm not sure that this is a dash regression, it could also be a new
autoconf.
NB: I think the Makefile.in.in shouldn't have to use $(SHELL), but there
are so many weird usages that I don't think I care to fight, also this
is in at least gettext, intltool, glib, and copied in some custom
Makefile.in.in (such as gtk+/po-properties/Makefile.in.in); I don't
think it's worth fighting not to use $(SHELL) to call config.status --
even if config.status is +x and has a shebang generated at configure
time.
Bye
** Affects: autoconf (Ubuntu)
Importance: High
Status: New
** Affects: dash (Ubuntu)
Importance: High
Status: New
** Changed in: dash (Ubuntu)
Importance: Undecided => High
** Also affects: autoconf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: autoconf (Ubuntu)
Importance: Undecided => High
--
$(SHELL) config.status broken
https://bugs.launchpad.net/bugs/332840
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
