All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Naumann <dev@andin.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next v6 07/10] core: implement per-package SDK and target
Date: Thu, 6 Dec 2018 11:21:25 +0100	[thread overview]
Message-ID: <8a886731-26ee-ba33-f303-81d5bd0e7954@andin.de> (raw)
In-Reply-To: <672791f3-4383-cad2-f31c-5362b94b94fb@andin.de>

Hi Thomas,

Am 05.12.18 um 17:52 schrieb Andreas Naumann:
> Hi,
> 
> Am 05.12.18 um 17:31 schrieb Thomas Petazzoni:
>> Hello Andreas,
>>
>> On Wed, 5 Dec 2018 17:08:20 +0100, Andreas Naumann wrote:
>>
>>> In an answer to v4 of this series I mentioned the issue I had with empty
>>> RPATH in some host-lib. After digging some more I found this happens
>>> during the prepare-sdk step (which I call in my wrapper script). Before
>>> this step, your suggested readelf output reports the correct pathes,
>>> however after, RPATH is empty. I compared this to a "standard" SDK,
>>> there RPATH is set to $ORIGIN/../lib or something similar.
>>
>> So are you saying the issue still exists, and to reproduce, I simply
>> need to do:
>>
>> ? $ make
>> ? $ make prepare-sdk
>>
>> of a build with BR2_PER_PACKAGE_DIRECTORIES=y ?
> 
> in an essence that's what I did. My setup has two externals and some 
> custom defconfig, but that shouldnt matter since without the ppsh 
> patches things work fine.

Just to make sure I just did the above using your ppsh-v6 branch with 
the wandboard_defconfig. The only additional change was to use the 
external linaro toolchain. After 'make'
   $ readelf -d output/host/sbin/mkfs.ext3
shows
   0x000000000000001d (RUNPATH)            Bibliothek runpath: 
[/local/gsrc/buildroot.upstream/output/per-package/host-e2fsprogs/host/lib]

which is already unexpected, shouldn't it show .../output/host/lib?
After 'make prepare-sdk'
   $ readelf -d output/host/sbin/mkfs.ext3
shows
   0x000000000000001d (RUNPATH)            Bibliothek runpath: []


regards,
Andreas

> 
>>
>>> Actually, an unrelated question arises: Why does the SDK need to build
>>> world, which includes all filesystem images, first? Should it not be
>>> sufficient to depend on $(PACKAGES) or now host-finalize only?
>>
>> Yes, it would be sufficient to build packages + host-finalization I
>> believe.
> 
> Ok, I might submit a patch in this direction then..
> 
> 
> regards,
> Andreas
> 
>>
>> Best regards,
>>
>> Thomas
>>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

  reply	other threads:[~2018-12-06 10:21 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23 14:58 [Buildroot] [PATCH next v6 00/10] Per-package host/target directory support Thomas Petazzoni
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 01/10] Makefile: evaluate CCACHE and HOST{CC, CXX} at time of use Thomas Petazzoni
2018-11-26 18:14   ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 02/10] support/scripts/check-host-rpath: split condition on two statements Thomas Petazzoni
2018-11-26 18:14   ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 03/10] Makefile: rework main directory creation logic Thomas Petazzoni
2018-11-23 18:07   ` Yann E. MORIN
2018-11-26 18:14   ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 04/10] Makefile: move .NOTPARALLEL statement after including .config file Thomas Petazzoni
2018-11-26 18:15   ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 05/10] Makefile: define TARGET_DIR_WARNING_FILE relative to TARGET_DIR Thomas Petazzoni
2018-11-26 18:15   ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 06/10] package/pkg-generic: adjust config scripts tweaks for per-package directories Thomas Petazzoni
2018-11-23 18:09   ` Yann E. MORIN
2018-11-26 18:15   ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 07/10] core: implement per-package SDK and target Thomas Petazzoni
2018-11-23 21:50   ` Yann E. MORIN
2018-12-04 22:24   ` Arnout Vandecappelle
2018-12-05  8:04     ` Thomas Petazzoni
2018-12-05  9:18       ` Arnout Vandecappelle
2018-12-05  9:44         ` Thomas Petazzoni
2018-12-05 10:41           ` Arnout Vandecappelle
2018-12-05 16:08   ` Andreas Naumann
2018-12-05 16:31     ` Thomas Petazzoni
2018-12-05 16:52       ` Andreas Naumann
2018-12-06 10:21         ` Andreas Naumann [this message]
2018-12-06 10:28           ` Thomas Petazzoni
2018-12-06 10:42             ` Andreas Naumann
2018-12-06 10:58               ` Thomas Petazzoni
2018-12-06 13:31                 ` Andreas Naumann
2018-12-26 17:34           ` Thomas Petazzoni
2018-12-26 18:33             ` Thomas De Schampheleire
2019-01-10 21:25               ` Arnout Vandecappelle
2019-01-11 20:09                 ` Thomas De Schampheleire
2019-01-13 22:10                   ` Arnout Vandecappelle
2019-01-14 16:01                     ` Thomas De Schampheleire
2019-01-14 16:33                       ` Thomas Petazzoni
2019-01-14 20:19                       ` Thomas De Schampheleire
2019-01-14 20:43                         ` Thomas De Schampheleire
2018-12-26 18:58             ` Yann E. MORIN
2018-12-27 16:17             ` Thomas Petazzoni
2019-01-10 21:14               ` Arnout Vandecappelle
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 08/10] Makefile: allow top-level parallel build with BR2_PER_PACKAGE_DIRECTORIES=y Thomas Petazzoni
2018-11-23 18:11   ` Yann E. MORIN
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 09/10] package/pkg-generic: make libtool .la files compatible with per-package directories Thomas Petazzoni
2018-11-25 17:57   ` Yann E. MORIN
2018-11-30 10:20     ` Thomas Petazzoni
2018-12-01 10:59       ` Yann E. MORIN
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 10/10] package/pkg-kconfig: handle KCONFIG_DEPENDENCIES " Thomas Petazzoni
2018-11-25 17:57   ` Yann E. MORIN
2018-12-05 15:23   ` Andreas Naumann
2018-12-06 14:07     ` Andreas Naumann
2018-12-06 14:25       ` Thomas Petazzoni
2018-12-26 16:40       ` 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=8a886731-26ee-ba33-f303-81d5bd0e7954@andin.de \
    --to=dev@andin.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.