unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Eric Bavier <ericbavier@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] utils: Clean trailing whitespace at end of SHELL
Date: Fri, 05 Sep 2014 10:11:33 +0200	[thread overview]
Message-ID: <87ha0m32ru.fsf@gnu.org> (raw)
In-Reply-To: <878uly3beg.fsf@gmail.com> (Eric Bavier's message of "Fri, 05 Sep 2014 00:05:10 -0500")

Eric Bavier <ericbavier@gmail.com> skribis:

> Ludovic Courtès writes:
>
>> Eric Bavier <ericbavier@gmail.com> skribis:
>>
>>> I found an unfortunate bug in the last patch I made to
>>> patch-makefile-SHELL that would leave a trailing ' ' at the end of SHELL
>>> assignments.  This is fine for most packages, but caused
>>> gobject-introspection to fail building for me just now (for the curious:
>>> it effectively does an "(apply system* (string-split (string-append SHELL
>>> " " "./libtool") #\space))" which causes sh to try to execute "")
>>
>> AFAIK trailing whitespace in assignments is ignored by ‘make’.
>>
>> I grepped gobject-introspection out of curiosity and couldn’t find any
>> suspicious SHELL assignment.  Do you still have it around?
>
> E.g. gobject-introspection-1.38.0/giscanner/utils.py:124

Oh, I see.

>> The (string=? args "\n") seems specific and non-obvious.
>
> I thought so too.  Your suggestion does work.  With this patch, I was
> able to bootstrap and build gobject-introspection.
>
>
> From 11459384968f654c42ad7dba4443dada35191f5b Mon Sep 17 00:00:00 2001
> From: Eric Bavier <bavier@member.fsf.org>
> Date: Thu, 4 Sep 2014 09:19:24 -0500
> Subject: [PATCH] utils: Clean trailing whitespace at end of SHELL
>
> * guix/build/utils.scm (patch-makefile-SHELL): Remove trailing whitespace.

OK to commit!

Thanks,
Ludo’.

      reply	other threads:[~2014-09-05  8:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 14:27 [PATCH] utils: Clean trailing whitespace at end of SHELL Eric Bavier
2014-09-04 19:31 ` Ludovic Courtès
2014-09-05  5:05   ` Eric Bavier
2014-09-05  8:11     ` Ludovic Courtès [this message]

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87ha0m32ru.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=ericbavier@gmail.com \
    --cc=guix-devel@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).