all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: 25304@debbugs.gnu.org
Subject: bug#25304: Libtool’s ltmain.sh still contains a /gnu/store shebang
Date: Fri, 21 Apr 2017 16:30:43 +0200	[thread overview]
Message-ID: <87mvb925po.fsf@gnu.org> (raw)
In-Reply-To: <878tqx7zzj.fsf@gnu.org>

Hi,

Commit 98341757c8c45fca8d2b53f9972f5c6a32cf2c95, which was meant to fix
this bug¹, actually failed to do so:

--8<---------------cut here---------------start------------->8---
$ head -1 $(./pre-inst-env guix build libtool)/share/libtool/build-aux/ltmain.sh
#!/gnu/store/k7029k5va68lkapbzcycdzj7m5bjb4b8-bash-4.4.12/bin/sh
$ git describe
v0.12.0-3136-g7312c62d3
--8<---------------cut here---------------end--------------->8---

I think the problem is that we’re patching ltmain.in when we should
really be patching the final file, after the ‘patch-shebangs’ phase.

Ludo’.

¹ <http://bugs.gnu.org/25304>

  parent reply	other threads:[~2017-04-21 14:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-23 13:35 Seeking advice: preparing releases on GuixSD ng0
2016-12-23 17:04 ` Alex Kost
2016-12-23 17:34   ` ng0
2016-12-24 10:13 ` Ricardo Wurmus
2016-12-24 14:45   ` ng0
2016-12-24 15:32     ` Ricardo Wurmus
2016-12-24 16:13       ` ng0
2016-12-24 16:23         ` Ricardo Wurmus
2016-12-24 16:34           ` ng0
2016-12-26 13:58             ` Ricardo Wurmus
2016-12-26 14:27               ` ng0
2016-12-30 23:34       ` Ludovic Courtès
2017-01-31 21:03         ` bug#25304: " Ludovic Courtès
2017-04-21 14:30         ` Ludovic Courtès [this message]
2020-11-13 15:32           ` bug#25304: Libtool’s ltmain.sh still contains a /gnu/store shebang Miguel Ángel Arruga Vivas
2020-11-15 11:08             ` Ludovic Courtès
2020-11-16 16:17               ` Miguel Ángel Arruga Vivas
2016-12-24 22:26   ` Seeking advice: preparing releases on GuixSD ng0
2016-12-25 12:37     ` Ricardo Wurmus
2016-12-26 12:41       ` ng0

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mvb925po.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=25304@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.