From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Wed, 5 Oct 2016 17:27:56 +0200 Subject: [Buildroot] gdb texinfo dependency In-Reply-To: References: Message-ID: <20161005172756.77aea89c@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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