Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Target/full GDB fails to build statically
Date: Thu, 20 Aug 2015 22:37:54 +0200	[thread overview]
Message-ID: <20150820223754.7540ee29@free-electrons.com> (raw)
In-Reply-To: <4881796E12491D4BB15146FE0209CE6465785322@DE02WEMBXB.internal.synopsys.com>

Dear Alexey Brodkin,

On Thu, 20 Aug 2015 13:10:25 +0000, Alexey Brodkin wrote:

> And that's what I see in the very end:
> ----------------->8-----------------
> linux-thread-db.c:23:19: fatal error: dlfcn.h: No such file or directory
>  #include <dlfcn.h>
>                    ^
> compilation terminated.
> Makefile:1078: recipe for target 'linux-thread-db.o' failed
> make[4]: *** [linux-thread-db.o] Error 1
> make[4]: *** Waiting for unfinished jobs....
> Makefile:8335: recipe for target 'all-gdb' failed
> make[3]: *** [all-gdb] Error 2
> Makefile:832: recipe for target 'all' failed
> make[2]: *** [all] Error 2
> ----------------->8-----------------
> 
> Seeing that GDB is not disabled in case of BR2_STATIC_LIBS=y I had a hope it could
> be built. But looks like something is broken.
> 
> I tried the same for ARC (where we use pretty recent gdb 7.9.1) and got exactly
> the same result.
> 
> If BR2_PACKAGE_GDB_DEBUGGER is disabled gdbserver gets built perfectly fine.
> ----------------->8-----------------
> $ file build/gdb-7.8.2/gdb/gdbserver/gdbserver 
> build/gdb-7.8.2/gdb/gdbserver/gdbserver: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, not stripped
> ----------------->8-----------------
> 
> So whether we need to disable building of target/full gdb statically or somebody will need to look into it.
> Given close relese of 2015.08 we may want to implement a former approach.

I believe we should mark the full gdb as requiring dynamic library
support. Maybe with threads disabled, dynamic library support is not
mandatory. But I don't think it's really worth the effort: if you want
to do static only, you have tight requirements and you probably can't
fit a full-blown gdb on your target.

So a patch making full gdb "depends on !BR2_STATIC_LIBS" would be fine
for me.

Best regards,

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

      reply	other threads:[~2015-08-20 20:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 13:10 [Buildroot] Target/full GDB fails to build statically Alexey Brodkin
2015-08-20 20:37 ` Thomas Petazzoni [this message]

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=20150820223754.7540ee29@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox