All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fakeroot: bump version to 1.21-2
Date: Mon, 13 Mar 2017 17:33:06 +0100	[thread overview]
Message-ID: <20170313163306.GA3680@free.fr> (raw)
In-Reply-To: <216f6108-da26-92cc-8177-07117d20092c@andin.de>

Andreas, All,

On 2017-03-13 16:23 +0100, Andreas Naumann spake thusly:
> Am 13.03.2017 um 13:32 schrieb Thomas Petazzoni:
> >Hello,
> >
> >On Mon, 13 Mar 2017 11:43:49 +0100, Andreas Naumann wrote:
> >
> >>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?
> >
> >Is your reason to depend on automake/autoconf still the same as what it
> >was in Maxime's patch?
> I think so, but in order test it I used FAKEROOT_AUTORECONF instead of
> running the bootstrap script. However, that does create the same dependency
> on automake/autoconf right?

I had a look at the diff between 1.20.2 (which we have right now) and
1.21, and the only noticeable delta is the change of a bufgfer size in
mesage.h, the rest of the delta being the removal of the generated
autostuff.

So we can quite safely backport that single change.

I'll send a patch in a moment.

Regards,
Yann E. MORIN.

>  If so, then we can patch Makefile.in instead of
> >Makefile.am. We normally don't like that very much, but I personally
> >prefer this solution over having fakeroot depending on
> >automake/autoconf.
> There is no Makefile.in, only .am and a configure.ac. Wouldnt a patch need
> to add configure + the contents of build-aux as well? Can you point out a
> package that I can use as an example?
> 
> 
> regards,
> Andreas
> 
> 
> >
> >Best regards,
> >
> >Thomas
> >
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2017-03-13 16:33 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
2017-03-13 12:32       ` Thomas Petazzoni
2017-03-13 15:23         ` Andreas Naumann
2017-03-13 16:33           ` Yann E. MORIN [this message]
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=20170313163306.GA3680@free.fr \
    --to=yann.morin.1998@free.fr \
    --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.