Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Zakharov <Vladislav.Zakharov@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork cleanup week #24
Date: Fri, 24 Jun 2016 07:24:37 +0000	[thread overview]
Message-ID: <1466753076.30418.15.camel@synopsys.com> (raw)
In-Reply-To: <1466574249.3622.15.camel@synopsys.com>

Hello,?

On Wed, 2016-06-22 at 05:45 +0000, Alexey Brodkin wrote:
> Hi Romain,
> 
> On Sat, 2016-06-18 at 16:07 +0200, Romain Naour wrote:
> > 
> > Hi Thomas, Alexey, Vlad, All,
> > 
> > Le 15/06/2016 ? 22:06, Thomas Petazzoni a ?crit :
> > > 
> > > 
> > > Hello,
> > > 
> > > The previous patchwork cleanup period being over, it's time to start
> > > the second period, with 10 other patches. We're on June 15th, so I'll
> > > give people until June 30th to react on the following patches. If
> > > there's no reaction, like no interest from either the original
> > > submitter nor any other Buildroot developer, the patch will be marked
> > > Rejected on June 30th.
> > > 
> > > If you are in To: of this e-mail, then one or several of the patches
> > > below have been authored by you, so you should be interested :-)
> > > 
> > > Thanks,
> > > 
> > > Thomas
> > > 
> > > ?5. Fix for the makeinfo / missing issue, proposal from Romain
> > > ????http://patchwork.ozlabs.org/patch/595041/
> > > ????http://patchwork.ozlabs.org/patch/595042/
> > > ????http://patchwork.ozlabs.org/patch/595043/
> > > 
> > > ????We need to take a decision on this one. The problem also occurs for
> > > ????gdb and binutils on ARC, for which we've added a custom hack
> > > ????recently.
> > > 
> > > ????I tried to play with timestamps by touch'ing the .info files before
> > > ????the build, it worked with one of gdb or binutils, but failed for
> > > ????the other.
> > > 
> > > ????So either we take Romain's approach, or we bite the bullet and add
> > > ????a host-makeinfo package on which we depend when gdb/binutils are
> > > ????fetched from Git.
> > > 
> > IHMO the real problem is that binutils/gdb doesn't support --disable-docs
> > option. When present on the command line, this option must completely disable
> > the documentation (man, info, pdf etc) and let the build continue.
> > 
> > It seems that this issue was already discussed back in 2007 [1].
> > Last year I submitted a patch upstream to do that but it was not complete and
> > not tested due to autoconf version mismatch [2].
> > 
> > If we want to autoreconf binutils/gdb in Buildroot we must downgrade autoconf to
> > 2.64 and automake to 1.12.6.
> > 
> > Alexey, Vlad, I would suggest to rework your patch [3] and add --disable-docs
> > option instead of testing missing 127 return value.
> > If you succeed, we can reject my proposal from patchwork :)
> Right, that's what we're looking at now.
> Stay tuned and patch(es) will follow :)
> 
> -Alexey

I looked around adding --disable-docs option and faced some difficulties.
Configuration process is rather difficult in binutils.
?* "configure" scripts are generated for each package from corresponding template file.
?* "configure" script is generated from "configure.ac",?
?* "configure" script generates Makefiles from "Makefile.in" files, also it runs "configure" scripts in sub-directories, etc.
?* Build is recursive.?
?* Doc targets for some packages are added to separate directory, for other the are not.

Also I don't have required versions of autoconf (v. 2.64) and automake (v.1.11.6).
It is required to use particular versions to avoid introducing subtle bugs in configure and/or Makefile.in.
For example:
https://sourceware.org/ml/binutils/2013-04/msg00210.html

So implementing this option doesn't seem to be a low-hanging fruit after all.

Returning to the problem. Real issue is that build fails when "makeinfo" is missing on build host.
So a nice and much easier idea is to add "makeinfo" package and make binutils and gdb dependent on the "host-makeinfo" package.

--?
Best regards,
Vlad Zakharov <vzakhar@synopsys.com>

  reply	other threads:[~2016-06-24  7:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 20:06 [Buildroot] Patchwork cleanup week #24 Thomas Petazzoni
     [not found] ` <CAJsd3zJkzAUJhvBPJ9hdQ60YmjSjuB7sahptmLFx6-1V70fLAg@mail.gmail.com>
2016-06-15 21:18   ` Thomas Petazzoni
2016-06-16  7:18 ` Thomas De Schampheleire
2016-06-16  7:32   ` Thomas Petazzoni
2016-06-16  9:52     ` Thomas De Schampheleire
2016-06-16  9:56       ` Thomas Petazzoni
2016-06-16 17:30         ` Yann E. MORIN
2016-06-16 17:23       ` Yann E. MORIN
2016-06-18 20:56         ` Thomas Petazzoni
2016-06-18 14:14 ` Romain Naour
     [not found] ` <4209f432-0fbd-8d44-7194-c99829f66e2e@smile.fr>
2016-06-22  5:45   ` Alexey Brodkin
2016-06-24  7:24     ` Vlad Zakharov [this message]
2016-06-24  7:32       ` Thomas Petazzoni
2016-06-24  9:13         ` Alexey Brodkin
2016-06-24  9:15           ` Thomas Petazzoni
2016-06-24  9:17             ` Alexey Brodkin
2016-07-01  7:59       ` Romain Naour
2016-06-22  6:14 ` Cam Hutchison
2016-06-30 23:51   ` Cam Hutchison
2016-07-01  7:01     ` Thomas Petazzoni
2016-06-22 20:57 ` Arnout Vandecappelle
2016-06-26 11:07 ` Jörg Krause
2016-06-26 12:53   ` Thomas Petazzoni
2016-07-24 20:23 ` Thomas Petazzoni

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=1466753076.30418.15.camel@synopsys.com \
    --to=vladislav.zakharov@synopsys.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox