All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] gdb texinfo dependency
Date: Wed, 5 Oct 2016 17:27:56 +0200	[thread overview]
Message-ID: <20161005172756.77aea89c@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LUHdDJyUPNcW-vQuZx6RhZxsPrGv69SqRPvRrAy46ropA@mail.gmail.com>

Hello,

On Wed, 5 Oct 2016 17:14:49 +0200, Thomas De Schampheleire wrote:


> I read in the archives that there have been multiple attempts to fix
> it differently, none of which were convincing, but I could not find
> details about these attempts or why they did not work.
> 
> I did find a patch by Romain that is rejected but I could not see why:
> https://patchwork.ozlabs.org/patch/595042/
> It tells gdb to use a different makeinfo command.

IIRC, what I didn't like with this approach is that it requires us to
keep a hacked-up version of the missing script in support/scripts/,
which I really didn't like.

> A similar trick is reported to work in the (still open) upstream bug
> for this issue:
> https://sourceware.org/bugzilla/show_bug.cgi?id=18113
> Essentially, setting MAKEINFO=true when calling the configure script.
> 
> My question is now: what is not working in that approach?

I honestly don't remember exactly :-/

Feel free to try out yourself: create a minimal Debian chroot with
texinfo not installed, and try to build gdb (both tarball versions, and
versions fetched from Git, such as the ones for ARC and Microblaze.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-10-05 15:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05 15:14 [Buildroot] gdb texinfo dependency Thomas De Schampheleire
2016-10-05 15:27 ` Thomas Petazzoni [this message]
2016-10-05 20:11   ` Thomas De Schampheleire
2016-10-05 20:16     ` Thomas Petazzoni
2016-10-05 21:23       ` Romain Naour
2016-10-06 18:57         ` Thomas De Schampheleire
2016-10-06 18:59           ` Thomas De Schampheleire
2016-10-06 19:36             ` Thomas Petazzoni
     [not found]               ` <CAAXf6LUwubkNu9+25LUZyOMchdFfHjYUa5pzdfOF9xYfjzWamA@mail.gmail.com>
     [not found]                 ` <CAAXf6LXcZ2BOc+znu6GQFX3oC=LVAYO=inYGwk83JKHRQR2T-g@mail.gmail.com>
2016-10-06 19:50                   ` Thomas De Schampheleire
2016-10-07 12:21                     ` Thomas Petazzoni
2016-10-07 16:20                       ` Khem Raj
2016-10-07 19:36                         ` Thomas De Schampheleire
2016-10-07 20:18                           ` Thomas Petazzoni
2016-10-07 19:34                       ` Thomas De Schampheleire
2016-10-07 20:19                         ` Thomas Petazzoni
2016-10-05 15:43 ` Khem Raj

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=20161005172756.77aea89c@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 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.