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] [PATCH] ncurses: remove BR2_PACKAGE_NCURSES_TARGET_{FORM, MENU, PANEL} options
Date: Thu, 23 Feb 2017 09:43:42 +0100	[thread overview]
Message-ID: <20170223094342.2072de65@free-electrons.com> (raw)
In-Reply-To: <20170222211702.GB3569@free.fr>

Hello,

On Wed, 22 Feb 2017 22:17:02 +0100, Yann E. MORIN wrote:

> Impressive xommit log. Great! :-)

Thanks!

> >  NCURSES_POST_INSTALL_STAGING_HOOKS += NCURSES_LINK_STAGING_LIBS
> >  NCURSES_POST_INSTALL_STAGING_HOOKS += NCURSES_LINK_STAGING_PC
> > +NCURSES_POST_INSTALL_TARGET_HOOKS += NCURSES_LINK_TARGET_LIBS  
> 
> Would do you need to create the symlinks in target/ ?
> 
> When a program (or lib) is linked to a library, its DT_SONAME is used,
> not the filename.
> 
> So if you have this chain of symlink, with the last element being an
> actual file:
> 
>     libform.so -> libformw.so -> libformw.so.6 -> libformw.so.6.0
> 
> Then 'ld -lform' will in fact use the file libformw.so.6.0, extract its
> DT_SONAME, and use that as a DT_NEEDED in the executable.
> 
> In this case, the DT_SONAME is libformw.so.6

Hum, that's right. Those symlinks are not needd. They were here before,
so I just kept them, but you are indeed right.

> Ditto the syminks about the static libs: they are totally useless in
> target/

Well, static libs are not installed at all on the target, so indeed,
symlinks are useless.

Thanks,

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

      reply	other threads:[~2017-02-23  8:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 21:39 [Buildroot] [PATCH] ncurses: remove BR2_PACKAGE_NCURSES_TARGET_{FORM, MENU, PANEL} options Thomas Petazzoni
2017-02-21 22:22 ` Romain Naour
2017-02-22 21:17 ` Yann E. MORIN
2017-02-23  8:43   ` 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=20170223094342.2072de65@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