All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Naumann <dev@andin.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fakeroot: bump version to 1.21-2
Date: Mon, 13 Mar 2017 11:43:49 +0100	[thread overview]
Message-ID: <d5b7097f-1af5-1130-21b2-fb3c1278a646@andin.de> (raw)
In-Reply-To: <CAGduivwqAtheOrr_J0XWXR-9rjWNwPC9Y0dFCqKyBua+bir0ww@mail.gmail.com>

Hi,

I have another reason to bump to 1.21, but experience the same 
difficulties in getting the configure step right. What would be a 
sensible way to avoid depending on autoconf/automake?

Background: I experience file ownership issues when doing a 'cp -a' 
inside fakeroot 1.20.2. I tracked it down to the bump commit (from 
1.18.4). Not sure what is causing it, but I just tried 1.21 and all is 
well again.


regards,
Andreas

Am 04.10.2016 um 16:39 schrieb Maxime Hadjinlian:
> On Tue, Oct 4, 2016 at 4:35 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Hello,
>>
>> On Tue,  4 Oct 2016 13:53:20 +0200, Maxime Hadjinlian wrote:
>>
>>> In this version, the configure and Makefile are not provided so we need
>>> to generate them using the 'bootstrap' script included in the source.
>>
>> This is super annoying.
>>
>> First, your patch is wrong because the bootstrap script most likely
>> needs autoconf and automake, possibly libtool as well, and you haven't
>> added these to the fakeroot dependencies.
>>
>> But above all, it means that you would now be adding the build of
>> autoconf and automake to *every* Buildroot build (since essentially
>> host-fakeroot is always built). This is really annoying.
>>
>> So I'd prefer if we just took the Debian patch that works around the
>> original problem.
> OK, will resend.
>>
>> Best regards,
>>
>> Thomas
>> --
>> Thomas Petazzoni, CTO, Free Electrons
>> Embedded Linux and Kernel engineering
>> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>

  reply	other threads:[~2017-03-13 10:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04 11:53 [Buildroot] [PATCH] fakeroot: bump version to 1.21-2 Maxime Hadjinlian
2016-10-04 14:35 ` Thomas Petazzoni
2016-10-04 14:39   ` Maxime Hadjinlian
2017-03-13 10:43     ` Andreas Naumann [this message]
2017-03-13 12:32       ` Thomas Petazzoni
2017-03-13 15:23         ` Andreas Naumann
2017-03-13 16:33           ` Yann E. MORIN
2017-03-14  8:16             ` Thomas Petazzoni
2017-03-14 11:04               ` Andreas Naumann
2017-03-14 13:48                 ` Andreas Naumann
2017-03-15  0:20                   ` Arnout Vandecappelle
2017-03-15  8:17                     ` Andreas Naumann
2017-03-15 19:07                       ` Arnout Vandecappelle
2017-03-15 19:46                         ` Arnout Vandecappelle
2017-03-15 20:09                           ` Yann E. MORIN
2017-03-15 20:41                             ` Peter Korsgaard
2017-03-15 22:35                               ` Thomas Petazzoni
2017-03-15 22:55                                 ` Peter Korsgaard
2017-03-16  8:13                             ` Andreas Naumann
2017-03-16 22:39                               ` Arnout Vandecappelle

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=d5b7097f-1af5-1130-21b2-fb3c1278a646@andin.de \
    --to=dev@andin.de \
    --cc=buildroot@busybox.net \
    /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.
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.