public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Stefan Hallas Mulvad <shm@hallas.nu>
To: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: GDB build failure from tip
Date: Tue, 26 Jul 2016 22:57:00 -0000	[thread overview]
Message-ID: <016D099B-EDBA-4F00-89B4-0BC50E95A99E@hallas.nu> (raw)
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C6EE86C05B@ex-mb1.corp.adtran.com>


[-- Attachment #1.1: Type: text/plain, Size: 328 bytes --]

It be great if you could post your build.log, or at least some more information from it.

A while back I faced a, what seams to be, similar issue. I proposed a patch which was rejected, however we use it at work and I know it has worked for several other people so give it a try.

Hope it works,

Best regards,
Stefan


[-- Attachment #1.2: 0001-Fixes-configure-error-expat-is-missing-or-unusable-w.patch --]
[-- Type: application/octet-stream, Size: 780 bytes --]

From 1d691f41aece8a5226b6da9f2507da66fe63ec3c Mon Sep 17 00:00:00 2001
From: Stefan Hallas Mulvad <shm@hallas.nu>
Date: Fri, 5 Feb 2016 00:04:43 -0800
Subject: [PATCH] Fixes 'configure: error: expat is missing or unusable' when
 native gdb is enabled

---
 scripts/build/debug/300-gdb.sh | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/build/debug/300-gdb.sh b/scripts/build/debug/300-gdb.sh
index 418e85c..4ede7b6 100644
--- a/scripts/build/debug/300-gdb.sh
+++ b/scripts/build/debug/300-gdb.sh
@@ -162,6 +162,7 @@ do_debug_gdb_build() {
         fi
 
         native_extra_config+=("--with-expat")
+        native_extra_config+=("--with-libexpat-prefix=${CT_SYSROOT_DIR}/usr")
 
         CT_DoLog EXTRA "Configuring native gdb"
 
-- 
2.7.3


[-- Attachment #1.3: Type: text/plain, Size: 865 bytes --]




> On Jul 26, 2016, at 3:46 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
> 
> configure error:  expat is missing or unusable
> 
> After digging into it for a couple of hours, I found that this message
> was a red herring.  This message comes from the native GDB build.
> 
> As it stands, it appears that the CC for the two builds are SWAPPED:
> 
> ~/base_layer/build/toolchain/mips64/crosstool-ng$ file .build/mips64-LinuxBSP-linux-gnu/build/build-gdb-cross/gdb/gdb
> .build/mips64-LinuxBSP-linux-gnu/build/build-gdb-cross/gdb/gdb: ELF 64-bit LSB  executable, x86-64, version 1 (GNU/Linux), statically linked, not stripped
> 
> Unless I way off (please let me know if that is the case), I'll be
> sending a patch file for this fix tomorrow.
> 
> Andy
> 
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
> 


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]

  reply	other threads:[~2016-07-26 22:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 22:46 ANDY KENNEDY
2016-07-26 22:57 ` Stefan Hallas Mulvad [this message]
2016-07-26 23:04   ` ANDY KENNEDY
2016-07-27  0:13     ` ANDY KENNEDY
2016-07-27 17:32       ` ANDY KENNEDY
2016-07-27 18:11         ` Stefan Hallas Mulvad
2016-07-27 20:19           ` ANDY KENNEDY

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=016D099B-EDBA-4F00-89B4-0BC50E95A99E@hallas.nu \
    --to=shm@hallas.nu \
    --cc=ANDY.KENNEDY@adtran.com \
    --cc=crossgcc@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).