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 22:16:19 +0200	[thread overview]
Message-ID: <20161005221619.6a958ba0@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LUJOwtpDmUg1zxDdBDKnOAnjkafxwuCAVRQP5aMm3zT9g@mail.gmail.com>

Hello,

On Wed, 5 Oct 2016 22:11:31 +0200, Thomas De Schampheleire wrote:

> I did that now. While I'm still running some more tests, I already
> tested tarball versions 7.10.1 and 7.11.1, and both ARC and Microblaze
> git versions. I currently only tested host-gdb, but for all these
> cases I can get rid of the host-texinfo dependency with following
> extra changes:
> 
> GDB_INSTALL_OPTS += MAKEINFO=true
> GDB_MAKE_OPTS += MAKEINFO=true
> HOST_GDB_INSTALL_OPTS += MAKEINFO=true
> HOST_GDB_MAKE_OPTS += MAKEINFO=true
> 
> The INSTALL_OPTS were needed for the tarball versions, while the
> MAKE_OPTS (and perhaps also the INSTALL_OPTS, not sure) for the git
> versions.

OK.

> I still need to test the (target-)gdb, but I guess it won't make a
> difference as the Makefiles are the same.

Worth testing to check that everything is alright.

> Is this too simplistic? Am I missing something?

If it works, then all good.

Note that for binutils, we have a different work-around: we touch
all .info files so that they have a date that is later than the source
files they are generated from. But that only works for tarball releases
(that contain .info files). For binutils fetched from Git, we depend on
host-texinfo.

Best regards,

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

  reply	other threads:[~2016-10-05 20:16 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
2016-10-05 20:11   ` Thomas De Schampheleire
2016-10-05 20:16     ` Thomas Petazzoni [this message]
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=20161005221619.6a958ba0@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.