Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ARC: bump tools to 2014.12 release
Date: Mon, 06 Apr 2015 22:29:18 +0200	[thread overview]
Message-ID: <5522EC9E.60306@openwide.fr> (raw)
In-Reply-To: <5521AED9.5030802@openwide.fr>

Hi Alexey,

Le 05/04/2015 23:53, Romain Naour a ?crit :
> Hi Alexey,
> 
> Le 24/03/2015 17:03, Alexey Brodkin a ?crit :
>> Hi Thomas,
>>
>> On Tue, 2015-03-24 at 16:31 +0100, Thomas Petazzoni wrote:
>>> Dear Alexey Brodkin,
>>>
>>> On Tue, 24 Mar 2015 13:51:08 +0000, Alexey Brodkin wrote:
>>>
>>>> On Fri, 2015-03-13 at 10:10 +0100, Romain Naour wrote:
>>>>> Hi Alexey,
>>>>>
>>>>> ----- Mail original -----
>>>>> | De: "Alexey Brodkin" <Alexey.Brodkin@synopsys.com>
>>>>> | ?: "romain naour" <romain.naour@openwide.fr>, "thomas petazzoni" <thomas.petazzoni@free-electrons.com>
>>>>> | Cc: buildroot at uclibc.org
>>>>> | Envoy?: Vendredi 13 Mars 2015 10:00:34
>>>>> | Objet: Re: [Buildroot] [PATCH] ARC: bump tools to 2014.12 release
>>>>> | 
>>>>> | On Fri, 2015-03-13 at 09:19 +0100, Romain Naour wrote:
>>>>> | > Hi Alexey,
>>>>> | > Can you have a look at this patch:
>>>>> | > https://patchwork.ozlabs.org/patch/449686/
>>>>
>>>> Do you think the patch Romain mentioned may fix
>>>> http://autobuild.buildroot.org/results/d62/d62f472d70f60281dfe94cffc46a3e0566fd4a3d ?
>>>
>>> Yes, most likely it will fix this problem.
>>
>> Are you going to apply it or we'll need to find somebody to try it
>> first?
>>
> 
> I'm back on this issue and I found a way to reproduce it.
> 
> As you can see in the build.log, libiberty.a is located in host/usr/lib/libiberty.a
> But on my machine libiberty.a is located in host/usr/lib64/libiberty.a
> 
> This is really weird because autobuilders are also 64bits machine
> (x86_64-unknown-linux-gnu) and there is no reason that libiberty.a is not in the
> same place...
> So, I moved libiberty.a from host/usr/lib64/libiberty.a to
> host/usr/lib/libiberty.a and now I have the very same build failure.

This issue reminds me the issue related to config.site import while
cross-compiling...
See:
http://git.buildroot.net/buildroot/commit/?id=f8d4fe376cf65cc4e41423804869a79c2570f674

I think the CONFIG_SITE=/dev/null setting is not taken into account somewhere
(binutils or gcc) and the /usr/share/config.site file is sourced.
So the libdir value is changed lib64 and that is why libiberty.a is installed to
host/usr/lib64.

I'm able to reproduce easily the issue on a debian 64bits and not on a Fedora 21
64bits.

Best regards,
Romain

> 
> When gdb is build with shared libraries, it try to link with it own libiberty.a
> (host-gdb-7.8.2/bfd/../libiberty/pic -liberty) but it take the one from
> host/usr/lib/libiberty.a because -LPath/to/host/usr/lib/libiberty.a is before
> -LPath/to/build/host-gdb-7.8.2/bfd/../libiberty/pic.
> 
> See the complete gcc line (verbose):
> /bin/sh ./libtool --tag=CC   --mode=link /usr/bin/gcc -W -Wall
> -Wstrict-prototypes -Wmissing-prototypes -Wshadow -O2
> -I/home/naourr/git/buildroot/test/gdb/host/usr/include  -release `cat
> libtool-soversion`  -L/home/naourr/git/buildroot/test/gdb/host/lib
> -L/home/naourr/git/buildroot/test/gdb/host/usr/lib
> -Wl,-rpath,/home/naourr/git/buildroot/test/gdb/host/usr/lib -o libbfd.la -rpath
> /home/naourr/git/buildroot/test/gdb/host/usr/x86_64-unknown-linux-gnu/arm-buildroot-linux-uclibcgnueabi/lib
> archive.lo archures.lo bfd.lo bfdio.lo bfdwin.lo cache.lo coffgen.lo corefile.lo
> format.lo init.lo libbfd.lo opncls.lo reloc.lo section.lo syms.lo targets.lo
> hash.lo linker.lo srec.lo binary.lo tekhex.lo ihex.lo stabs.lo stab-syms.lo
> merge.lo dwarf2.lo simple.lo compress.lo verilog.lo `cat ofiles`
> -L/home/naourr/git/buildroot/test/gdb/build/host-gdb-7.8.2/bfd/../libiberty/pic
> -liberty -Wl,-lc,--as-needed,-lm,--no-as-needed  -lz
> 
> This line come from gdb/bfd/Makefile.in: l1239:
> libbfd.la: $(libbfd_la_OBJECTS) $(libbfd_la_DEPENDENCIES)
> 	$(libbfd_la_LINK) $(am_libbfd_la_rpath) $(libbfd_la_OBJECTS)
> $(libbfd_la_LIBADD) $(LIBS)
> 
> One solution is to disable shared libraries (preferred).
> 
> The second is to tweak LDFLAGS in gdb.mk like this:
> HOST_GDB_CONF_OPTS = \
> 	[...]
> 	LDFLAGS="-L$(@D)/bfd/../libiberty/pic $(HOST_LDFLAGS)"
> 
> I don't see a better fix for gdb.
> 
> Best regards,
> Romain
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

      reply	other threads:[~2015-04-06 20:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 12:19 [Buildroot] [PATCH] ARC: bump tools to 2014.12 release Alexey Brodkin
2015-02-02 20:28 ` Thomas Petazzoni
2015-03-04 11:03 ` Thomas Petazzoni
2015-03-13  7:18   ` Alexey Brodkin
2015-03-13  8:19     ` Romain Naour
2015-03-13  9:00       ` Alexey Brodkin
2015-03-13  9:10         ` Romain Naour
2015-03-24 13:51           ` Alexey Brodkin
2015-03-24 15:31             ` Thomas Petazzoni
2015-03-24 16:03               ` Alexey Brodkin
2015-04-05 21:53                 ` Romain Naour
2015-04-06 20:29                   ` Romain Naour [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=5522EC9E.60306@openwide.fr \
    --to=romain.naour@openwide.fr \
    --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