* [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
@ 2014-05-07 8:07 Michael Olbrich
2014-05-07 8:41 ` Alexander Dahl
2014-09-24 13:43 ` Tim Sander
0 siblings, 2 replies; 16+ messages in thread
From: Michael Olbrich @ 2014-05-07 8:07 UTC (permalink / raw)
To: ptxdist
Hi,
I'm happy to announce that I've just released OSELAS.Toolchain-2013.12.2.
This is a bugfix-only release. The relevant changes since 2013.12.1 are:
- The toolchains can now be built with make 4.0
- Some toolchains did not optimize for the correct CPU. The code works but
might be slower. This is fixed now.
- All security relevant fixes mentioned in the glibc 2.19 changelog have
been added for glibc 2.18 based toolchains.
- All generated toolchain archives are now XZ comressed.
Download the release here:
http://www.pengutronix.de/oselas/toolchain/download/
Enjoy,
Michael Olbrich
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-05-07 8:07 [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released Michael Olbrich
@ 2014-05-07 8:41 ` Alexander Dahl
2014-05-07 10:23 ` Michael Olbrich
2014-09-24 13:43 ` Tim Sander
1 sibling, 1 reply; 16+ messages in thread
From: Alexander Dahl @ 2014-05-07 8:41 UTC (permalink / raw)
To: ptxdist
Moin,
Am 2014-05-07 10:07, schrieb Michael Olbrich:
> - All generated toolchain archives are now XZ comressed.
Who generates this? Can I do this when building the toolchain? Up to now
I do this manually.
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-05-07 8:41 ` Alexander Dahl
@ 2014-05-07 10:23 ` Michael Olbrich
2014-05-07 11:16 ` Alexander Dahl
0 siblings, 1 reply; 16+ messages in thread
From: Michael Olbrich @ 2014-05-07 10:23 UTC (permalink / raw)
To: ptxdist
Hi,
On Wed, May 07, 2014 at 10:41:33AM +0200, Alexander Dahl wrote:
> Am 2014-05-07 10:07, schrieb Michael Olbrich:
> > - All generated toolchain archives are now XZ comressed.
>
> Who generates this? Can I do this when building the toolchain? Up to now
> I do this manually.
this is done in the build_all_v2.mk script. For one toolchain I use e.g.
$ ./build_one.sh arm-v7a-linux-gnueabihf
This does some matching to find the correct config and calls
build_all_v2.mk with the correct target to build on toolchain.
The result is in inst/ and a tarball and Debian package (if dpkg is
available) are generated in dist/.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-05-07 10:23 ` Michael Olbrich
@ 2014-05-07 11:16 ` Alexander Dahl
2014-05-07 12:15 ` Michael Olbrich
0 siblings, 1 reply; 16+ messages in thread
From: Alexander Dahl @ 2014-05-07 11:16 UTC (permalink / raw)
To: ptxdist
Hei hei,
Am 2014-05-07 12:23, schrieb Michael Olbrich:
> On Wed, May 07, 2014 at 10:41:33AM +0200, Alexander Dahl wrote:
>> Am 2014-05-07 10:07, schrieb Michael Olbrich:
>> > - All generated toolchain archives are now XZ comressed.
>>
>> Who generates this? Can I do this when building the toolchain? Up to now
>> I do this manually.
>
> this is done in the build_all_v2.mk script. For one toolchain I use e.g.
>
> $ ./build_one.sh arm-v7a-linux-gnueabihf
>
> This does some matching to find the correct config and calls
> build_all_v2.mk with the correct target to build on toolchain.
> The result is in inst/ and a tarball and Debian package (if dpkg is
> available) are generated in dist/.
I like the idea, however it does not work out of the box because of line
36 in build_all_v2.mk … ;-)
But handy anyway, thanks for the hint.
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-05-07 11:16 ` Alexander Dahl
@ 2014-05-07 12:15 ` Michael Olbrich
2014-05-07 12:30 ` Bernhard Walle
2014-05-07 13:01 ` Alexander Dahl
0 siblings, 2 replies; 16+ messages in thread
From: Michael Olbrich @ 2014-05-07 12:15 UTC (permalink / raw)
To: ptxdist
Hi,
On Wed, May 07, 2014 at 01:16:10PM +0200, Alexander Dahl wrote:
> Am 2014-05-07 12:23, schrieb Michael Olbrich:
> > On Wed, May 07, 2014 at 10:41:33AM +0200, Alexander Dahl wrote:
> >> Am 2014-05-07 10:07, schrieb Michael Olbrich:
> >> > - All generated toolchain archives are now XZ comressed.
> >>
> >> Who generates this? Can I do this when building the toolchain? Up to now
> >> I do this manually.
> >
> > this is done in the build_all_v2.mk script. For one toolchain I use e.g.
> >
> > $ ./build_one.sh arm-v7a-linux-gnueabihf
> >
> > This does some matching to find the correct config and calls
> > build_all_v2.mk with the correct target to build on toolchain.
> > The result is in inst/ and a tarball and Debian package (if dpkg is
> > available) are generated in dist/.
>
> I like the idea, however it does not work out of the box because of line
> 36 in build_all_v2.mk … ;-)
>
> But handy anyway, thanks for the hint.
Well, I don't think I have any ptxdist based project without a 'p' link
pointing to the correct ptxdist version... :-)
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-05-07 12:15 ` Michael Olbrich
@ 2014-05-07 12:30 ` Bernhard Walle
2014-05-07 14:39 ` Uwe Kleine-König
2014-05-07 13:01 ` Alexander Dahl
1 sibling, 1 reply; 16+ messages in thread
From: Bernhard Walle @ 2014-05-07 12:30 UTC (permalink / raw)
To: ptxdist
Am 2014-05-07 14:15, schrieb Michael Olbrich:
>
> Well, I don't think I have any ptxdist based project without a 'p' link
> pointing to the correct ptxdist version... :-)
http://comments.gmane.org/gmane.comp.embedded.ptxdist.devel/8002 :)
Regards,
Bernhard
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-05-07 12:15 ` Michael Olbrich
2014-05-07 12:30 ` Bernhard Walle
@ 2014-05-07 13:01 ` Alexander Dahl
2014-05-07 13:08 ` Michael Olbrich
1 sibling, 1 reply; 16+ messages in thread
From: Alexander Dahl @ 2014-05-07 13:01 UTC (permalink / raw)
To: ptxdist
Hei hei,
Am 2014-05-07 14:15, schrieb Michael Olbrich:
> On Wed, May 07, 2014 at 01:16:10PM +0200, Alexander Dahl wrote:
>> I like the idea, however it does not work out of the box because of line
>> 36 in build_all_v2.mk … ;-)
>>
>> But handy anyway, thanks for the hint.
>
> Well, I don't think I have any ptxdist based project without a 'p' link
> pointing to the correct ptxdist version... :-)
Got it. The --force in the Makefile should not be necessary then. ;-)
Thanks guys, this will simplify some things here for building and
distributing new toolchains. :-)
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-05-07 13:01 ` Alexander Dahl
@ 2014-05-07 13:08 ` Michael Olbrich
0 siblings, 0 replies; 16+ messages in thread
From: Michael Olbrich @ 2014-05-07 13:08 UTC (permalink / raw)
To: ptxdist
Hi,
On Wed, May 07, 2014 at 03:01:50PM +0200, Alexander Dahl wrote:
> Am 2014-05-07 14:15, schrieb Michael Olbrich:
> > On Wed, May 07, 2014 at 01:16:10PM +0200, Alexander Dahl wrote:
> >> I like the idea, however it does not work out of the box because of line
> >> 36 in build_all_v2.mk … ;-)
> >>
> >> But handy anyway, thanks for the hint.
> >
> > Well, I don't think I have any ptxdist based project without a 'p' link
> > pointing to the correct ptxdist version... :-)
>
> Got it. The --force in the Makefile should not be necessary then. ;-)
True. It's a relict from times when the script was less flexible. I should
really remove it now...
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-05-07 12:30 ` Bernhard Walle
@ 2014-05-07 14:39 ` Uwe Kleine-König
0 siblings, 0 replies; 16+ messages in thread
From: Uwe Kleine-König @ 2014-05-07 14:39 UTC (permalink / raw)
To: ptxdist
On Wed, May 07, 2014 at 02:30:44PM +0200, Bernhard Walle wrote:
> Am 2014-05-07 14:15, schrieb Michael Olbrich:
> >
> >Well, I don't think I have any ptxdist based project without a 'p' link
> >pointing to the correct ptxdist version... :-)
>
> http://comments.gmane.org/gmane.comp.embedded.ptxdist.devel/8002 :)
BTW, the approach I'm using is a script called p in my PATH, that looks
as follows:
-------->8---------
#! /bin/sh
debug() {
: echo "$*"
}
if test -h p; then
exec ./p "$@"
fi
# guess ptxconfig to take
for ptxconfig in selected_ptxconfig configs/ptxconfig; do
if test -f "$ptxconfig"; then
break
fi
done
debug "Using \"$ptxconfig\""
ptxdistversion=$(sed -n 's/PTXCONF_CONFIGFILE_VERSION="\([^"]*\)"/\1/p; T; q' -- "$ptxconfig")
debug "Found version $ptxdistversion"
# todo: guess path to ptxdist.git if it's an unreleased version
case "$ptxdistversion" in
20[0-9][0-9].[01][0-9].[0-9])
exec "/opt/bin/ptxdist-$ptxdistversion" "$@"
;;
*)
echo "Sorry"
;;
esac
-------->8---------
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-05-07 8:07 [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released Michael Olbrich
2014-05-07 8:41 ` Alexander Dahl
@ 2014-09-24 13:43 ` Tim Sander
2014-09-24 18:01 ` Uwe Kleine-König
2014-09-26 6:46 ` Michael Olbrich
1 sibling, 2 replies; 16+ messages in thread
From: Tim Sander @ 2014-09-24 13:43 UTC (permalink / raw)
To: ptxdist; +Cc: Michael Olbrich
Hi
> I'm happy to announce that I've just released OSELAS.Toolchain-2013.12.2.
>
> This is a bugfix-only release. The relevant changes since 2013.12.1 are:
> - The toolchains can now be built with make 4.0
> - Some toolchains did not optimize for the correct CPU. The code works but
> might be slower. This is fixed now.
> - All security relevant fixes mentioned in the glibc 2.19 changelog have
> been added for glibc 2.18 based toolchains.
> - All generated toolchain archives are now XZ comressed.
While i have used this toolchain arm-v7a-linux-gnueabihf with an Xilinx Zynx
compiling nearly the same Project with a different Kernelconfig /DTB for Altera
SOC fails with this toolchain !?! The kernel boots but on mounting the rootfs
it fails to execute any binary?
Compiling the same project with OSELAS.Toolchain-2012.12.1/arm-cortexa9-linux-
gnueabihf/gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized does work
however.
I have also tried setting:
PTXCONF_TARGET_EXTRA_CFLAGS="-mcpu=cortex-a9 -mfpu=neon"
PTXCONF_TARGET_EXTRA_CXXFLAGS="-mcpu=cortex-a9 -mfpu=neon"
But it still fails on executing any binary.
Best regards
Tim
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-09-24 13:43 ` Tim Sander
@ 2014-09-24 18:01 ` Uwe Kleine-König
2014-09-26 6:09 ` Tim Sander
2014-09-26 6:46 ` Michael Olbrich
1 sibling, 1 reply; 16+ messages in thread
From: Uwe Kleine-König @ 2014-09-24 18:01 UTC (permalink / raw)
To: ptxdist; +Cc: Michael Olbrich
On Wed, Sep 24, 2014 at 03:43:10PM +0200, Tim Sander wrote:
> Hi
>
> > I'm happy to announce that I've just released OSELAS.Toolchain-2013.12.2.
> >
> > This is a bugfix-only release. The relevant changes since 2013.12.1 are:
> > - The toolchains can now be built with make 4.0
> > - Some toolchains did not optimize for the correct CPU. The code works but
> > might be slower. This is fixed now.
> > - All security relevant fixes mentioned in the glibc 2.19 changelog have
> > been added for glibc 2.18 based toolchains.
> > - All generated toolchain archives are now XZ comressed.
> While i have used this toolchain arm-v7a-linux-gnueabihf with an Xilinx Zynx
> compiling nearly the same Project with a different Kernelconfig /DTB for Altera
> SOC fails with this toolchain !?! The kernel boots but on mounting the rootfs
> it fails to execute any binary?
>
> Compiling the same project with OSELAS.Toolchain-2012.12.1/arm-cortexa9-linux-
> gnueabihf/gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized does work
> however.
>
> I have also tried setting:
> PTXCONF_TARGET_EXTRA_CFLAGS="-mcpu=cortex-a9 -mfpu=neon"
> PTXCONF_TARGET_EXTRA_CXXFLAGS="-mcpu=cortex-a9 -mfpu=neon"
> But it still fails on executing any binary.
Without knowing details about the two toolchains in question, this might
be an ABI-problem. Does your kernel have OABI_COMPAT=y?
Did you try to run a 2013.12.1 userspace with a 2012.12.1-compiled
kernel and vice versa?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-09-24 18:01 ` Uwe Kleine-König
@ 2014-09-26 6:09 ` Tim Sander
0 siblings, 0 replies; 16+ messages in thread
From: Tim Sander @ 2014-09-26 6:09 UTC (permalink / raw)
To: ptxdist; +Cc: Michael Olbrich, Uwe Kleine-König
Hi Uwe
Thanks for your reply. It sounds it could get more involved, if yes we should
set up some support for this via private mail, as i am wearing my business
hat.
Am Mittwoch, 24. September 2014, 20:01:54 schrieb Uwe Kleine-König:
> On Wed, Sep 24, 2014 at 03:43:10PM +0200, Tim Sander wrote:
> > Hi
> >
> > > I'm happy to announce that I've just released
> > > OSELAS.Toolchain-2013.12.2.
> > >
> > > This is a bugfix-only release. The relevant changes since 2013.12.1 are:
> > > - The toolchains can now be built with make 4.0
> > > - Some toolchains did not optimize for the correct CPU. The code works
> > > but
> > >
> > > might be slower. This is fixed now.
> > >
> > > - All security relevant fixes mentioned in the glibc 2.19 changelog
> > > have
> > >
> > > been added for glibc 2.18 based toolchains.
> > >
> > > - All generated toolchain archives are now XZ comressed.
> >
> > While i have used this toolchain arm-v7a-linux-gnueabihf with an Xilinx
> > Zynx compiling nearly the same Project with a different Kernelconfig /DTB
> > for Altera SOC fails with this toolchain !?! The kernel boots but on
> > mounting the rootfs it fails to execute any binary?
> >
> > Compiling the same project with
> > OSELAS.Toolchain-2012.12.1/arm-cortexa9-linux-
> > gnueabihf/gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized does
> > work however.
> >
> > I have also tried setting:
> > PTXCONF_TARGET_EXTRA_CFLAGS="-mcpu=cortex-a9 -mfpu=neon"
> > PTXCONF_TARGET_EXTRA_CXXFLAGS="-mcpu=cortex-a9 -mfpu=neon"
> > But it still fails on executing any binary.
>
> Without knowing details about the two toolchains in question, this might
> be an ABI-problem. Does your kernel have OABI_COMPAT=y?
No its disabled, in the Xilinx Zynq (working) and the Altera SOC (not working)
but CONFIG_AEABI=y .
> Did you try to run a 2013.12.1 userspace with a 2012.12.1-compiled
> kernel and vice versa?
No, i was doing a "ptxdist clean" inbetween switching toolchains. So the whole
project was only compiled with one compiler. That is, if "ptxdist clean" is
working as expected.
Best regards
Tim
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-09-24 13:43 ` Tim Sander
2014-09-24 18:01 ` Uwe Kleine-König
@ 2014-09-26 6:46 ` Michael Olbrich
2014-09-29 13:47 ` Tim Sander
2014-09-29 13:56 ` Tim Sander
1 sibling, 2 replies; 16+ messages in thread
From: Michael Olbrich @ 2014-09-26 6:46 UTC (permalink / raw)
To: ptxdist
On Wed, Sep 24, 2014 at 03:43:10PM +0200, Tim Sander wrote:
> > I'm happy to announce that I've just released OSELAS.Toolchain-2013.12.2.
> >
> > This is a bugfix-only release. The relevant changes since 2013.12.1 are:
> > - The toolchains can now be built with make 4.0
> > - Some toolchains did not optimize for the correct CPU. The code works but
> > might be slower. This is fixed now.
> > - All security relevant fixes mentioned in the glibc 2.19 changelog have
> > been added for glibc 2.18 based toolchains.
> > - All generated toolchain archives are now XZ comressed.
> While i have used this toolchain arm-v7a-linux-gnueabihf with an Xilinx Zynx
> compiling nearly the same Project with a different Kernelconfig /DTB for Altera
> SOC fails with this toolchain !?! The kernel boots but on mounting the rootfs
> it fails to execute any binary?
Is the dynamic linker (whatever /lib/ld-linux-armhf.so.3 points to) executable?
Do you have a working system? Boot it and try to chroot into your new
system. You get better error messages that way.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-09-26 6:46 ` Michael Olbrich
@ 2014-09-29 13:47 ` Tim Sander
2014-09-29 13:56 ` Tim Sander
1 sibling, 0 replies; 16+ messages in thread
From: Tim Sander @ 2014-09-29 13:47 UTC (permalink / raw)
To: ptxdist; +Cc: Michael Olbrich
[-- Attachment #1: Type: text/plain, Size: 2380 bytes --]
Hi Michael
Am Freitag, 26. September 2014, 08:46:21 schrieb Michael Olbrich:
> On Wed, Sep 24, 2014 at 03:43:10PM +0200, Tim Sander wrote:
> > > I'm happy to announce that I've just released
> > > OSELAS.Toolchain-2013.12.2.
> > >
> > > This is a bugfix-only release. The relevant changes since 2013.12.1 are:
> > > - The toolchains can now be built with make 4.0
> > > - Some toolchains did not optimize for the correct CPU. The code works
> > > but
> > >
> > > might be slower. This is fixed now.
> > >
> > > - All security relevant fixes mentioned in the glibc 2.19 changelog
> > > have
> > >
> > > been added for glibc 2.18 based toolchains.
> > >
> > > - All generated toolchain archives are now XZ comressed.
> >
> > While i have used this toolchain arm-v7a-linux-gnueabihf with an Xilinx
> > Zynx compiling nearly the same Project with a different Kernelconfig /DTB
> > for Altera SOC fails with this toolchain !?! The kernel boots but on
> > mounting the rootfs it fails to execute any binary?
>
> Is the dynamic linker (whatever /lib/ld-linux-armhf.so.3 points to)
> executable? Do you have a working system? Boot it and try to chroot into
> your new system. You get better error messages that way.
Ok i have now setup booted into the environment compiled with
OSELAS.Toolchain-2012.12.1/arm-cortexa9-linux-gnueabihf, mounted the other
system via nfs and tried to start any executable:
/mnt/bin/busybox: line 1: syntax error: unexpected word (expecting ")")
(thats with OSELAS.Toolchain-2013.12.2/arm-v7a-linux-gnueabihf on Altera SOC)
I have taken a look at both busyboxes and have run them through "readelf -e"
(attached). The only difference which sprung to my eye was the hardfloat
support, which i don't understand as both toolchains should be hardfloat
toolchains.
Starting the binary with strace gives:
execve("mnt/bin/busybox", ["mnt/bin/busybox"], [/* 11 vars */]) = -1 ENOEXEC
(Exec format error)
write(2, "strace: exec: Exec format error\n", 32strace: exec: Exec format
error
) = 32
exit_group(1) = ?
+++ exited with 1 +++
So i have an execution error and the shell error seems to be the shell
fallback from the kernel.
Another thing which caught my attention was the fact that:
objdump -d bin/busybox |grep UNDEFINED |wc -l
is 364 for the old and 13478 for the new toolchain.
Best regards
Tim
[-- Attachment #2: OSELAS.Toolchain-2012.12.1/arm-cortexa9-linux-gnueabihf --]
[-- Type: text/plain, Size: 4790 bytes --]
ELF-Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Klasse: ELF32
Daten: 2er-Komplement, Little-Endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI-Version: 0
Typ: EXEC (ausführbare Datei)
Maschine: ARM
Version: 0x1
Einstiegspunktadresse: 0x10010
Beginn der Programm-Header: 52 (Bytes in Datei)
Beginn der Sektions-header: 460812 (Bytes in Datei)
Flags: 0x5000002, has entry point, Version5 EABI
Größe dieses Headers: 52 (Byte)
Größe der Programm-Header: 32 (Byte)
Number of program headers: 8
Größe der Sektions-Header: 40 (bytes)
Anzahl der Sektions-Header: 28
Sektions-Header Stringtabellen-Index: 27
Sektions-Header:
[Nr] Name Typ Adr Off Größe ES Flg Lk Inf Ar
[ 0] NULL 00000000 000000 000000 00 0 0 0
[ 1] .interp PROGBITS 00008134 000134 000019 00 A 0 0 1
[ 2] .note.ABI-tag NOTE 00008150 000150 000020 00 A 0 0 4
[ 3] .hash HASH 00008170 000170 0008cc 04 A 4 0 4
[ 4] .dynsym DYNSYM 00008a3c 000a3c 0012a0 10 A 5 1 4
[ 5] .dynstr STRTAB 00009cdc 001cdc 00097c 00 A 0 0 1
[ 6] .gnu.version VERSYM 0000a658 002658 000254 02 A 4 0 2
[ 7] .gnu.version_r VERNEED 0000a8ac 0028ac 000020 00 A 5 1 4
[ 8] .rel.dyn REL 0000a8cc 0028cc 000048 08 A 4 0 4
[ 9] .rel.plt REL 0000a914 002914 0008e8 08 A 4 11 4
[10] .init PROGBITS 0000b1fc 0031fc 00000c 00 AX 0 0 4
[11] .plt PROGBITS 0000b208 003208 000d70 04 AX 0 0 4
[12] .text PROGBITS 0000bf78 003f78 05c610 00 AX 0 0 8
[13] .fini PROGBITS 00068588 060588 000008 00 AX 0 0 4
[14] .rodata PROGBITS 00068590 060590 00f0f4 00 A 0 0 4
[15] .ARM.extab PROGBITS 00077684 06f684 000030 00 A 0 0 4
[16] .ARM.exidx ARM_EXIDX 000776b4 06f6b4 0000d8 00 AL 12 0 4
[17] .eh_frame PROGBITS 0007778c 06f78c 000004 00 A 0 0 4
[18] .init_array INIT_ARRAY 00078000 070000 000004 00 WA 0 0 4
[19] .fini_array FINI_ARRAY 00078004 070004 000004 00 WA 0 0 4
[20] .jcr PROGBITS 00078008 070008 000004 00 WA 0 0 4
[21] .dynamic DYNAMIC 0007800c 07000c 0000e8 08 WA 5 0 4
[22] .got PROGBITS 000780f4 0700f4 000498 04 WA 0 0 4
[23] .data PROGBITS 0007858c 07058c 00013d 00 WA 0 0 4
[24] .bss NOBITS 000786d0 0706c9 002234 00 WA 0 0 8
[25] .ARM.attributes ARM_ATTRIBUTES 00000000 0706c9 000043 00 0 0 1
[26] .gnu_debuglink PROGBITS 00000000 07070c 00000c 00 0 0 1
[27] .shstrtab STRTAB 00000000 070718 0000f4 00 0 0 1
Key to Flags:
W (write), A (alloc), X (execute), M (merge), S (strings)
I (info), L (link order), G (group), T (TLS), E (exclude), x (unknown)
O (extra OS processing required) o (OS specific), p (processor specific)
Programm-Header:
Typ Offset VirtAdr PhysAdr DateiGr SpeiGr Flg Ausr.
EXIDX 0x06f6b4 0x000776b4 0x000776b4 0x000d8 0x000d8 R 0x4
PHDR 0x000034 0x00008034 0x00008034 0x00100 0x00100 R E 0x4
INTERP 0x000134 0x00008134 0x00008134 0x00019 0x00019 R 0x1
[Programminterpreter anfordern: /lib/ld-linux-armhf.so.3]
LOAD 0x000000 0x00008000 0x00008000 0x6f790 0x6f790 R E 0x8000
LOAD 0x070000 0x00078000 0x00078000 0x006c9 0x02904 RW 0x8000
DYNAMIC 0x07000c 0x0007800c 0x0007800c 0x000e8 0x000e8 RW 0x4
NOTE 0x000150 0x00008150 0x00008150 0x00020 0x00020 R 0x4
GNU_STACK 0x000000 0x00000000 0x00000000 0x00000 0x00000 RW 0x4
Abbildung von Sektion nach Segment:
Segmentsektionen...
00 .ARM.exidx
01
02 .interp
03 .interp .note.ABI-tag .hash .dynsym .dynstr .gnu.version .gnu.version_r .rel.dyn .rel.plt .init .plt .text .fini .rodata .ARM.extab .ARM.exidx .eh_frame
04 .init_array .fini_array .jcr .dynamic .got .data .bss
05 .dynamic
06 .note.ABI-tag
07
[-- Attachment #3: OSELAS.Toolchain-2013.12.2/arm-v7a-linux-gnueabihf --]
[-- Type: text/plain, Size: 4713 bytes --]
ELF-Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Klasse: ELF32
Daten: 2er-Komplement, Little-Endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI-Version: 0
Typ: EXEC (ausführbare Datei)
Maschine: ARM
Version: 0x1
Einstiegspunktadresse: 0xe789
Beginn der Programm-Header: 52 (Bytes in Datei)
Beginn der Sektions-header: 321624 (Bytes in Datei)
Flags: 0x5000402, has entry point, Version5 EABI, hard-float ABI
Größe dieses Headers: 52 (Byte)
Größe der Programm-Header: 32 (Byte)
Number of program headers: 8
Größe der Sektions-Header: 40 (bytes)
Anzahl der Sektions-Header: 27
Sektions-Header Stringtabellen-Index: 26
Sektions-Header:
[Nr] Name Typ Adr Off Größe ES Flg Lk Inf Ar
[ 0] NULL 00000000 000000 000000 00 0 0 0
[ 1] .interp PROGBITS 00008134 000134 000019 00 A 0 0 1
[ 2] .note.ABI-tag NOTE 00008150 000150 000020 00 A 0 0 4
[ 3] .hash HASH 00008170 000170 0008ac 04 A 4 0 4
[ 4] .dynsym DYNSYM 00008a1c 000a1c 001220 10 A 5 1 4
[ 5] .dynstr STRTAB 00009c3c 001c3c 00090e 00 A 0 0 1
[ 6] .gnu.version VERSYM 0000a54a 00254a 000244 02 A 4 0 2
[ 7] .gnu.version_r VERNEED 0000a790 002790 000020 00 A 5 1 4
[ 8] .rel.dyn REL 0000a7b0 0027b0 000038 08 A 4 0 4
[ 9] .rel.plt REL 0000a7e8 0027e8 0008d0 08 A 4 11 4
[10] .init PROGBITS 0000b0b8 0030b8 00000c 00 AX 0 0 4
[11] .plt PROGBITS 0000b0c4 0030c4 000ddc 04 AX 0 0 4
[12] .text PROGBITS 0000bea0 003ea0 03b116 00 AX 0 0 8
[13] .fini PROGBITS 00046fb8 03efb8 000008 00 AX 0 0 4
[14] .rodata PROGBITS 00046fc0 03efc0 00f0af 00 A 0 0 4
[15] .ARM.exidx ARM_EXIDX 00056070 04e070 000008 00 AL 12 0 4
[16] .eh_frame PROGBITS 00056078 04e078 000004 00 A 0 0 4
[17] .init_array INIT_ARRAY 0005e07c 04e07c 000004 00 WA 0 0 4
[18] .fini_array FINI_ARRAY 0005e080 04e080 000004 00 WA 0 0 4
[19] .jcr PROGBITS 0005e084 04e084 000004 00 WA 0 0 4
[20] .dynamic DYNAMIC 0005e088 04e088 0000e8 08 WA 5 0 4
[21] .got PROGBITS 0005e170 04e170 00047c 04 WA 0 0 4
[22] .data PROGBITS 0005e5ec 04e5ec 00013d 00 WA 0 0 4
[23] .bss NOBITS 0005e730 04e729 00223c 00 WA 0 0 8
[24] .ARM.attributes ARM_ATTRIBUTES 00000000 04e729 000037 00 0 0 1
[25] .gnu_debuglink PROGBITS 00000000 04e760 00000c 00 0 0 1
[26] .shstrtab STRTAB 00000000 04e76c 0000e9 00 0 0 1
Key to Flags:
W (write), A (alloc), X (execute), M (merge), S (strings)
I (info), L (link order), G (group), T (TLS), E (exclude), x (unknown)
O (extra OS processing required) o (OS specific), p (processor specific)
Programm-Header:
Typ Offset VirtAdr PhysAdr DateiGr SpeiGr Flg Ausr.
EXIDX 0x04e070 0x00056070 0x00056070 0x00008 0x00008 R 0x4
PHDR 0x000034 0x00008034 0x00008034 0x00100 0x00100 R E 0x4
INTERP 0x000134 0x00008134 0x00008134 0x00019 0x00019 R 0x1
[Programminterpreter anfordern: /lib/ld-linux-armhf.so.3]
LOAD 0x000000 0x00008000 0x00008000 0x4e07c 0x4e07c R E 0x8000
LOAD 0x04e07c 0x0005e07c 0x0005e07c 0x006ad 0x028f0 RW 0x8000
DYNAMIC 0x04e088 0x0005e088 0x0005e088 0x000e8 0x000e8 RW 0x4
NOTE 0x000150 0x00008150 0x00008150 0x00020 0x00020 R 0x4
GNU_STACK 0x000000 0x00000000 0x00000000 0x00000 0x00000 RW 0x10
Abbildung von Sektion nach Segment:
Segmentsektionen...
00 .ARM.exidx
01
02 .interp
03 .interp .note.ABI-tag .hash .dynsym .dynstr .gnu.version .gnu.version_r .rel.dyn .rel.plt .init .plt .text .fini .rodata .ARM.exidx .eh_frame
04 .init_array .fini_array .jcr .dynamic .got .data .bss
05 .dynamic
06 .note.ABI-tag
07
[-- Attachment #4: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-09-26 6:46 ` Michael Olbrich
2014-09-29 13:47 ` Tim Sander
@ 2014-09-29 13:56 ` Tim Sander
2014-10-01 13:02 ` Michael Olbrich
1 sibling, 1 reply; 16+ messages in thread
From: Tim Sander @ 2014-09-29 13:56 UTC (permalink / raw)
To: ptxdist; +Cc: Michael Olbrich
[-- Attachment #1: Type: text/plain, Size: 2380 bytes --]
Hi Michael
Am Freitag, 26. September 2014, 08:46:21 schrieb Michael Olbrich:
> On Wed, Sep 24, 2014 at 03:43:10PM +0200, Tim Sander wrote:
> > > I'm happy to announce that I've just released
> > > OSELAS.Toolchain-2013.12.2.
> > >
> > > This is a bugfix-only release. The relevant changes since 2013.12.1 are:
> > > - The toolchains can now be built with make 4.0
> > > - Some toolchains did not optimize for the correct CPU. The code works
> > > but
> > >
> > > might be slower. This is fixed now.
> > >
> > > - All security relevant fixes mentioned in the glibc 2.19 changelog
> > > have
> > >
> > > been added for glibc 2.18 based toolchains.
> > >
> > > - All generated toolchain archives are now XZ comressed.
> >
> > While i have used this toolchain arm-v7a-linux-gnueabihf with an Xilinx
> > Zynx compiling nearly the same Project with a different Kernelconfig /DTB
> > for Altera SOC fails with this toolchain !?! The kernel boots but on
> > mounting the rootfs it fails to execute any binary?
>
> Is the dynamic linker (whatever /lib/ld-linux-armhf.so.3 points to)
> executable? Do you have a working system? Boot it and try to chroot into
> your new system. You get better error messages that way.
Ok i have now setup booted into the environment compiled with
OSELAS.Toolchain-2012.12.1/arm-cortexa9-linux-gnueabihf, mounted the other
system via nfs and tried to start any executable:
/mnt/bin/busybox: line 1: syntax error: unexpected word (expecting ")")
(thats with OSELAS.Toolchain-2013.12.2/arm-v7a-linux-gnueabihf on Altera SOC)
I have taken a look at both busyboxes and have run them through "readelf -e"
(attached). The only difference which sprung to my eye was the hardfloat
support, which i don't understand as both toolchains should be hardfloat
toolchains.
Starting the binary with strace gives:
execve("mnt/bin/busybox", ["mnt/bin/busybox"], [/* 11 vars */]) = -1 ENOEXEC
(Exec format error)
write(2, "strace: exec: Exec format error\n", 32strace: exec: Exec format
error
) = 32
exit_group(1) = ?
+++ exited with 1 +++
So i have an execution error and the shell error seems to be the shell
fallback from the kernel.
Another thing which caught my attention was the fact that:
objdump -d bin/busybox |grep UNDEFINED |wc -l
is 364 for the old and 13478 for the new toolchain.
Best regards
Tim
[-- Attachment #2: OSELAS.Toolchain-2012.12.1/arm-cortexa9-linux-gnueabihf --]
[-- Type: text/plain, Size: 4788 bytes --]
ELF-Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Klasse: ELF32
Daten: 2er-Komplement, Little-Endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI-Version: 0
Typ: EXEC (ausführbare Datei)
Maschine: ARM
Version: 0x1
Einstiegspunktadresse: 0x10010
Beginn der Programm-Header: 52 (Bytes in Datei)
Beginn der Sektions-header: 460812 (Bytes in Datei)
Flags: 0x5000002, has entry point, Version5 EABI
Größe dieses Headers: 52 (Byte)
Größe der Programm-Header: 32 (Byte)
Number of program headers: 8
Größe der Sektions-Header: 40 (bytes)
Anzahl der Sektions-Header: 28
Sektions-Header Stringtabellen-Index: 27
Sektions-Header:
[Nr] Name Typ Adr Off Größe ES Flg Lk Inf Ar
[ 0] NULL 00000000 000000 000000 00 0 0 0
[ 1] .interp PROGBITS 00008134 000134 000019 00 A 0 0 1
[ 2] .note.ABI-tag NOTE 00008150 000150 000020 00 A 0 0 4
[ 3] .hash HASH 00008170 000170 0008cc 04 A 4 0 4
[ 4] .dynsym DYNSYM 00008a3c 000a3c 0012a0 10 A 5 1 4
[ 5] .dynstr STRTAB 00009cdc 001cdc 00097c 00 A 0 0 1
[ 6] .gnu.version VERSYM 0000a658 002658 000254 02 A 4 0 2
[ 7] .gnu.version_r VERNEED 0000a8ac 0028ac 000020 00 A 5 1 4
[ 8] .rel.dyn REL 0000a8cc 0028cc 000048 08 A 4 0 4
[ 9] .rel.plt REL 0000a914 002914 0008e8 08 A 4 11 4
[10] .init PROGBITS 0000b1fc 0031fc 00000c 00 AX 0 0 4
[11] .plt PROGBITS 0000b208 003208 000d70 04 AX 0 0 4
[12] .text PROGBITS 0000bf78 003f78 05c610 00 AX 0 0 8
[13] .fini PROGBITS 00068588 060588 000008 00 AX 0 0 4
[14] .rodata PROGBITS 00068590 060590 00f0f4 00 A 0 0 4
[15] .ARM.extab PROGBITS 00077684 06f684 000030 00 A 0 0 4
[16] .ARM.exidx ARM_EXIDX 000776b4 06f6b4 0000d8 00 AL 12 0 4
[17] .eh_frame PROGBITS 0007778c 06f78c 000004 00 A 0 0 4
[18] .init_array INIT_ARRAY 00078000 070000 000004 00 WA 0 0 4
[19] .fini_array FINI_ARRAY 00078004 070004 000004 00 WA 0 0 4
[20] .jcr PROGBITS 00078008 070008 000004 00 WA 0 0 4
[21] .dynamic DYNAMIC 0007800c 07000c 0000e8 08 WA 5 0 4
[22] .got PROGBITS 000780f4 0700f4 000498 04 WA 0 0 4
[23] .data PROGBITS 0007858c 07058c 00013d 00 WA 0 0 4
[24] .bss NOBITS 000786d0 0706c9 002234 00 WA 0 0 8
[25] .ARM.attributes ARM_ATTRIBUTES 00000000 0706c9 000043 00 0 0 1
[26] .gnu_debuglink PROGBITS 00000000 07070c 00000c 00 0 0 1
[27] .shstrtab STRTAB 00000000 070718 0000f4 00 0 0 1
Key to Flags:
W (write), A (alloc), X (execute), M (merge), S (strings)
I (info), L (link order), G (group), T (TLS), E (exclude), x (unknown)
O (extra OS processing required) o (OS specific), p (processor specific)
Programm-Header:
Typ Offset VirtAdr PhysAdr DateiGr SpeiGr Flg Ausr.
EXIDX 0x06f6b4 0x000776b4 0x000776b4 0x000d8 0x000d8 R 0x4
PHDR 0x000034 0x00008034 0x00008034 0x00100 0x00100 R E 0x4
INTERP 0x000134 0x00008134 0x00008134 0x00019 0x00019 R 0x1
[Programminterpreter anfordern: /lib/ld-linux-armhf.so.3]
LOAD 0x000000 0x00008000 0x00008000 0x6f790 0x6f790 R E 0x8000
LOAD 0x070000 0x00078000 0x00078000 0x006c9 0x02904 RW 0x8000
DYNAMIC 0x07000c 0x0007800c 0x0007800c 0x000e8 0x000e8 RW 0x4
NOTE 0x000150 0x00008150 0x00008150 0x00020 0x00020 R 0x4
GNU_STACK 0x000000 0x00000000 0x00000000 0x00000 0x00000 RW 0x4
Abbildung von Sektion nach Segment:
Segmentsektionen...
00 .ARM.exidx
01
02 .interp
03 .interp .note.ABI-tag .hash .dynsym .dynstr .gnu.version .gnu.version_r .rel.dyn .rel.plt .init .plt .text .fini .rodata .ARM.extab .ARM.exidx .eh_frame
04 .init_array .fini_array .jcr .dynamic .got .data .bss
05 .dynamic
06 .note.ABI-tag
07
[-- Attachment #3: OSELAS.Toolchain-2013.12.2/arm-v7a-linux-gnueabihf --]
[-- Type: text/plain, Size: 4711 bytes --]
ELF-Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Klasse: ELF32
Daten: 2er-Komplement, Little-Endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI-Version: 0
Typ: EXEC (ausführbare Datei)
Maschine: ARM
Version: 0x1
Einstiegspunktadresse: 0xe789
Beginn der Programm-Header: 52 (Bytes in Datei)
Beginn der Sektions-header: 321624 (Bytes in Datei)
Flags: 0x5000402, has entry point, Version5 EABI, hard-float ABI
Größe dieses Headers: 52 (Byte)
Größe der Programm-Header: 32 (Byte)
Number of program headers: 8
Größe der Sektions-Header: 40 (bytes)
Anzahl der Sektions-Header: 27
Sektions-Header Stringtabellen-Index: 26
Sektions-Header:
[Nr] Name Typ Adr Off Größe ES Flg Lk Inf Ar
[ 0] NULL 00000000 000000 000000 00 0 0 0
[ 1] .interp PROGBITS 00008134 000134 000019 00 A 0 0 1
[ 2] .note.ABI-tag NOTE 00008150 000150 000020 00 A 0 0 4
[ 3] .hash HASH 00008170 000170 0008ac 04 A 4 0 4
[ 4] .dynsym DYNSYM 00008a1c 000a1c 001220 10 A 5 1 4
[ 5] .dynstr STRTAB 00009c3c 001c3c 00090e 00 A 0 0 1
[ 6] .gnu.version VERSYM 0000a54a 00254a 000244 02 A 4 0 2
[ 7] .gnu.version_r VERNEED 0000a790 002790 000020 00 A 5 1 4
[ 8] .rel.dyn REL 0000a7b0 0027b0 000038 08 A 4 0 4
[ 9] .rel.plt REL 0000a7e8 0027e8 0008d0 08 A 4 11 4
[10] .init PROGBITS 0000b0b8 0030b8 00000c 00 AX 0 0 4
[11] .plt PROGBITS 0000b0c4 0030c4 000ddc 04 AX 0 0 4
[12] .text PROGBITS 0000bea0 003ea0 03b116 00 AX 0 0 8
[13] .fini PROGBITS 00046fb8 03efb8 000008 00 AX 0 0 4
[14] .rodata PROGBITS 00046fc0 03efc0 00f0af 00 A 0 0 4
[15] .ARM.exidx ARM_EXIDX 00056070 04e070 000008 00 AL 12 0 4
[16] .eh_frame PROGBITS 00056078 04e078 000004 00 A 0 0 4
[17] .init_array INIT_ARRAY 0005e07c 04e07c 000004 00 WA 0 0 4
[18] .fini_array FINI_ARRAY 0005e080 04e080 000004 00 WA 0 0 4
[19] .jcr PROGBITS 0005e084 04e084 000004 00 WA 0 0 4
[20] .dynamic DYNAMIC 0005e088 04e088 0000e8 08 WA 5 0 4
[21] .got PROGBITS 0005e170 04e170 00047c 04 WA 0 0 4
[22] .data PROGBITS 0005e5ec 04e5ec 00013d 00 WA 0 0 4
[23] .bss NOBITS 0005e730 04e729 00223c 00 WA 0 0 8
[24] .ARM.attributes ARM_ATTRIBUTES 00000000 04e729 000037 00 0 0 1
[25] .gnu_debuglink PROGBITS 00000000 04e760 00000c 00 0 0 1
[26] .shstrtab STRTAB 00000000 04e76c 0000e9 00 0 0 1
Key to Flags:
W (write), A (alloc), X (execute), M (merge), S (strings)
I (info), L (link order), G (group), T (TLS), E (exclude), x (unknown)
O (extra OS processing required) o (OS specific), p (processor specific)
Programm-Header:
Typ Offset VirtAdr PhysAdr DateiGr SpeiGr Flg Ausr.
EXIDX 0x04e070 0x00056070 0x00056070 0x00008 0x00008 R 0x4
PHDR 0x000034 0x00008034 0x00008034 0x00100 0x00100 R E 0x4
INTERP 0x000134 0x00008134 0x00008134 0x00019 0x00019 R 0x1
[Programminterpreter anfordern: /lib/ld-linux-armhf.so.3]
LOAD 0x000000 0x00008000 0x00008000 0x4e07c 0x4e07c R E 0x8000
LOAD 0x04e07c 0x0005e07c 0x0005e07c 0x006ad 0x028f0 RW 0x8000
DYNAMIC 0x04e088 0x0005e088 0x0005e088 0x000e8 0x000e8 RW 0x4
NOTE 0x000150 0x00008150 0x00008150 0x00020 0x00020 R 0x4
GNU_STACK 0x000000 0x00000000 0x00000000 0x00000 0x00000 RW 0x10
Abbildung von Sektion nach Segment:
Segmentsektionen...
00 .ARM.exidx
01
02 .interp
03 .interp .note.ABI-tag .hash .dynsym .dynstr .gnu.version .gnu.version_r .rel.dyn .rel.plt .init .plt .text .fini .rodata .ARM.exidx .eh_frame
04 .init_array .fini_array .jcr .dynamic .got .data .bss
05 .dynamic
06 .note.ABI-tag
07
[-- Attachment #4: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
2014-09-29 13:56 ` Tim Sander
@ 2014-10-01 13:02 ` Michael Olbrich
0 siblings, 0 replies; 16+ messages in thread
From: Michael Olbrich @ 2014-10-01 13:02 UTC (permalink / raw)
To: ptxdist
On Mon, Sep 29, 2014 at 03:56:40PM +0200, Tim Sander wrote:
> Am Freitag, 26. September 2014, 08:46:21 schrieb Michael Olbrich:
> > On Wed, Sep 24, 2014 at 03:43:10PM +0200, Tim Sander wrote:
> > > > I'm happy to announce that I've just released
> > > > OSELAS.Toolchain-2013.12.2.
> > > >
> > > > This is a bugfix-only release. The relevant changes since 2013.12.1 are:
> > > > - The toolchains can now be built with make 4.0
> > > > - Some toolchains did not optimize for the correct CPU. The code works
> > > > but
> > > >
> > > > might be slower. This is fixed now.
> > > >
> > > > - All security relevant fixes mentioned in the glibc 2.19 changelog
> > > > have
> > > >
> > > > been added for glibc 2.18 based toolchains.
> > > >
> > > > - All generated toolchain archives are now XZ comressed.
> > >
> > > While i have used this toolchain arm-v7a-linux-gnueabihf with an Xilinx
> > > Zynx compiling nearly the same Project with a different Kernelconfig /DTB
> > > for Altera SOC fails with this toolchain !?! The kernel boots but on
> > > mounting the rootfs it fails to execute any binary?
> >
> > Is the dynamic linker (whatever /lib/ld-linux-armhf.so.3 points to)
> > executable? Do you have a working system? Boot it and try to chroot into
> > your new system. You get better error messages that way.
> Ok i have now setup booted into the environment compiled with
> OSELAS.Toolchain-2012.12.1/arm-cortexa9-linux-gnueabihf, mounted the other
> system via nfs and tried to start any executable:
Carefull: you need to chroot into the new root, otherwise you'll use the
wrong linker (/lib/ld-linux-armhf.so.3). Did you do this?
> /mnt/bin/busybox: line 1: syntax error: unexpected word (expecting ")")
>
> (thats with OSELAS.Toolchain-2013.12.2/arm-v7a-linux-gnueabihf on Altera SOC)
>
> I have taken a look at both busyboxes and have run them through "readelf -e"
> (attached). The only difference which sprung to my eye was the hardfloat
> support, which i don't understand as both toolchains should be hardfloat
> toolchains.
They are: The linker is /lib/ld-linux-armhf.so.3 for both. I'm not sure why
the old binary is missing the hf flag.
> Starting the binary with strace gives:
> execve("mnt/bin/busybox", ["mnt/bin/busybox"], [/* 11 vars */]) = -1 ENOEXEC
> (Exec format error)
> write(2, "strace: exec: Exec format error\n", 32strace: exec: Exec format
> error
> ) = 32
> exit_group(1) = ?
> +++ exited with 1 +++
>
> So i have an execution error and the shell error seems to be the shell
> fallback from the kernel.
>
> Another thing which caught my attention was the fact that:
> objdump -d bin/busybox |grep UNDEFINED |wc -l
> is 364 for the old and 13478 for the new toolchain.
Try using objdump from the toolchain. Do you still get these results?
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2014-10-01 13:02 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-05-07 8:07 [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released Michael Olbrich
2014-05-07 8:41 ` Alexander Dahl
2014-05-07 10:23 ` Michael Olbrich
2014-05-07 11:16 ` Alexander Dahl
2014-05-07 12:15 ` Michael Olbrich
2014-05-07 12:30 ` Bernhard Walle
2014-05-07 14:39 ` Uwe Kleine-König
2014-05-07 13:01 ` Alexander Dahl
2014-05-07 13:08 ` Michael Olbrich
2014-09-24 13:43 ` Tim Sander
2014-09-24 18:01 ` Uwe Kleine-König
2014-09-26 6:09 ` Tim Sander
2014-09-26 6:46 ` Michael Olbrich
2014-09-29 13:47 ` Tim Sander
2014-09-29 13:56 ` Tim Sander
2014-10-01 13:02 ` Michael Olbrich
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox