Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] toolchain-external: fix C++ build issues with the Blackfin toolchain
Date: Sun, 23 Nov 2014 19:03:31 +0100	[thread overview]
Message-ID: <20141123180331.GG11143@free.fr> (raw)
In-Reply-To: <20141123185637.5c00ad44@free-electrons.com>

Thomas, All,

On 2014-11-23 18:56 +0100, Thomas Petazzoni spake thusly:
> On Sun, 23 Nov 2014 18:54:30 +0100, Yann E. MORIN wrote:
> > On 2014-11-23 18:35 +0100, Thomas Petazzoni spake thusly:
> > > The Blackfin toolchain install some libtool .la files, which none of
> > > the other toolchains seem to do,
> > 
> > Well, with my crostool-NG toolchains, I have some, for example:
[--SNIP--]
> What do they contain?

    $ cat ./armv6-rpi-linux-gnueabihf/armv6-rpi-linux-gnueabihf/sysroot/lib/libstdc++.la
    # libstdc++.la - a libtool library file
    # Generated by libtool (GNU libtool 1.3134 2009-11-29) 2.2.7a
    #
    # Please DO NOT delete this file!
    # It is necessary for linking the library.

    # The name that we can dlopen(3).
    dlname='libstdc++.so.6'

    # Names of this library.
    library_names='libstdc++.so.6.0.20 libstdc++.so.6 libstdc++.so'

    # The name of the static archive.
    old_library='libstdc++.a'

    # Linker flags that can not go in dependency_libs.
    inherited_linker_flags=''

    # Libraries that this one depends upon.
    dependency_libs=' -lm'

    # Names of additional weak libraries provided by this library
    weak_library_names=''

    # Version information for libstdc++.
    current=6
    age=0
    revision=20

    # Is this an already installed library?
    installed=yes

    # Should we warn about portability when linking against -modules?
    shouldnotlink=no

    # Files to dlopen/dlpreopen
    dlopen=''
    dlpreopen=''

    # Directory that this library needs to be installed in:
    libdir='/home/ymorin/x-tools/armv6-rpi-linux-gnueabihf/armv6-rpi-linux-gnueabihf/lib'

> At least, with the Blackfin toolchain, for some reason, libtool find it
> smart to append the Buildroot sysroot path with the libdir value found
> in the .la file.

What. Wait, did you say 'libtool' and 'smart' in the same sentence? ;-]

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-11-23 18:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-23 17:35 [Buildroot] [PATCH 0/5] Misc autobuilder fixes Thomas Petazzoni
2014-11-23 17:35 ` [Buildroot] [PATCH 1/5] toolchain-external: fix C++ build issues with the Blackfin toolchain Thomas Petazzoni
2014-11-23 17:54   ` Yann E. MORIN
2014-11-23 17:56     ` Thomas Petazzoni
2014-11-23 18:03       ` Yann E. MORIN [this message]
2014-11-23 17:36 ` [Buildroot] [PATCH 2/5] mpdecimal: fix build on pure static library configurations Thomas Petazzoni
2014-11-23 18:00   ` Yann E. MORIN
2014-11-23 17:36 ` [Buildroot] [PATCH 3/5] ushare: do not allow building in static lib situations Thomas Petazzoni
2014-11-23 18:18   ` Yann E. MORIN
2014-11-23 17:36 ` [Buildroot] [PATCH 4/5] radvd: switch to new patch naming convention, use Git formatted patches Thomas Petazzoni
2014-11-23 18:22   ` Yann E. MORIN
2014-11-23 17:36 ` [Buildroot] [PATCH 5/5] radvd: add a patch to fix build failure on architectures without sysctl() Thomas Petazzoni
2014-11-23 18:25   ` Yann E. MORIN
2014-11-24 21:06 ` [Buildroot] [PATCH 0/5] Misc autobuilder fixes Thomas Petazzoni

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=20141123180331.GG11143@free.fr \
    --to=yann.morin.1998@free.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