From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 6/7] arch: Introduce blackfin-specific Makefile
Date: Sun, 7 Apr 2013 23:41:29 +0200 [thread overview]
Message-ID: <20130407234129.60c6ac9d@skate> (raw)
In-Reply-To: <1364550643-11793-6-git-send-email-sonic.adi@gmail.com>
Dear Sonic Zhang,
On Fri, 29 Mar 2013 17:50:42 +0800, Sonic Zhang wrote:
> +config BR2_BFIN_INSTALL_FDPIC_SHARED
> + depends on BR2_bfin && !BR2_BINFMT_FDPIC
> + bool "Install FDPIC shared libraries"
> + default y
Any reason to have this default to y ?
> + help
> + Blackfin Linux kernel supports running both FDPIC and FLAT applications
The Blackfin Linux kernel ...
> + concurrently if the binary format specific libraries installed properly.
are installed properly.
> + This option allow developer to install FDPIC libraries into a buildroot
allows the developer
> + rootfs image built with binary format macro other than BR2_BINFMT_FDPIC.
built with a binary format that is not FDPIC.
> +
> +config BR2_BFIN_INSTALL_FLAT_SHARED
> + depends on BR2_bfin && !BR2_BINFMT_FLAT_SHARED
> + bool "Install FLAT shared libraries"
> + default y
> + help
> + Blackfin Linux kernel supports running both FDPIC and FLAT applications
> + concurrently if the binary format specific libraries installed properly.
> + This option allow developer to install FLAT libraries into a buildroot
> + rootfs image built with binary format macro other than
> + BR2_BINFMT_FLAT_SHARED.
Same typos.
> diff --git a/arch/Makefile.in.bfin b/arch/Makefile.in.bfin
> new file mode 100644
> index 0000000..9089bc5
> --- /dev/null
> +++ b/arch/Makefile.in.bfin
> @@ -0,0 +1,22 @@
> +TARGETS_BFIN-$(BR2_BFIN_INSTALL_FDPIC_SHARED) += target-shared-libs-fdpic
> +TARGETS_BFIN-$(BR2_BFIN_INSTALL_FLAT_SHARED) += target-shared-libs-flat
> +TARGETS += $(TARGETS_BFIN-y)
> +
> +CROSS_COMPILE_SHARED_FDPIC ?= bfin-linux-uclibc-
> +target-shared-libs-fdpic:
> + set -e; \
> + t=`$(CROSS_COMPILE_SHARED_FDPIC)gcc $(CPUFLAGS) -print-file-name=libc.a`; \
> + t=`dirname $$t`/../..; \
> + for i in $$t/lib/*so*; do \
> + i=`readlink -f "$$i"`; \
> + soname=`$(CROSS_COMPILE_SHARED_FDPIC)readelf -d "$$i" | sed -n '/(SONAME)/s:.*[[]\(.*\)[]].*:\1:p'`; \
> + $(INSTALL) -D $$i $(TARGET_DIR)/lib/$$soname; \
> + done
> +
> +CROSS_COMPILE_SHARED_FLAT ?= bfin-uclinux-
> +target-shared-libs-flat:
> + set -e; \
> + t=`$(CROSS_COMPILE_SHARED_FLAT)gcc $(CPUFLAGS) -mid-shared-library -print-file-name=libc`; \
> + if [ -f $$t -a ! -h $$t ] ; then \
> + $(INSTALL) -D $$t $(TARGET_DIR)/lib/lib1.so; \
> + fi
I am still not happy with this, because it simply doesn't work unless
you have the Blackfin toolchain installed globally on your system,
which simply isn't the case for normal users.
So I believe we should extend the external toolchain logic to be able
to use three variants of the Blackfin toolchain:
* Only FDPIC
* Only FLAT
* Both FLAT and FDPIC
And then, this logic should be moved in the external toolchain logic,
where we already do the process of copying libraries from the toolchain
to the target, and from the toolchain to the staging directory.
Also:
* $(CPUFLAGS) isn't defined anywhere
* the logic to determine which .so files to copy should use the
$(LIB_EXTERNAL_LIBS) and $(USR_LIB_EXTERNAL_LIBS) that we already
use in ext-tool.mk.
* I don't quite understand the logic you're using for the shared flat
library copying. You use -print-file-name=libc, but then you copy it
under the name 'lib1.so'. I think a comment above this part would be
useful.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-04-07 21:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 9:50 [Buildroot] [PATCH v2 1/7] arch: Add blackfin CPU choice Sonic Zhang
2013-03-29 9:50 ` [Buildroot] [PATCH v2 2/7] arch: toolchain: Introduce target CPU revision Sonic Zhang
2013-04-07 20:42 ` Thomas Petazzoni
2013-04-08 6:30 ` Sonic Zhang
2013-03-29 9:50 ` [Buildroot] [PATCH v2 3/7] arch: toolchain: Introduce binary formats BINFMT_* Sonic Zhang
2013-04-07 20:45 ` Thomas Petazzoni
2013-04-08 6:03 ` Sonic Zhang
2013-04-07 20:47 ` Thomas Petazzoni
2013-04-08 6:04 ` Sonic Zhang
2013-03-29 9:50 ` [Buildroot] [PATCH v2 4/7] arch: toolchain: Introduce binary format FLAT types Sonic Zhang
2013-04-07 20:51 ` Thomas Petazzoni
2013-04-08 6:43 ` Sonic Zhang
2013-04-12 3:39 ` Sonic Zhang
2013-04-13 14:31 ` Thomas Petazzoni
2013-04-16 10:26 ` Sonic Zhang
2013-04-16 10:46 ` Thomas Petazzoni
2013-04-17 9:02 ` Sonic Zhang
2013-04-23 5:57 ` Sonic Zhang
2013-03-29 9:50 ` [Buildroot] [PATCH v2 5/7] package: Introduce package-specific BINFMT_FLAT options Sonic Zhang
2013-04-07 21:27 ` Thomas Petazzoni
2013-04-10 5:47 ` Arnout Vandecappelle
2013-04-10 8:10 ` Sonic Zhang
2013-04-10 10:36 ` Arnout Vandecappelle
2013-03-29 9:50 ` [Buildroot] [PATCH v2 6/7] arch: Introduce blackfin-specific Makefile Sonic Zhang
2013-04-07 21:41 ` Thomas Petazzoni [this message]
2013-04-08 7:19 ` Sonic Zhang
2013-04-08 21:23 ` Thomas Petazzoni
2013-03-29 9:50 ` [Buildroot] [PATCH v2 7/7] package: Introduce NOMMU symbol Sonic Zhang
2013-04-07 20:39 ` [Buildroot] [PATCH v2 1/7] arch: Add blackfin CPU choice Thomas Petazzoni
2013-04-08 3:28 ` Sonic Zhang
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=20130407234129.60c6ac9d@skate \
--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