| Message ID | 1390798091-24747-1-git-send-email-afaerber@suse.de |
|---|---|
| State | Accepted |
| Delegated to: | Albert ARIBAUD |
| Headers | show |
Dear Andreas Färber, In message <1390798091-24747-1-git-send-email-afaerber@suse.de> you wrote: > Avoids "could not find output section .gnu.hash" ld.bfd errors on openSUSE. > > Cc: Albert Aribaud <albert.u.boot@aribaud.net> > Cc: Tom Rini <trini@ti.com> > Signed-off-by: Andreas Färber <afaerber@suse.de> > --- > More changes like this may be needed, but these I compile-tested with > v2014.01 (regression from v2013.10). colibri_t20_iris was runtime-tested. > GCC 4.8.2 r206511, binutils 2.24 > > arch/arm/cpu/u-boot.lds | 1 + > board/ti/am335x/u-boot.lds | 1 + > 2 files changed, 2 insertions(+) Is this an ARM specific issue, or other architectures affected as well? Best regards, Wolfgang Denk
Hello, Am 27.01.2014 15:24, schrieb Wolfgang Denk: > In message <1390798091-24747-1-git-send-email-afaerber@suse.de> you wrote: >> Avoids "could not find output section .gnu.hash" ld.bfd errors on openSUSE. >> >> Cc: Albert Aribaud <albert.u.boot@aribaud.net> >> Cc: Tom Rini <trini@ti.com> >> Signed-off-by: Andreas Färber <afaerber@suse.de> >> --- >> More changes like this may be needed, but these I compile-tested with >> v2014.01 (regression from v2013.10). colibri_t20_iris was runtime-tested. >> GCC 4.8.2 r206511, binutils 2.24 >> >> arch/arm/cpu/u-boot.lds | 1 + >> board/ti/am335x/u-boot.lds | 1 + >> 2 files changed, 2 insertions(+) > > Is this an ARM specific issue, or other architectures affected as > well? I figured out that the section was apparently not caught by the .gnu* wildcard and this patch fixed our build for the following ARM configs: am335x_evm arndale colibri_t20_iris cubieboard highbank hyundai_a7hd mele_a1000 mx53loco omap3_beagle omap4_panda paz00 rpi_b My guess was that this could be related to the arm-only commit: http://git.denx.de/?p=u-boot.git;a=commit;h=47ed5dd031d7d2c587e6afd386e79ccec1a1b7f7 (which touches on a few more .lds files than mine) But I see nothing ARM-specific in .gnu.hash sections, so other architectures might in theory be affected as well. Cf. http://sourceware.org/ml/binutils/2006-10/msg00377.html I did read your post for ELDK pointing someone to an FAQ entry on not using gcc-specific flags with ld, but for one I did not spot such a thing in the ld command line, and for another our toolchain did not change and v2013.10 builds succeed whereas v2014.01 builds failed without the patch. I could try to git-bisect the offending change if necessary. Best regards, Andreas
Dear Andreas Färber, In message <52E6A96B.1080002@suse.de> you wrote: > > I figured out that the section was apparently not caught by the .gnu* > wildcard and this patch fixed our build for the following ARM configs: Do I understand you correctly that this fixes a _build_ error? So we can assume as long as the other archtiectures build fine, they are not affected by this? Best regards, Wolfgang Denk
Dear Wolfgang Denk, Am 27.01.2014 20:11, schrieb Wolfgang Denk: > In message <52E6A96B.1080002@suse.de> you wrote: >> >> I figured out that the section was apparently not caught by the .gnu* >> wildcard and this patch fixed our build for the following ARM configs: > > Do I understand you correctly that this fixes a _build_ error? So we > can assume as long as the other archtiectures build fine, they are not > affected by this? Affirmative. :) Best regards, Andreas
Dear Andreas Färber, In message <52E7B855.2080906@suse.de> you wrote: > > > Do I understand you correctly that this fixes a _build_ error? So we > > can assume as long as the other archtiectures build fine, they are not > > affected by this? > > Affirmative. :) OK, then we can just lean back and relax :) Thanks! Best regards, Wolfgang Denk
Hi Andreas, On Mon, 27 Jan 2014 19:46:03 +0100, Andreas Färber <afaerber@suse.de> wrote: > Hello, > > Am 27.01.2014 15:24, schrieb Wolfgang Denk: > > In message <1390798091-24747-1-git-send-email-afaerber@suse.de> you wrote: > >> Avoids "could not find output section .gnu.hash" ld.bfd errors on openSUSE. > >> > >> Cc: Albert Aribaud <albert.u.boot@aribaud.net> > >> Cc: Tom Rini <trini@ti.com> > >> Signed-off-by: Andreas Färber <afaerber@suse.de> > >> --- > >> More changes like this may be needed, but these I compile-tested with > >> v2014.01 (regression from v2013.10). colibri_t20_iris was runtime-tested. > >> GCC 4.8.2 r206511, binutils 2.24 > >> > >> arch/arm/cpu/u-boot.lds | 1 + > >> board/ti/am335x/u-boot.lds | 1 + > >> 2 files changed, 2 insertions(+) > > > > Is this an ARM specific issue, or other architectures affected as > > well? > > I figured out that the section was apparently not caught by the .gnu* > wildcard and this patch fixed our build for the following ARM configs: > > am335x_evm > arndale > colibri_t20_iris > cubieboard > highbank > hyundai_a7hd > mele_a1000 > mx53loco > omap3_beagle > omap4_panda > paz00 > rpi_b > > My guess was that this could be related to the arm-only commit: > http://git.denx.de/?p=u-boot.git;a=commit;h=47ed5dd031d7d2c587e6afd386e79ccec1a1b7f7 > (which touches on a few more .lds files than mine) > > But I see nothing ARM-specific in .gnu.hash sections, so other > architectures might in theory be affected as well. > Cf. http://sourceware.org/ml/binutils/2006-10/msg00377.html > > I did read your post for ELDK pointing someone to an FAQ entry on not > using gcc-specific flags with ld, but for one I did not spot such a > thing in the ld command line, and for another our toolchain did not > change and v2013.10 builds succeed whereas v2014.01 builds failed > without the patch. I could try to git-bisect the offending change if > necessary. Using gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu7), I cannot see any issues on these boards: am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle omap4_panda paz00 rpi_b On arndale, issues are due to warnings unrelated to linking. Cubieboard, hyundai_a7hd, mele_a1000 are not in mainline AFAICT (but I'd like to see mele_a1000 in, as this might mean mele_a1000g could follow. :) ) Can you point me to the toolchain you are using, and if you are not building mainline code, can you make this code available to me somehow? > Best regards, > > Andreas Amicalement,
Hi Albert, On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD <albert.u.boot@aribaud.net> wrote: > Hi Andreas, > > On Mon, 27 Jan 2014 19:46:03 +0100, Andreas Färber <afaerber@suse.de> > wrote: > > > Hello, > > > > Am 27.01.2014 15:24, schrieb Wolfgang Denk: > > > In message <1390798091-24747-1-git-send-email-afaerber@suse.de> you wrote: > > >> Avoids "could not find output section .gnu.hash" ld.bfd errors on openSUSE. > > >> > > >> Cc: Albert Aribaud <albert.u.boot@aribaud.net> > > >> Cc: Tom Rini <trini@ti.com> > > >> Signed-off-by: Andreas Färber <afaerber@suse.de> > > >> --- > > >> More changes like this may be needed, but these I compile-tested with > > >> v2014.01 (regression from v2013.10). colibri_t20_iris was runtime-tested. > > >> GCC 4.8.2 r206511, binutils 2.24 > > >> > > >> arch/arm/cpu/u-boot.lds | 1 + > > >> board/ti/am335x/u-boot.lds | 1 + > > >> 2 files changed, 2 insertions(+) > > > > > > Is this an ARM specific issue, or other architectures affected as > > > well? > > > > I figured out that the section was apparently not caught by the .gnu* > > wildcard and this patch fixed our build for the following ARM configs: > > > > am335x_evm > > arndale > > colibri_t20_iris > > cubieboard > > highbank > > hyundai_a7hd > > mele_a1000 > > mx53loco > > omap3_beagle > > omap4_panda > > paz00 > > rpi_b > > > > My guess was that this could be related to the arm-only commit: > > http://git.denx.de/?p=u-boot.git;a=commit;h=47ed5dd031d7d2c587e6afd386e79ccec1a1b7f7 > > (which touches on a few more .lds files than mine) > > > > But I see nothing ARM-specific in .gnu.hash sections, so other > > architectures might in theory be affected as well. > > Cf. http://sourceware.org/ml/binutils/2006-10/msg00377.html > > > > I did read your post for ELDK pointing someone to an FAQ entry on not > > using gcc-specific flags with ld, but for one I did not spot such a > > thing in the ld command line, and for another our toolchain did not > > change and v2013.10 builds succeed whereas v2014.01 builds failed > > without the patch. I could try to git-bisect the offending change if > > necessary. > > Using gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu7), I cannot see > any issues on these boards: > > am335x_evm > colibri_t20_iris > highbank > mx53loco > omap3_beagle > omap4_panda > paz00 > rpi_b > > On arndale, issues are due to warnings unrelated to linking. > > Cubieboard, hyundai_a7hd, mele_a1000 are not in mainline AFAICT (but I'd > like to see mele_a1000 in, as this might mean mele_a1000g could > follow. :) ) > > Can you point me to the toolchain you are using, and if you are not > building mainline code, can you make this code available to me somehow? Ping. > > Best regards, > > > > Andreas Amicalement,
Hi Albert, Am 22.02.2014 14:27, schrieb Albert ARIBAUD: > Hi Albert, > > On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD > <albert.u.boot@aribaud.net> wrote: > >> Hi Andreas, >> >> On Mon, 27 Jan 2014 19:46:03 +0100, Andreas Färber <afaerber@suse.de> >> wrote: >> >>> Hello, >>> >>> Am 27.01.2014 15:24, schrieb Wolfgang Denk: >>>> In message <1390798091-24747-1-git-send-email-afaerber@suse.de> you wrote: >>>>> Avoids "could not find output section .gnu.hash" ld.bfd errors on openSUSE. >>>>> >>>>> Cc: Albert Aribaud <albert.u.boot@aribaud.net> >>>>> Cc: Tom Rini <trini@ti.com> >>>>> Signed-off-by: Andreas Färber <afaerber@suse.de> >>>>> --- >>>>> More changes like this may be needed, but these I compile-tested with >>>>> v2014.01 (regression from v2013.10). colibri_t20_iris was runtime-tested. >>>>> GCC 4.8.2 r206511, binutils 2.24 >>>>> >>>>> arch/arm/cpu/u-boot.lds | 1 + >>>>> board/ti/am335x/u-boot.lds | 1 + >>>>> 2 files changed, 2 insertions(+) >>>> >>>> Is this an ARM specific issue, or other architectures affected as >>>> well? >>> >>> I figured out that the section was apparently not caught by the .gnu* >>> wildcard and this patch fixed our build for the following ARM configs: >>> >>> am335x_evm >>> arndale >>> colibri_t20_iris >>> cubieboard >>> highbank >>> hyundai_a7hd >>> mele_a1000 >>> mx53loco >>> omap3_beagle >>> omap4_panda >>> paz00 >>> rpi_b >>> >>> My guess was that this could be related to the arm-only commit: >>> http://git.denx.de/?p=u-boot.git;a=commit;h=47ed5dd031d7d2c587e6afd386e79ccec1a1b7f7 >>> (which touches on a few more .lds files than mine) >>> >>> But I see nothing ARM-specific in .gnu.hash sections, so other >>> architectures might in theory be affected as well. >>> Cf. http://sourceware.org/ml/binutils/2006-10/msg00377.html >>> >>> I did read your post for ELDK pointing someone to an FAQ entry on not >>> using gcc-specific flags with ld, but for one I did not spot such a >>> thing in the ld command line, and for another our toolchain did not >>> change and v2013.10 builds succeed whereas v2014.01 builds failed >>> without the patch. I could try to git-bisect the offending change if >>> necessary. >> >> Using gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu7), I cannot see >> any issues on these boards: >> >> am335x_evm >> colibri_t20_iris >> highbank >> mx53loco >> omap3_beagle >> omap4_panda >> paz00 >> rpi_b >> >> On arndale, issues are due to warnings unrelated to linking. >> >> Cubieboard, hyundai_a7hd, mele_a1000 are not in mainline AFAICT (but I'd >> like to see mele_a1000 in, as this might mean mele_a1000g could >> follow. :) ) Sorry, missed that. I had merged v2014.01 into the sunxi tree and updated our downstream patch from it (v2014.01-sunxi.patch). It did not seem to touch on Makefile or ldscript in an interfering way. Cf. https://github.com/afaerber/u-boot/commits/sunxi Other downstream changes include forcing ext4 support for SPL and tweaking boot.scr vs. boot.scr.uimg filename inconsistencies. >> Can you point me to the toolchain you are using, and if you are not >> building mainline code, can you make this code available to me somehow? > > Ping. Somehow I did not receive the previous message... Our latest GCC 4.8.2 can be found here: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 Matching binutils 2.24 are here: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils Our latest U-Boot tarball and patches: https://build.opensuse.org/package/show/Base:System/u-boot Build logs can be found in the u-boot-* packages in the same project, with underscores stripped, e.g.: https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm Amicalement, Andreas
Hi Andreas, On Sun, 02 Mar 2014 18:57:14 +0100, Andreas Färber <afaerber@suse.de> wrote: > Hi Albert, > > Am 22.02.2014 14:27, schrieb Albert ARIBAUD: > > Hi Albert, > > > > On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD > > <albert.u.boot@aribaud.net> wrote: > > > >> Hi Andreas, > >> > >> On Mon, 27 Jan 2014 19:46:03 +0100, Andreas Färber <afaerber@suse.de> > >> wrote: > >> > >>> Hello, > >>> > >>> Am 27.01.2014 15:24, schrieb Wolfgang Denk: > >>>> In message <1390798091-24747-1-git-send-email-afaerber@suse.de> you wrote: > >>>>> Avoids "could not find output section .gnu.hash" ld.bfd errors on openSUSE. > >>>>> > >>>>> Cc: Albert Aribaud <albert.u.boot@aribaud.net> > >>>>> Cc: Tom Rini <trini@ti.com> > >>>>> Signed-off-by: Andreas Färber <afaerber@suse.de> > >>>>> --- > >>>>> More changes like this may be needed, but these I compile-tested with > >>>>> v2014.01 (regression from v2013.10). colibri_t20_iris was runtime-tested. > >>>>> GCC 4.8.2 r206511, binutils 2.24 > >>>>> > >>>>> arch/arm/cpu/u-boot.lds | 1 + > >>>>> board/ti/am335x/u-boot.lds | 1 + > >>>>> 2 files changed, 2 insertions(+) > >>>> > >>>> Is this an ARM specific issue, or other architectures affected as > >>>> well? > >>> > >>> I figured out that the section was apparently not caught by the .gnu* > >>> wildcard and this patch fixed our build for the following ARM configs: > >>> > >>> am335x_evm > >>> arndale > >>> colibri_t20_iris > >>> cubieboard > >>> highbank > >>> hyundai_a7hd > >>> mele_a1000 > >>> mx53loco > >>> omap3_beagle > >>> omap4_panda > >>> paz00 > >>> rpi_b > >>> > >>> My guess was that this could be related to the arm-only commit: > >>> http://git.denx.de/?p=u-boot.git;a=commit;h=47ed5dd031d7d2c587e6afd386e79ccec1a1b7f7 > >>> (which touches on a few more .lds files than mine) > >>> > >>> But I see nothing ARM-specific in .gnu.hash sections, so other > >>> architectures might in theory be affected as well. > >>> Cf. http://sourceware.org/ml/binutils/2006-10/msg00377.html > >>> > >>> I did read your post for ELDK pointing someone to an FAQ entry on not > >>> using gcc-specific flags with ld, but for one I did not spot such a > >>> thing in the ld command line, and for another our toolchain did not > >>> change and v2013.10 builds succeed whereas v2014.01 builds failed > >>> without the patch. I could try to git-bisect the offending change if > >>> necessary. > >> > >> Using gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu7), I cannot see > >> any issues on these boards: > >> > >> am335x_evm > >> colibri_t20_iris > >> highbank > >> mx53loco > >> omap3_beagle > >> omap4_panda > >> paz00 > >> rpi_b > >> > >> On arndale, issues are due to warnings unrelated to linking. > >> > >> Cubieboard, hyundai_a7hd, mele_a1000 are not in mainline AFAICT (but I'd > >> like to see mele_a1000 in, as this might mean mele_a1000g could > >> follow. :) ) > > Sorry, missed that. I had merged v2014.01 into the sunxi tree and > updated our downstream patch from it (v2014.01-sunxi.patch). It did not > seem to touch on Makefile or ldscript in an interfering way. > Cf. https://github.com/afaerber/u-boot/commits/sunxi > > Other downstream changes include forcing ext4 support for SPL and > tweaking boot.scr vs. boot.scr.uimg filename inconsistencies. > > >> Can you point me to the toolchain you are using, and if you are not > >> building mainline code, can you make this code available to me somehow? > > > > Ping. > > Somehow I did not receive the previous message... > > Our latest GCC 4.8.2 can be found here: > https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 > > Matching binutils 2.24 are here: > https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils > > Our latest U-Boot tarball and patches: > https://build.opensuse.org/package/show/Base:System/u-boot > Build logs can be found in the u-boot-* packages in the same project, > with underscores stripped, e.g.: > https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm Thanks for your reply. Apparently, the problem does not appear for the boards in mainline U-Boot which I listed above with the source code from our v2014.01 tag and using gcc 4.8.1 from Linaro. I can install 4.8.2, but meanwhile, can you try to build v2014.01 for these boards with your setup? am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle omap4_panda paz00 rpi_b > Amicalement, > > Andreas Amicalement,
Hi Albert, Am 02.03.2014 20:15, schrieb Albert ARIBAUD: > Hi Andreas, > > On Sun, 02 Mar 2014 18:57:14 +0100, Andreas Färber <afaerber@suse.de> > wrote: > >> Hi Albert, >> >> Am 22.02.2014 14:27, schrieb Albert ARIBAUD: >>> On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD >>> <albert.u.boot@aribaud.net> wrote: >>> >>>> Can you point me to the toolchain you are using, and if you are not >>>> building mainline code, can you make this code available to me somehow? [...] >> Our latest GCC 4.8.2 can be found here: >> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 >> >> Matching binutils 2.24 are here: >> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils >> >> Our latest U-Boot tarball and patches: >> https://build.opensuse.org/package/show/Base:System/u-boot >> Build logs can be found in the u-boot-* packages in the same project, >> with underscores stripped, e.g.: >> https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm > > Thanks for your reply. Apparently, the problem does not appear for the > boards in mainline U-Boot which I listed above with the source code > from our v2014.01 tag and using gcc 4.8.1 from Linaro. I can install > 4.8.2, but meanwhile, can you try to build v2014.01 for these boards > with your setup? > > am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle > omap4_panda paz00 rpi_b I have commented out the patch in: https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System While there are apparently frequent rebuilds scheduled ATM, it seemed like the colibri_t20_iris config intermittently built OK without it. Maybe some gcc 4.8 stable branch update [1] resolved it ... will keep an eye on the build status to confirm. If everything builds, I'm happy. Amicalement, Andreas [1] https://build.opensuse.org/package/view_file/openSUSE:Factory:ARM/gcc48/gcc48.changes?expand=1
Am 02.03.2014 21:57, schrieb Andreas Färber: > Hi Albert, > > Am 02.03.2014 20:15, schrieb Albert ARIBAUD: >> Hi Andreas, >> >> On Sun, 02 Mar 2014 18:57:14 +0100, Andreas Färber <afaerber@suse.de> >> wrote: >> >>> Hi Albert, >>> >>> Am 22.02.2014 14:27, schrieb Albert ARIBAUD: >>>> On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD >>>> <albert.u.boot@aribaud.net> wrote: >>>> >>>>> Can you point me to the toolchain you are using, and if you are not >>>>> building mainline code, can you make this code available to me somehow? > [...] >>> Our latest GCC 4.8.2 can be found here: >>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 >>> >>> Matching binutils 2.24 are here: >>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils >>> >>> Our latest U-Boot tarball and patches: >>> https://build.opensuse.org/package/show/Base:System/u-boot >>> Build logs can be found in the u-boot-* packages in the same project, >>> with underscores stripped, e.g.: >>> https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm >> >> Thanks for your reply. Apparently, the problem does not appear for the >> boards in mainline U-Boot which I listed above with the source code >> from our v2014.01 tag and using gcc 4.8.1 from Linaro. I can install >> 4.8.2, but meanwhile, can you try to build v2014.01 for these boards >> with your setup? >> >> am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle >> omap4_panda paz00 rpi_b > > I have commented out the patch in: > https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System > > While there are apparently frequent rebuilds scheduled ATM, it seemed > like the colibri_t20_iris config intermittently built OK without it. > Maybe some gcc 4.8 stable branch update [1] resolved it ... will keep an > eye on the build status to confirm. If everything builds, I'm happy. Nah, still fails without the patch: [ 178s] gcc -E -g -Os -ffunction-sections -fdata-sections -fno-common -ffixed-r9 -msoft-float -D__KERNEL__ -DCONFIG_SYS_TEXT_BASE=0x0010E000 -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/include -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/include -pipe -DCONFIG_ARM -D__ARM__ -marm -mno-thumb-interwork -mabi=aapcs-linux -mword-relocations -march=armv7-a -include /home/abuild/rpmbuild/BUILD/u-boot-2014.01/include/u-boot/u-boot.lds.h -DCPUDIR=arch/arm/cpu/armv7 -ansi -D__ASSEMBLY__ -P - </home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/cpu/u-boot.lds >u-boot.lds [ 178s] cd /home/abuild/rpmbuild/BUILD/u-boot-2014.01 && ld.bfd -pie -T u-boot.lds --gc-sections -Bstatic -Ttext 0x0010E000 arch/arm/cpu/armv7/start.o --start-group arch/arm/cpu/armv7/built-in.o arch/arm/cpu/armv7/tegra20/built-in.o arch/arm/cpu/built-in.o arch/arm/lib/built-in.o board/toradex/colibri_t20_iris/built-in.o common/built-in.o disk/built-in.o drivers/built-in.o drivers/dma/built-in.o drivers/gpio/built-in.o drivers/i2c/built-in.o drivers/input/built-in.o drivers/mmc/built-in.o drivers/mtd/built-in.o drivers/mtd/nand/built-in.o drivers/mtd/onenand/built-in.o drivers/mtd/spi/built-in.o drivers/net/built-in.o drivers/net/phy/built-in.o drivers/pci/built-in.o drivers/power/battery/built-in.o drivers/power/built-in.o drivers/power/fuel_gauge/built-in.o drivers/power/mfd/built-in.o drivers/power/pmic/built-in.o drivers/serial/built-in.o drivers/spi/built-in.o drivers/usb/eth/built-in.o drivers/usb/gadget/built-in.o drivers/usb/host/built-in.o drivers/usb/musb-new/built-in.o drivers/usb/musb/built-in.o drivers/usb/phy/built-in.o drivers/usb/ulpi/built-in.o fs/built-in.o lib/built-in.o lib/libfdt/built-in.o net/built-in.o test/built-in.o --end-group /home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/lib/eabi_compat.o -L /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8 -lgcc -Map u-boot.map -o u-boot [ 178s] ld.bfd: u-boot: could not find output section .gnu.hash [ 178s] ld.bfd: final link failed: Nonrepresentable section on output [ 178s] Makefile:556: recipe for target 'u-boot' failed [ 178s] make: *** [u-boot] Error 1 https://build.opensuse.org/package/live_build_log/home:a_faerber:branches:Base:System/u-boot-colibrit20iris/openSUSE_Factory_ARM/armv7l Regards, Andreas
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/02/2014 05:00 PM, Andreas Färber wrote: > Am 02.03.2014 21:57, schrieb Andreas Färber: >> Hi Albert, >> >> Am 02.03.2014 20:15, schrieb Albert ARIBAUD: >>> Hi Andreas, >>> >>> On Sun, 02 Mar 2014 18:57:14 +0100, Andreas Färber <afaerber@suse.de> >>> wrote: >>> >>>> Hi Albert, >>>> >>>> Am 22.02.2014 14:27, schrieb Albert ARIBAUD: >>>>> On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD >>>>> <albert.u.boot@aribaud.net> wrote: >>>>> >>>>>> Can you point me to the toolchain you are using, and if you are not >>>>>> building mainline code, can you make this code available to me somehow? >> [...] >>>> Our latest GCC 4.8.2 can be found here: >>>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 >>>> >>>> Matching binutils 2.24 are here: >>>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils >>>> >>>> Our latest U-Boot tarball and patches: >>>> https://build.opensuse.org/package/show/Base:System/u-boot >>>> Build logs can be found in the u-boot-* packages in the same project, >>>> with underscores stripped, e.g.: >>>> https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm >>> >>> Thanks for your reply. Apparently, the problem does not appear for the >>> boards in mainline U-Boot which I listed above with the source code >>> from our v2014.01 tag and using gcc 4.8.1 from Linaro. I can install >>> 4.8.2, but meanwhile, can you try to build v2014.01 for these boards >>> with your setup? >>> >>> am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle >>> omap4_panda paz00 rpi_b >> >> I have commented out the patch in: >> https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System >> >> While there are apparently frequent rebuilds scheduled ATM, it seemed >> like the colibri_t20_iris config intermittently built OK without it. >> Maybe some gcc 4.8 stable branch update [1] resolved it ... will keep an >> eye on the build status to confirm. If everything builds, I'm happy. > > Nah, still fails without the patch: > > [ 178s] gcc -E -g -Os -ffunction-sections -fdata-sections > -fno-common -ffixed-r9 -msoft-float -D__KERNEL__ > -DCONFIG_SYS_TEXT_BASE=0x0010E000 > -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/include > -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/include > -fno-builtin -ffreestanding -nostdinc -isystem > /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/include -pipe -DCONFIG_ARM > -D__ARM__ -marm -mno-thumb-interwork -mabi=aapcs-linux > -mword-relocations -march=armv7-a -include > /home/abuild/rpmbuild/BUILD/u-boot-2014.01/include/u-boot/u-boot.lds.h > -DCPUDIR=arch/arm/cpu/armv7 -ansi -D__ASSEMBLY__ -P - > </home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/cpu/u-boot.lds >> u-boot.lds > [ 178s] cd /home/abuild/rpmbuild/BUILD/u-boot-2014.01 && ld.bfd -pie > -T u-boot.lds --gc-sections -Bstatic -Ttext 0x0010E000 > arch/arm/cpu/armv7/start.o --start-group arch/arm/cpu/armv7/built-in.o > arch/arm/cpu/armv7/tegra20/built-in.o arch/arm/cpu/built-in.o > arch/arm/lib/built-in.o board/toradex/colibri_t20_iris/built-in.o > common/built-in.o disk/built-in.o drivers/built-in.o > drivers/dma/built-in.o drivers/gpio/built-in.o drivers/i2c/built-in.o > drivers/input/built-in.o drivers/mmc/built-in.o drivers/mtd/built-in.o > drivers/mtd/nand/built-in.o drivers/mtd/onenand/built-in.o > drivers/mtd/spi/built-in.o drivers/net/built-in.o > drivers/net/phy/built-in.o drivers/pci/built-in.o > drivers/power/battery/built-in.o drivers/power/built-in.o > drivers/power/fuel_gauge/built-in.o drivers/power/mfd/built-in.o > drivers/power/pmic/built-in.o drivers/serial/built-in.o > drivers/spi/built-in.o drivers/usb/eth/built-in.o > drivers/usb/gadget/built-in.o drivers/usb/host/built-in.o > drivers/usb/musb-new/built-in.o drivers/usb/musb/built-in.o > drivers/usb/phy/built-in.o drivers/usb/ulpi/built-in.o fs/built-in.o > lib/built-in.o lib/libfdt/built-in.o net/built-in.o test/built-in.o > --end-group > /home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/lib/eabi_compat.o > -L /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8 -lgcc -Map u-boot.map -o > u-boot > [ 178s] ld.bfd: u-boot: could not find output section .gnu.hash > [ 178s] ld.bfd: final link failed: Nonrepresentable section on output > [ 178s] Makefile:556: recipe for target 'u-boot' failed > [ 178s] make: *** [u-boot] Error 1 > > > https://build.opensuse.org/package/live_build_log/home:a_faerber:branches:Base:System/u-boot-colibrit20iris/openSUSE_Factory_ARM/armv7l When this fails can you save the objdir? - -- Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTE8JzAAoJENk4IS6UOR1W8+AP/AprGiLzAuh3IVmZjvgRe71y enMJCdR8wo3Kw4DLPD78ZSiOXtS0R5zOHLqBcsj+4Aa3VmRAd40m0YbH0eG3QqXQ 9l9u6ueUGVsSTdhNuLnQaH71l5Ev+ykEPM6IUdvHELVrO9evc9guI0EMH3RYXOox qpRgQj9VJoRqpGzxE+UHoRgyKzK5N2UOnojhNCRVRvRk/EXTn7bWB554eTzZi2J1 9LnHiQX0MsI7SOWvXZ2jZTRCdMouJ7xMJkcUATRpgwj9m/H2QBlh4D9yZb5UD4K2 wO5wYpnr60s6H8c80HUlNrPXU1xPxi7cOMYaR9jXxFLjsGewac+e1mWNAR/zrDmI Vy0T+BvywGRp/cxOI29gYupxYxtp0ofHlYmhzz4XfspfLJiGXGrzEDzzGpzlXXDG OLEJ9v5KqM9PtTiBzj422V8Z9vxt+Hd0Iri/i8VhhIFv0KPf2spQQOoeIgLDst/V 8d2aiKFGTjl/J8aYsR7icA9+YHYqtCSeQR/npdEsoiPQoV/q5FyICAvJ7ztmOOiD gkko8RaeE0ps853UdaZs7LE5KyZJV7sF2OObo+fiNuLPk/YPWsv4dG1DsDzuRa3g DfAcaeKSqtL2SB7Se9X4FnETsHCh3BsfE6p/Wp8guJuzVrE/UhWh8lcLzDD8rxlu W6h1F96vTyM4BYCwGMT4 =IdOK -----END PGP SIGNATURE-----
Hi Andreas, (seems an answer from me yesterday didn't make it out of the NSA interceptors...) On Sun, 02 Mar 2014 23:00:19 +0100, Andreas Färber <afaerber@suse.de> wrote: > Am 02.03.2014 21:57, schrieb Andreas Färber: > > Hi Albert, > > > > Am 02.03.2014 20:15, schrieb Albert ARIBAUD: > >> Hi Andreas, > >> > >> On Sun, 02 Mar 2014 18:57:14 +0100, Andreas Färber <afaerber@suse.de> > >> wrote: > >> > >>> Hi Albert, > >>> > >>> Am 22.02.2014 14:27, schrieb Albert ARIBAUD: > >>>> On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD > >>>> <albert.u.boot@aribaud.net> wrote: > >>>> > >>>>> Can you point me to the toolchain you are using, and if you are not > >>>>> building mainline code, can you make this code available to me somehow? > > [...] > >>> Our latest GCC 4.8.2 can be found here: > >>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 > >>> > >>> Matching binutils 2.24 are here: > >>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils > >>> > >>> Our latest U-Boot tarball and patches: > >>> https://build.opensuse.org/package/show/Base:System/u-boot > >>> Build logs can be found in the u-boot-* packages in the same project, > >>> with underscores stripped, e.g.: > >>> https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm > >> > >> Thanks for your reply. Apparently, the problem does not appear for the > >> boards in mainline U-Boot which I listed above with the source code > >> from our v2014.01 tag and using gcc 4.8.1 from Linaro. I can install > >> 4.8.2, but meanwhile, can you try to build v2014.01 for these boards > >> with your setup? > >> > >> am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle > >> omap4_panda paz00 rpi_b > > > > I have commented out the patch in: > > https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System > > > > While there are apparently frequent rebuilds scheduled ATM, it seemed > > like the colibri_t20_iris config intermittently built OK without it. > > Maybe some gcc 4.8 stable branch update [1] resolved it ... will keep an > > eye on the build status to confirm. If everything builds, I'm happy. > > Nah, still fails without the patch: > > [ 178s] gcc -E -g -Os -ffunction-sections -fdata-sections > -fno-common -ffixed-r9 -msoft-float -D__KERNEL__ > -DCONFIG_SYS_TEXT_BASE=0x0010E000 > -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/include > -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/include > -fno-builtin -ffreestanding -nostdinc -isystem > /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/include -pipe -DCONFIG_ARM > -D__ARM__ -marm -mno-thumb-interwork -mabi=aapcs-linux > -mword-relocations -march=armv7-a -include > /home/abuild/rpmbuild/BUILD/u-boot-2014.01/include/u-boot/u-boot.lds.h > -DCPUDIR=arch/arm/cpu/armv7 -ansi -D__ASSEMBLY__ -P - > </home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/cpu/u-boot.lds > >u-boot.lds > [ 178s] cd /home/abuild/rpmbuild/BUILD/u-boot-2014.01 && ld.bfd -pie > -T u-boot.lds --gc-sections -Bstatic -Ttext 0x0010E000 > arch/arm/cpu/armv7/start.o --start-group arch/arm/cpu/armv7/built-in.o > arch/arm/cpu/armv7/tegra20/built-in.o arch/arm/cpu/built-in.o > arch/arm/lib/built-in.o board/toradex/colibri_t20_iris/built-in.o > common/built-in.o disk/built-in.o drivers/built-in.o > drivers/dma/built-in.o drivers/gpio/built-in.o drivers/i2c/built-in.o > drivers/input/built-in.o drivers/mmc/built-in.o drivers/mtd/built-in.o > drivers/mtd/nand/built-in.o drivers/mtd/onenand/built-in.o > drivers/mtd/spi/built-in.o drivers/net/built-in.o > drivers/net/phy/built-in.o drivers/pci/built-in.o > drivers/power/battery/built-in.o drivers/power/built-in.o > drivers/power/fuel_gauge/built-in.o drivers/power/mfd/built-in.o > drivers/power/pmic/built-in.o drivers/serial/built-in.o > drivers/spi/built-in.o drivers/usb/eth/built-in.o > drivers/usb/gadget/built-in.o drivers/usb/host/built-in.o > drivers/usb/musb-new/built-in.o drivers/usb/musb/built-in.o > drivers/usb/phy/built-in.o drivers/usb/ulpi/built-in.o fs/built-in.o > lib/built-in.o lib/libfdt/built-in.o net/built-in.o test/built-in.o > --end-group > /home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/lib/eabi_compat.o > -L /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8 -lgcc -Map u-boot.map -o > u-boot > [ 178s] ld.bfd: u-boot: could not find output section .gnu.hash > [ 178s] ld.bfd: final link failed: Nonrepresentable section on output > [ 178s] Makefile:556: recipe for target 'u-boot' failed > [ 178s] make: *** [u-boot] Error 1 You are trying this with your codebase, right? If so, can you try and build vanilla v2014.01 with the exact same build environment? If it builds fine, then can you tell me which changes your patch(es) made to linker scripts in your tree wrt 2014.01? > https://build.opensuse.org/package/live_build_log/home:a_faerber:branches:Base:System/u-boot-colibrit20iris/openSUSE_Factory_ARM/armv7l > > Regards, > Andreas Amicalement,
Hi Andreas, (seems an answer from me yesterday didn't make it out of the NSA interceptors...) On Sun, 02 Mar 2014 23:00:19 +0100, Andreas Färber <afaerber@suse.de> wrote: > Am 02.03.2014 21:57, schrieb Andreas Färber: > > Hi Albert, > > > > Am 02.03.2014 20:15, schrieb Albert ARIBAUD: > >> Hi Andreas, > >> > >> On Sun, 02 Mar 2014 18:57:14 +0100, Andreas Färber <afaerber@suse.de> > >> wrote: > >> > >>> Hi Albert, > >>> > >>> Am 22.02.2014 14:27, schrieb Albert ARIBAUD: > >>>> On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD > >>>> <albert.u.boot@aribaud.net> wrote: > >>>> > >>>>> Can you point me to the toolchain you are using, and if you are not > >>>>> building mainline code, can you make this code available to me somehow? > > [...] > >>> Our latest GCC 4.8.2 can be found here: > >>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 > >>> > >>> Matching binutils 2.24 are here: > >>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils > >>> > >>> Our latest U-Boot tarball and patches: > >>> https://build.opensuse.org/package/show/Base:System/u-boot > >>> Build logs can be found in the u-boot-* packages in the same project, > >>> with underscores stripped, e.g.: > >>> https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm > >> > >> Thanks for your reply. Apparently, the problem does not appear for the > >> boards in mainline U-Boot which I listed above with the source code > >> from our v2014.01 tag and using gcc 4.8.1 from Linaro. I can install > >> 4.8.2, but meanwhile, can you try to build v2014.01 for these boards > >> with your setup? > >> > >> am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle > >> omap4_panda paz00 rpi_b > > > > I have commented out the patch in: > > https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System > > > > While there are apparently frequent rebuilds scheduled ATM, it seemed > > like the colibri_t20_iris config intermittently built OK without it. > > Maybe some gcc 4.8 stable branch update [1] resolved it ... will keep an > > eye on the build status to confirm. If everything builds, I'm happy. > > Nah, still fails without the patch: > > [ 178s] gcc -E -g -Os -ffunction-sections -fdata-sections > -fno-common -ffixed-r9 -msoft-float -D__KERNEL__ > -DCONFIG_SYS_TEXT_BASE=0x0010E000 > -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/include > -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/include > -fno-builtin -ffreestanding -nostdinc -isystem > /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/include -pipe -DCONFIG_ARM > -D__ARM__ -marm -mno-thumb-interwork -mabi=aapcs-linux > -mword-relocations -march=armv7-a -include > /home/abuild/rpmbuild/BUILD/u-boot-2014.01/include/u-boot/u-boot.lds.h > -DCPUDIR=arch/arm/cpu/armv7 -ansi -D__ASSEMBLY__ -P - > </home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/cpu/u-boot.lds > >u-boot.lds > [ 178s] cd /home/abuild/rpmbuild/BUILD/u-boot-2014.01 && ld.bfd -pie > -T u-boot.lds --gc-sections -Bstatic -Ttext 0x0010E000 > arch/arm/cpu/armv7/start.o --start-group arch/arm/cpu/armv7/built-in.o > arch/arm/cpu/armv7/tegra20/built-in.o arch/arm/cpu/built-in.o > arch/arm/lib/built-in.o board/toradex/colibri_t20_iris/built-in.o > common/built-in.o disk/built-in.o drivers/built-in.o > drivers/dma/built-in.o drivers/gpio/built-in.o drivers/i2c/built-in.o > drivers/input/built-in.o drivers/mmc/built-in.o drivers/mtd/built-in.o > drivers/mtd/nand/built-in.o drivers/mtd/onenand/built-in.o > drivers/mtd/spi/built-in.o drivers/net/built-in.o > drivers/net/phy/built-in.o drivers/pci/built-in.o > drivers/power/battery/built-in.o drivers/power/built-in.o > drivers/power/fuel_gauge/built-in.o drivers/power/mfd/built-in.o > drivers/power/pmic/built-in.o drivers/serial/built-in.o > drivers/spi/built-in.o drivers/usb/eth/built-in.o > drivers/usb/gadget/built-in.o drivers/usb/host/built-in.o > drivers/usb/musb-new/built-in.o drivers/usb/musb/built-in.o > drivers/usb/phy/built-in.o drivers/usb/ulpi/built-in.o fs/built-in.o > lib/built-in.o lib/libfdt/built-in.o net/built-in.o test/built-in.o > --end-group > /home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/lib/eabi_compat.o > -L /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8 -lgcc -Map u-boot.map -o > u-boot > [ 178s] ld.bfd: u-boot: could not find output section .gnu.hash > [ 178s] ld.bfd: final link failed: Nonrepresentable section on output > [ 178s] Makefile:556: recipe for target 'u-boot' failed > [ 178s] make: *** [u-boot] Error 1 You are trying this with your codebase, right? If so, can you try and build vanilla v2014.01 with the exact same build environment? If it builds fine, then can you tell me which changes your patch(es) made to linker scripts in your tree wrt 2014.01? > https://build.opensuse.org/package/live_build_log/home:a_faerber:branches:Base:System/u-boot-colibrit20iris/openSUSE_Factory_ARM/armv7l > > Regards, > Andreas Amicalement,
On Sun, 2 Mar 2014, Andreas Färber wrote: > Am 02.03.2014 21:57, schrieb Andreas Färber: > > Hi Albert, > > > > Am 02.03.2014 20:15, schrieb Albert ARIBAUD: > >> Hi Andreas, > >> > >> On Sun, 02 Mar 2014 18:57:14 +0100, Andreas Färber <afaerber@suse.de> > >> wrote: > >> > >>> Hi Albert, > >>> > >>> Am 22.02.2014 14:27, schrieb Albert ARIBAUD: > >>>> On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD > >>>> <albert.u.boot@aribaud.net> wrote: > >>>> > >>>>> Can you point me to the toolchain you are using, and if you are not > >>>>> building mainline code, can you make this code available to me somehow? > > [...] > >>> Our latest GCC 4.8.2 can be found here: > >>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 > >>> > >>> Matching binutils 2.24 are here: > >>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils > >>> > >>> Our latest U-Boot tarball and patches: > >>> https://build.opensuse.org/package/show/Base:System/u-boot > >>> Build logs can be found in the u-boot-* packages in the same project, > >>> with underscores stripped, e.g.: > >>> https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm > >> > >> Thanks for your reply. Apparently, the problem does not appear for the > >> boards in mainline U-Boot which I listed above with the source code > >> from our v2014.01 tag and using gcc 4.8.1 from Linaro. I can install > >> 4.8.2, but meanwhile, can you try to build v2014.01 for these boards > >> with your setup? > >> > >> am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle > >> omap4_panda paz00 rpi_b > > > > I have commented out the patch in: > > https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System > > > > While there are apparently frequent rebuilds scheduled ATM, it seemed > > like the colibri_t20_iris config intermittently built OK without it. > > Maybe some gcc 4.8 stable branch update [1] resolved it ... will keep an > > eye on the build status to confirm. If everything builds, I'm happy. > > Nah, still fails without the patch: > > [ 178s] gcc -E -g -Os -ffunction-sections -fdata-sections > -fno-common -ffixed-r9 -msoft-float -D__KERNEL__ > -DCONFIG_SYS_TEXT_BASE=0x0010E000 > -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/include > -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/include > -fno-builtin -ffreestanding -nostdinc -isystem > /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/include -pipe -DCONFIG_ARM > -D__ARM__ -marm -mno-thumb-interwork -mabi=aapcs-linux > -mword-relocations -march=armv7-a -include > /home/abuild/rpmbuild/BUILD/u-boot-2014.01/include/u-boot/u-boot.lds.h > -DCPUDIR=arch/arm/cpu/armv7 -ansi -D__ASSEMBLY__ -P - > </home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/cpu/u-boot.lds > >u-boot.lds > [ 178s] cd /home/abuild/rpmbuild/BUILD/u-boot-2014.01 && ld.bfd -pie > -T u-boot.lds --gc-sections -Bstatic -Ttext 0x0010E000 ^^^^^^^^^^^^ > arch/arm/cpu/armv7/start.o --start-group arch/arm/cpu/armv7/built-in.o > arch/arm/cpu/armv7/tegra20/built-in.o arch/arm/cpu/built-in.o > arch/arm/lib/built-in.o board/toradex/colibri_t20_iris/built-in.o > common/built-in.o disk/built-in.o drivers/built-in.o > drivers/dma/built-in.o drivers/gpio/built-in.o drivers/i2c/built-in.o > drivers/input/built-in.o drivers/mmc/built-in.o drivers/mtd/built-in.o > drivers/mtd/nand/built-in.o drivers/mtd/onenand/built-in.o > drivers/mtd/spi/built-in.o drivers/net/built-in.o > drivers/net/phy/built-in.o drivers/pci/built-in.o > drivers/power/battery/built-in.o drivers/power/built-in.o > drivers/power/fuel_gauge/built-in.o drivers/power/mfd/built-in.o > drivers/power/pmic/built-in.o drivers/serial/built-in.o > drivers/spi/built-in.o drivers/usb/eth/built-in.o > drivers/usb/gadget/built-in.o drivers/usb/host/built-in.o > drivers/usb/musb-new/built-in.o drivers/usb/musb/built-in.o > drivers/usb/phy/built-in.o drivers/usb/ulpi/built-in.o fs/built-in.o > lib/built-in.o lib/libfdt/built-in.o net/built-in.o test/built-in.o > --end-group > /home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/lib/eabi_compat.o > -L /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8 -lgcc -Map u-boot.map -o > u-boot > [ 178s] ld.bfd: u-boot: could not find output section .gnu.hash > [ 178s] ld.bfd: final link failed: Nonrepresentable section on output > [ 178s] Makefile:556: recipe for target 'u-boot' failed > [ 178s] make: *** [u-boot] Error 1 Looks more like an issue with the linker script used by u-boot. .gnu.hash is simply what recent linkers produce by default - you could try if using -Wl,--hash-style=sysv works around the issue, but it would still point to a linker script bug IMHO (or a bug in binutils, not gcc). Richard. > > https://build.opensuse.org/package/live_build_log/home:a_faerber:branches:Base:System/u-boot-colibrit20iris/openSUSE_Factory_ARM/armv7l > > Regards, > Andreas > >
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/03/2014 03:41 AM, Richard Biener wrote: > On Sun, 2 Mar 2014, Andreas Färber wrote: > >> Am 02.03.2014 21:57, schrieb Andreas Färber: >>> Hi Albert, >>> >>> Am 02.03.2014 20:15, schrieb Albert ARIBAUD: >>>> Hi Andreas, >>>> >>>> On Sun, 02 Mar 2014 18:57:14 +0100, Andreas Färber <afaerber@suse.de> >>>> wrote: >>>> >>>>> Hi Albert, >>>>> >>>>> Am 22.02.2014 14:27, schrieb Albert ARIBAUD: >>>>>> On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD >>>>>> <albert.u.boot@aribaud.net> wrote: >>>>>> >>>>>>> Can you point me to the toolchain you are using, and if you are not >>>>>>> building mainline code, can you make this code available to me somehow? >>> [...] >>>>> Our latest GCC 4.8.2 can be found here: >>>>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 >>>>> >>>>> Matching binutils 2.24 are here: >>>>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils >>>>> >>>>> Our latest U-Boot tarball and patches: >>>>> https://build.opensuse.org/package/show/Base:System/u-boot >>>>> Build logs can be found in the u-boot-* packages in the same project, >>>>> with underscores stripped, e.g.: >>>>> https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm >>>> >>>> Thanks for your reply. Apparently, the problem does not appear for the >>>> boards in mainline U-Boot which I listed above with the source code >>>> from our v2014.01 tag and using gcc 4.8.1 from Linaro. I can install >>>> 4.8.2, but meanwhile, can you try to build v2014.01 for these boards >>>> with your setup? >>>> >>>> am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle >>>> omap4_panda paz00 rpi_b >>> >>> I have commented out the patch in: >>> https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System >>> >>> While there are apparently frequent rebuilds scheduled ATM, it seemed >>> like the colibri_t20_iris config intermittently built OK without it. >>> Maybe some gcc 4.8 stable branch update [1] resolved it ... will keep an >>> eye on the build status to confirm. If everything builds, I'm happy. >> >> Nah, still fails without the patch: >> >> [ 178s] gcc -E -g -Os -ffunction-sections -fdata-sections >> -fno-common -ffixed-r9 -msoft-float -D__KERNEL__ >> -DCONFIG_SYS_TEXT_BASE=0x0010E000 >> -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/include >> -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/include >> -fno-builtin -ffreestanding -nostdinc -isystem >> /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/include -pipe -DCONFIG_ARM >> -D__ARM__ -marm -mno-thumb-interwork -mabi=aapcs-linux >> -mword-relocations -march=armv7-a -include >> /home/abuild/rpmbuild/BUILD/u-boot-2014.01/include/u-boot/u-boot.lds.h >> -DCPUDIR=arch/arm/cpu/armv7 -ansi -D__ASSEMBLY__ -P - >> </home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/cpu/u-boot.lds >>> u-boot.lds >> [ 178s] cd /home/abuild/rpmbuild/BUILD/u-boot-2014.01 && ld.bfd -pie >> -T u-boot.lds --gc-sections -Bstatic -Ttext 0x0010E000 > ^^^^^^^^^^^^ > >> arch/arm/cpu/armv7/start.o --start-group arch/arm/cpu/armv7/built-in.o >> arch/arm/cpu/armv7/tegra20/built-in.o arch/arm/cpu/built-in.o >> arch/arm/lib/built-in.o board/toradex/colibri_t20_iris/built-in.o >> common/built-in.o disk/built-in.o drivers/built-in.o >> drivers/dma/built-in.o drivers/gpio/built-in.o drivers/i2c/built-in.o >> drivers/input/built-in.o drivers/mmc/built-in.o drivers/mtd/built-in.o >> drivers/mtd/nand/built-in.o drivers/mtd/onenand/built-in.o >> drivers/mtd/spi/built-in.o drivers/net/built-in.o >> drivers/net/phy/built-in.o drivers/pci/built-in.o >> drivers/power/battery/built-in.o drivers/power/built-in.o >> drivers/power/fuel_gauge/built-in.o drivers/power/mfd/built-in.o >> drivers/power/pmic/built-in.o drivers/serial/built-in.o >> drivers/spi/built-in.o drivers/usb/eth/built-in.o >> drivers/usb/gadget/built-in.o drivers/usb/host/built-in.o >> drivers/usb/musb-new/built-in.o drivers/usb/musb/built-in.o >> drivers/usb/phy/built-in.o drivers/usb/ulpi/built-in.o fs/built-in.o >> lib/built-in.o lib/libfdt/built-in.o net/built-in.o test/built-in.o >> --end-group >> /home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/lib/eabi_compat.o >> -L /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8 -lgcc -Map u-boot.map -o >> u-boot >> [ 178s] ld.bfd: u-boot: could not find output section .gnu.hash >> [ 178s] ld.bfd: final link failed: Nonrepresentable section on output >> [ 178s] Makefile:556: recipe for target 'u-boot' failed >> [ 178s] make: *** [u-boot] Error 1 > > Looks more like an issue with the linker script used by u-boot. .gnu.hash > is simply what recent linkers produce by default - you could try > if using -Wl,--hash-style=sysv works around the issue, but it would still > point to a linker script bug IMHO (or a bug in binutils, not gcc). If that was true it would be consistently happening, but it's not. I hope it's possible to save the output when the build fails. - -- Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTFIKtAAoJENk4IS6UOR1WFX8P+gLx3xjt0ZQny9LtSO0NtPqE blyRLfwofg3ZRQz/aPk3Cpser+09jOJmAjqMCdweSSV+xR241jDWMI9V35zWr8kC dmkMO6hKPlZVsA/odwD/cNco/1BOvZnr8+n1QA3vjcKSVaIU3y8+4v/wD4cuXbEl MHFpN4fMEgatTVR85pxTdgXQAa9FUvxFp9czRkDjKOnY2gEFO7akxGbyY6sATtqU 5bzQbXGFdq+6viQazF0SgyXs0YDnq8oBRe7udK3BWI2m7lG0jNG+NR9cLO9uXbzm fAWo7bZ1HHZC4HIPjNglpixFz/mI1pw6/uLyZMmfOTOFfKIsHZcXhKBnetHpQr1A Lbvf8H8JTn1dkX3i4qx2nJWk4uDatJnQ6sr8TUaYc7xbt/yBkLdPqyjZwG6B1iNJ GQHpKV2TUlNc59vWBEPJnH62mGd59UFs5vvckGP0KC/XQjT8EzIexpim7fLTAlrU W94qwT8BXeq1dgS5o/9Kr1loaM/ek2sH9ihdATRHnrZ0wDzkta0Q72wGPCtbL+/8 nY75K4H3GN1sfZVW7ODjwrSIGUhPYX+pKzlK4t+rOSZrg2B46zARzVOXYaERAhIo MTfg+qFvaMo5Le5bhun2FctYszVszO17fZ003QTY8y3w9RIoPzylentwYYAg7s0n oZlQA7KMTcg1wmVqz697 =0p/l -----END PGP SIGNATURE-----
On Mon, 3 Mar 2014 08:00:52 +0100, Albert ARIBAUD <albert.u.boot@aribaud.net> wrote: > Hi Andreas, > > (seems an answer from me yesterday didn't make it out of the NSA > interceptors...) > > On Sun, 02 Mar 2014 23:00:19 +0100, Andreas Färber > <afaerber@suse.de> wrote: > > > Am 02.03.2014 21:57, schrieb Andreas Färber: > > > Hi Albert, > > > > > > Am 02.03.2014 20:15, schrieb Albert ARIBAUD: > > >> Hi Andreas, > > >> > > >> On Sun, 02 Mar 2014 18:57:14 +0100, Andreas Färber <afaerber@suse.de> > > >> wrote: > > >> > > >>> Hi Albert, > > >>> > > >>> Am 22.02.2014 14:27, schrieb Albert ARIBAUD: > > >>>> On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD > > >>>> <albert.u.boot@aribaud.net> wrote: > > >>>> > > >>>>> Can you point me to the toolchain you are using, and if you are not > > >>>>> building mainline code, can you make this code available to me somehow? > > > [...] > > >>> Our latest GCC 4.8.2 can be found here: > > >>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 > > >>> > > >>> Matching binutils 2.24 are here: > > >>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils > > >>> > > >>> Our latest U-Boot tarball and patches: > > >>> https://build.opensuse.org/package/show/Base:System/u-boot > > >>> Build logs can be found in the u-boot-* packages in the same project, > > >>> with underscores stripped, e.g.: > > >>> https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm > > >> > > >> Thanks for your reply. Apparently, the problem does not appear for the > > >> boards in mainline U-Boot which I listed above with the source code > > >> from our v2014.01 tag and using gcc 4.8.1 from Linaro. I can install > > >> 4.8.2, but meanwhile, can you try to build v2014.01 for these boards > > >> with your setup? > > >> > > >> am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle > > >> omap4_panda paz00 rpi_b > > > > > > I have commented out the patch in: > > > https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System > > > > > > While there are apparently frequent rebuilds scheduled ATM, it seemed > > > like the colibri_t20_iris config intermittently built OK without it. > > > Maybe some gcc 4.8 stable branch update [1] resolved it ... will keep an > > > eye on the build status to confirm. If everything builds, I'm happy. > > > > Nah, still fails without the patch: > > > > [ 178s] gcc -E -g -Os -ffunction-sections -fdata-sections > > -fno-common -ffixed-r9 -msoft-float -D__KERNEL__ > > -DCONFIG_SYS_TEXT_BASE=0x0010E000 > > -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/include > > -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/include > > -fno-builtin -ffreestanding -nostdinc -isystem > > /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/include -pipe -DCONFIG_ARM > > -D__ARM__ -marm -mno-thumb-interwork -mabi=aapcs-linux > > -mword-relocations -march=armv7-a -include > > /home/abuild/rpmbuild/BUILD/u-boot-2014.01/include/u-boot/u-boot.lds.h > > -DCPUDIR=arch/arm/cpu/armv7 -ansi -D__ASSEMBLY__ -P - > > </home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/cpu/u-boot.lds > > >u-boot.lds > > [ 178s] cd /home/abuild/rpmbuild/BUILD/u-boot-2014.01 && ld.bfd -pie > > -T u-boot.lds --gc-sections -Bstatic -Ttext 0x0010E000 > > arch/arm/cpu/armv7/start.o --start-group arch/arm/cpu/armv7/built-in.o > > arch/arm/cpu/armv7/tegra20/built-in.o arch/arm/cpu/built-in.o > > arch/arm/lib/built-in.o board/toradex/colibri_t20_iris/built-in.o > > common/built-in.o disk/built-in.o drivers/built-in.o > > drivers/dma/built-in.o drivers/gpio/built-in.o drivers/i2c/built-in.o > > drivers/input/built-in.o drivers/mmc/built-in.o drivers/mtd/built-in.o > > drivers/mtd/nand/built-in.o drivers/mtd/onenand/built-in.o > > drivers/mtd/spi/built-in.o drivers/net/built-in.o > > drivers/net/phy/built-in.o drivers/pci/built-in.o > > drivers/power/battery/built-in.o drivers/power/built-in.o > > drivers/power/fuel_gauge/built-in.o drivers/power/mfd/built-in.o > > drivers/power/pmic/built-in.o drivers/serial/built-in.o > > drivers/spi/built-in.o drivers/usb/eth/built-in.o > > drivers/usb/gadget/built-in.o drivers/usb/host/built-in.o > > drivers/usb/musb-new/built-in.o drivers/usb/musb/built-in.o > > drivers/usb/phy/built-in.o drivers/usb/ulpi/built-in.o fs/built-in.o > > lib/built-in.o lib/libfdt/built-in.o net/built-in.o test/built-in.o > > --end-group > > /home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/lib/eabi_compat.o > > -L /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8 -lgcc -Map u-boot.map -o > > u-boot > > [ 178s] ld.bfd: u-boot: could not find output section .gnu.hash > > [ 178s] ld.bfd: final link failed: Nonrepresentable section on output > > [ 178s] Makefile:556: recipe for target 'u-boot' failed > > [ 178s] make: *** [u-boot] Error 1 > > You are trying this with your codebase, right? If so, can you try and > build vanilla v2014.01 with the exact same build environment? If it > builds fine, then can you tell me which changes your patch(es) made to > linker scripts in your tree wrt 2014.01? Ping. > > https://build.opensuse.org/package/live_build_log/home:a_faerber:branches:Base:System/u-boot-colibrit20iris/openSUSE_Factory_ARM/armv7l > > > > Regards, > > Andreas Amicalement,
Am 09.03.2014 21:05, schrieb Albert ARIBAUD: > On Mon, 3 Mar 2014 08:00:52 +0100, Albert ARIBAUD > <albert.u.boot@aribaud.net> wrote: > >> Hi Andreas, >> >> (seems an answer from me yesterday didn't make it out of the NSA >> interceptors...) >> >> On Sun, 02 Mar 2014 23:00:19 +0100, Andreas Färber >> <afaerber@suse.de> wrote: >> >>> Am 02.03.2014 21:57, schrieb Andreas Färber: >>>> Hi Albert, >>>> >>>> Am 02.03.2014 20:15, schrieb Albert ARIBAUD: >>>>> Hi Andreas, >>>>> >>>>> On Sun, 02 Mar 2014 18:57:14 +0100, Andreas Färber <afaerber@suse.de> >>>>> wrote: >>>>> >>>>>> Hi Albert, >>>>>> >>>>>> Am 22.02.2014 14:27, schrieb Albert ARIBAUD: >>>>>>> On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD >>>>>>> <albert.u.boot@aribaud.net> wrote: >>>>>>> >>>>>>>> Can you point me to the toolchain you are using, and if you are not >>>>>>>> building mainline code, can you make this code available to me somehow? >>>> [...] >>>>>> Our latest GCC 4.8.2 can be found here: >>>>>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 >>>>>> >>>>>> Matching binutils 2.24 are here: >>>>>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils >>>>>> >>>>>> Our latest U-Boot tarball and patches: >>>>>> https://build.opensuse.org/package/show/Base:System/u-boot >>>>>> Build logs can be found in the u-boot-* packages in the same project, >>>>>> with underscores stripped, e.g.: >>>>>> https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm >>>>> >>>>> Thanks for your reply. Apparently, the problem does not appear for the >>>>> boards in mainline U-Boot which I listed above with the source code >>>>> from our v2014.01 tag and using gcc 4.8.1 from Linaro. I can install >>>>> 4.8.2, but meanwhile, can you try to build v2014.01 for these boards >>>>> with your setup? >>>>> >>>>> am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle >>>>> omap4_panda paz00 rpi_b >>>> >>>> I have commented out the patch in: >>>> https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System >>>> >>>> While there are apparently frequent rebuilds scheduled ATM, it seemed >>>> like the colibri_t20_iris config intermittently built OK without it. >>>> Maybe some gcc 4.8 stable branch update [1] resolved it ... will keep an >>>> eye on the build status to confirm. If everything builds, I'm happy. >>> >>> Nah, still fails without the patch: >>> >>> [ 178s] gcc -E -g -Os -ffunction-sections -fdata-sections >>> -fno-common -ffixed-r9 -msoft-float -D__KERNEL__ >>> -DCONFIG_SYS_TEXT_BASE=0x0010E000 >>> -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/include >>> -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/include >>> -fno-builtin -ffreestanding -nostdinc -isystem >>> /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/include -pipe -DCONFIG_ARM >>> -D__ARM__ -marm -mno-thumb-interwork -mabi=aapcs-linux >>> -mword-relocations -march=armv7-a -include >>> /home/abuild/rpmbuild/BUILD/u-boot-2014.01/include/u-boot/u-boot.lds.h >>> -DCPUDIR=arch/arm/cpu/armv7 -ansi -D__ASSEMBLY__ -P - >>> </home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/cpu/u-boot.lds >>>> u-boot.lds >>> [ 178s] cd /home/abuild/rpmbuild/BUILD/u-boot-2014.01 && ld.bfd -pie >>> -T u-boot.lds --gc-sections -Bstatic -Ttext 0x0010E000 >>> arch/arm/cpu/armv7/start.o --start-group arch/arm/cpu/armv7/built-in.o >>> arch/arm/cpu/armv7/tegra20/built-in.o arch/arm/cpu/built-in.o >>> arch/arm/lib/built-in.o board/toradex/colibri_t20_iris/built-in.o >>> common/built-in.o disk/built-in.o drivers/built-in.o >>> drivers/dma/built-in.o drivers/gpio/built-in.o drivers/i2c/built-in.o >>> drivers/input/built-in.o drivers/mmc/built-in.o drivers/mtd/built-in.o >>> drivers/mtd/nand/built-in.o drivers/mtd/onenand/built-in.o >>> drivers/mtd/spi/built-in.o drivers/net/built-in.o >>> drivers/net/phy/built-in.o drivers/pci/built-in.o >>> drivers/power/battery/built-in.o drivers/power/built-in.o >>> drivers/power/fuel_gauge/built-in.o drivers/power/mfd/built-in.o >>> drivers/power/pmic/built-in.o drivers/serial/built-in.o >>> drivers/spi/built-in.o drivers/usb/eth/built-in.o >>> drivers/usb/gadget/built-in.o drivers/usb/host/built-in.o >>> drivers/usb/musb-new/built-in.o drivers/usb/musb/built-in.o >>> drivers/usb/phy/built-in.o drivers/usb/ulpi/built-in.o fs/built-in.o >>> lib/built-in.o lib/libfdt/built-in.o net/built-in.o test/built-in.o >>> --end-group >>> /home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/lib/eabi_compat.o >>> -L /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8 -lgcc -Map u-boot.map -o >>> u-boot >>> [ 178s] ld.bfd: u-boot: could not find output section .gnu.hash >>> [ 178s] ld.bfd: final link failed: Nonrepresentable section on output >>> [ 178s] Makefile:556: recipe for target 'u-boot' failed >>> [ 178s] make: *** [u-boot] Error 1 >> >> You are trying this with your codebase, right? If so, can you try and >> build vanilla v2014.01 with the exact same build environment? Commented out all our patches at: https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System Failure of any sunxi-added targets is to be expected, of course. > If it >> builds fine, then can you tell me which changes your patch(es) made to >> linker scripts in your tree wrt 2014.01? > > Ping. I had previously pointed to our patches and explained that they do not touch on any existing linker scripts. They merely change CONFIG_ options, tweak environment settings and add the sunxi targets. As for the other open question, OBS does not package build intermediaries of failed builds, so I'll need to reproduce it locally. ATM I'm lacking time because QEMU is about to enter Hard Freeze for 2.0. Amicalement, Andreas >>> https://build.opensuse.org/package/live_build_log/home:a_faerber:branches:Base:System/u-boot-colibrit20iris/openSUSE_Factory_ARM/armv7l >>> >>> Regards, >>> Andreas > > Amicalement,
Hi Andreas, On Sun, 09 Mar 2014 21:22:34 +0100, Andreas Färber <afaerber@suse.de> wrote: > Am 09.03.2014 21:05, schrieb Albert ARIBAUD: > > On Mon, 3 Mar 2014 08:00:52 +0100, Albert ARIBAUD > > <albert.u.boot@aribaud.net> wrote: > > > >> Hi Andreas, > >> > >> (seems an answer from me yesterday didn't make it out of the NSA > >> interceptors...) > >> > >> On Sun, 02 Mar 2014 23:00:19 +0100, Andreas Färber > >> <afaerber@suse.de> wrote: > >> > >>> Am 02.03.2014 21:57, schrieb Andreas Färber: > >>>> Hi Albert, > >>>> > >>>> Am 02.03.2014 20:15, schrieb Albert ARIBAUD: > >>>>> Hi Andreas, > >>>>> > >>>>> On Sun, 02 Mar 2014 18:57:14 +0100, Andreas Färber <afaerber@suse.de> > >>>>> wrote: > >>>>> > >>>>>> Hi Albert, > >>>>>> > >>>>>> Am 22.02.2014 14:27, schrieb Albert ARIBAUD: > >>>>>>> On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD > >>>>>>> <albert.u.boot@aribaud.net> wrote: > >>>>>>> > >>>>>>>> Can you point me to the toolchain you are using, and if you are not > >>>>>>>> building mainline code, can you make this code available to me somehow? > >>>> [...] > >>>>>> Our latest GCC 4.8.2 can be found here: > >>>>>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 > >>>>>> > >>>>>> Matching binutils 2.24 are here: > >>>>>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils > >>>>>> > >>>>>> Our latest U-Boot tarball and patches: > >>>>>> https://build.opensuse.org/package/show/Base:System/u-boot > >>>>>> Build logs can be found in the u-boot-* packages in the same project, > >>>>>> with underscores stripped, e.g.: > >>>>>> https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm > >>>>> > >>>>> Thanks for your reply. Apparently, the problem does not appear for the > >>>>> boards in mainline U-Boot which I listed above with the source code > >>>>> from our v2014.01 tag and using gcc 4.8.1 from Linaro. I can install > >>>>> 4.8.2, but meanwhile, can you try to build v2014.01 for these boards > >>>>> with your setup? > >>>>> > >>>>> am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle > >>>>> omap4_panda paz00 rpi_b > >>>> > >>>> I have commented out the patch in: > >>>> https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System > >>>> > >>>> While there are apparently frequent rebuilds scheduled ATM, it seemed > >>>> like the colibri_t20_iris config intermittently built OK without it. > >>>> Maybe some gcc 4.8 stable branch update [1] resolved it ... will keep an > >>>> eye on the build status to confirm. If everything builds, I'm happy. > >>> > >>> Nah, still fails without the patch: > >>> > >>> [ 178s] gcc -E -g -Os -ffunction-sections -fdata-sections > >>> -fno-common -ffixed-r9 -msoft-float -D__KERNEL__ > >>> -DCONFIG_SYS_TEXT_BASE=0x0010E000 > >>> -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/include > >>> -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/include > >>> -fno-builtin -ffreestanding -nostdinc -isystem > >>> /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/include -pipe -DCONFIG_ARM > >>> -D__ARM__ -marm -mno-thumb-interwork -mabi=aapcs-linux > >>> -mword-relocations -march=armv7-a -include > >>> /home/abuild/rpmbuild/BUILD/u-boot-2014.01/include/u-boot/u-boot.lds.h > >>> -DCPUDIR=arch/arm/cpu/armv7 -ansi -D__ASSEMBLY__ -P - > >>> </home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/cpu/u-boot.lds > >>>> u-boot.lds > >>> [ 178s] cd /home/abuild/rpmbuild/BUILD/u-boot-2014.01 && ld.bfd -pie > >>> -T u-boot.lds --gc-sections -Bstatic -Ttext 0x0010E000 > >>> arch/arm/cpu/armv7/start.o --start-group arch/arm/cpu/armv7/built-in.o > >>> arch/arm/cpu/armv7/tegra20/built-in.o arch/arm/cpu/built-in.o > >>> arch/arm/lib/built-in.o board/toradex/colibri_t20_iris/built-in.o > >>> common/built-in.o disk/built-in.o drivers/built-in.o > >>> drivers/dma/built-in.o drivers/gpio/built-in.o drivers/i2c/built-in.o > >>> drivers/input/built-in.o drivers/mmc/built-in.o drivers/mtd/built-in.o > >>> drivers/mtd/nand/built-in.o drivers/mtd/onenand/built-in.o > >>> drivers/mtd/spi/built-in.o drivers/net/built-in.o > >>> drivers/net/phy/built-in.o drivers/pci/built-in.o > >>> drivers/power/battery/built-in.o drivers/power/built-in.o > >>> drivers/power/fuel_gauge/built-in.o drivers/power/mfd/built-in.o > >>> drivers/power/pmic/built-in.o drivers/serial/built-in.o > >>> drivers/spi/built-in.o drivers/usb/eth/built-in.o > >>> drivers/usb/gadget/built-in.o drivers/usb/host/built-in.o > >>> drivers/usb/musb-new/built-in.o drivers/usb/musb/built-in.o > >>> drivers/usb/phy/built-in.o drivers/usb/ulpi/built-in.o fs/built-in.o > >>> lib/built-in.o lib/libfdt/built-in.o net/built-in.o test/built-in.o > >>> --end-group > >>> /home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/lib/eabi_compat.o > >>> -L /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8 -lgcc -Map u-boot.map -o > >>> u-boot > >>> [ 178s] ld.bfd: u-boot: could not find output section .gnu.hash > >>> [ 178s] ld.bfd: final link failed: Nonrepresentable section on output > >>> [ 178s] Makefile:556: recipe for target 'u-boot' failed > >>> [ 178s] make: *** [u-boot] Error 1 > >> > >> You are trying this with your codebase, right? If so, can you try and > >> build vanilla v2014.01 with the exact same build environment? > > Commented out all our patches at: > https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System > > Failure of any sunxi-added targets is to be expected, of course. Not sure I'm getting this: if you build vanilla v2014.01, there shouldn't be any sunxi target built at all, should it? > > If it > >> builds fine, then can you tell me which changes your patch(es) made to > >> linker scripts in your tree wrt 2014.01? > > > > Ping. > > I had previously pointed to our patches and explained that they do not > touch on any existing linker scripts. They merely change CONFIG_ > options, tweak environment settings and add the sunxi targets. I am not asking about changing linker scripts; I am asking about trying your build environment on the pristine v2014.01 codebase, e.g. build all mainline ARM targets with your toolchains. > As for the other open question, OBS does not package build > intermediaries of failed builds, so I'll need to reproduce it locally. > ATM I'm lacking time because QEMU is about to enter Hard Freeze for 2.0. Could you just run this in a git clone of U-Boot with v2014.01 checked out? ARCH=arm CROSS_COMPILE=your-toolchain-prefix- ./MAKEALL -a arm It would build all targets unattended using your toolchain (assuming it is in your PATH of course). > Amicalement, > Andreas Amicalement,
Hi, Am 09.03.2014 21:34, schrieb Albert ARIBAUD: > On Sun, 09 Mar 2014 21:22:34 +0100, Andreas Färber <afaerber@suse.de> > wrote: >> Am 09.03.2014 21:05, schrieb Albert ARIBAUD: >>> On Mon, 3 Mar 2014 08:00:52 +0100, Albert ARIBAUD >>> <albert.u.boot@aribaud.net> wrote: >>>> On Sun, 02 Mar 2014 23:00:19 +0100, Andreas Färber >>>> <afaerber@suse.de> wrote: >>>>> Am 02.03.2014 21:57, schrieb Andreas Färber: >>>>>> Am 02.03.2014 20:15, schrieb Albert ARIBAUD: >>>>>>> On Sun, 02 Mar 2014 18:57:14 +0100, Andreas Färber <afaerber@suse.de> >>>>>>> wrote: >>>>>>>> Am 22.02.2014 14:27, schrieb Albert ARIBAUD: >>>>>>>>> On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD >>>>>>>>> <albert.u.boot@aribaud.net> wrote: >>>>>>>>> >>>>>>>>>> Can you point me to the toolchain you are using, and if you are not >>>>>>>>>> building mainline code, can you make this code available to me somehow? >>>>>> [...] >>>>>>>> Our latest GCC 4.8.2 can be found here: >>>>>>>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 >>>>>>>> >>>>>>>> Matching binutils 2.24 are here: >>>>>>>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils >>>>>>>> >>>>>>>> Our latest U-Boot tarball and patches: >>>>>>>> https://build.opensuse.org/package/show/Base:System/u-boot >>>>>>>> Build logs can be found in the u-boot-* packages in the same project, >>>>>>>> with underscores stripped, e.g.: >>>>>>>> https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm >>>>>>> >>>>>>> Thanks for your reply. Apparently, the problem does not appear for the >>>>>>> boards in mainline U-Boot which I listed above with the source code >>>>>>> from our v2014.01 tag and using gcc 4.8.1 from Linaro. I can install >>>>>>> 4.8.2, but meanwhile, can you try to build v2014.01 for these boards >>>>>>> with your setup? >>>>>>> >>>>>>> am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle >>>>>>> omap4_panda paz00 rpi_b >>>>>> >>>>>> I have commented out the patch in: >>>>>> https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System >>>>>> >>>>>> While there are apparently frequent rebuilds scheduled ATM, it seemed >>>>>> like the colibri_t20_iris config intermittently built OK without it. >>>>>> Maybe some gcc 4.8 stable branch update [1] resolved it ... will keep an >>>>>> eye on the build status to confirm. If everything builds, I'm happy. >>>>> >>>>> Nah, still fails without the patch: >>>>> >>>>> [ 178s] gcc -E -g -Os -ffunction-sections -fdata-sections >>>>> -fno-common -ffixed-r9 -msoft-float -D__KERNEL__ >>>>> -DCONFIG_SYS_TEXT_BASE=0x0010E000 >>>>> -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/include >>>>> -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/include >>>>> -fno-builtin -ffreestanding -nostdinc -isystem >>>>> /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/include -pipe -DCONFIG_ARM >>>>> -D__ARM__ -marm -mno-thumb-interwork -mabi=aapcs-linux >>>>> -mword-relocations -march=armv7-a -include >>>>> /home/abuild/rpmbuild/BUILD/u-boot-2014.01/include/u-boot/u-boot.lds.h >>>>> -DCPUDIR=arch/arm/cpu/armv7 -ansi -D__ASSEMBLY__ -P - >>>>> </home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/cpu/u-boot.lds >>>>>> u-boot.lds >>>>> [ 178s] cd /home/abuild/rpmbuild/BUILD/u-boot-2014.01 && ld.bfd -pie >>>>> -T u-boot.lds --gc-sections -Bstatic -Ttext 0x0010E000 >>>>> arch/arm/cpu/armv7/start.o --start-group arch/arm/cpu/armv7/built-in.o >>>>> arch/arm/cpu/armv7/tegra20/built-in.o arch/arm/cpu/built-in.o >>>>> arch/arm/lib/built-in.o board/toradex/colibri_t20_iris/built-in.o >>>>> common/built-in.o disk/built-in.o drivers/built-in.o >>>>> drivers/dma/built-in.o drivers/gpio/built-in.o drivers/i2c/built-in.o >>>>> drivers/input/built-in.o drivers/mmc/built-in.o drivers/mtd/built-in.o >>>>> drivers/mtd/nand/built-in.o drivers/mtd/onenand/built-in.o >>>>> drivers/mtd/spi/built-in.o drivers/net/built-in.o >>>>> drivers/net/phy/built-in.o drivers/pci/built-in.o >>>>> drivers/power/battery/built-in.o drivers/power/built-in.o >>>>> drivers/power/fuel_gauge/built-in.o drivers/power/mfd/built-in.o >>>>> drivers/power/pmic/built-in.o drivers/serial/built-in.o >>>>> drivers/spi/built-in.o drivers/usb/eth/built-in.o >>>>> drivers/usb/gadget/built-in.o drivers/usb/host/built-in.o >>>>> drivers/usb/musb-new/built-in.o drivers/usb/musb/built-in.o >>>>> drivers/usb/phy/built-in.o drivers/usb/ulpi/built-in.o fs/built-in.o >>>>> lib/built-in.o lib/libfdt/built-in.o net/built-in.o test/built-in.o >>>>> --end-group >>>>> /home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/lib/eabi_compat.o >>>>> -L /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8 -lgcc -Map u-boot.map -o >>>>> u-boot >>>>> [ 178s] ld.bfd: u-boot: could not find output section .gnu.hash >>>>> [ 178s] ld.bfd: final link failed: Nonrepresentable section on output >>>>> [ 178s] Makefile:556: recipe for target 'u-boot' failed >>>>> [ 178s] make: *** [u-boot] Error 1 >>>> >>>> You are trying this with your codebase, right? If so, can you try and >>>> build vanilla v2014.01 with the exact same build environment? >> >> Commented out all our patches at: >> https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System >> >> Failure of any sunxi-added targets is to be expected, of course. > > Not sure I'm getting this: if you build vanilla v2014.01, there > shouldn't be any sunxi target built at all, should it? I removed the patches from the spec file in our build service. That doesn't drop the packages for those no longer patched-in targets, so failures of those targets are to be expected. I am not building locally. Here's a vanilla "highbank" target failing: https://build.opensuse.org/package/live_build_log/home:a_faerber:branches:Base:System/u-boot-highbank/openSUSE_Factory_ARM/armv7l >>> If it >>>> builds fine, then can you tell me which changes your patch(es) made to >>>> linker scripts in your tree wrt 2014.01? >>> >>> Ping. >> >> I had previously pointed to our patches and explained that they do not >> touch on any existing linker scripts. They merely change CONFIG_ >> options, tweak environment settings and add the sunxi targets. > > I am not asking about changing linker scripts; I am asking about > trying your build environment on the pristine v2014.01 codebase, e.g. > build all mainline ARM targets with your toolchains. You did ask above "which changes" our patches "made to linker scripts". And the answer is: None, apart from the already commented-out gnuhash.patch, which corresponds to this very patch under discussion. >> As for the other open question, OBS does not package build >> intermediaries of failed builds, so I'll need to reproduce it locally. >> ATM I'm lacking time because QEMU is about to enter Hard Freeze for 2.0. > > Could you just run this in a git clone of U-Boot with v2014.01 checked > out? > > ARCH=arm CROSS_COMPILE=your-toolchain-prefix- ./MAKEALL -a arm > > It would build all targets unattended using your toolchain (assuming it > is in your PATH of course). My local ARM machines are all 13.1, not Factory, but I can try running that command there later. Amicalement, Andreas
Hi Andreas, On Sun, 09 Mar 2014 21:52:44 +0100, Andreas Färber <afaerber@suse.de> wrote: > Hi, > > Am 09.03.2014 21:34, schrieb Albert ARIBAUD: > > On Sun, 09 Mar 2014 21:22:34 +0100, Andreas Färber <afaerber@suse.de> > > wrote: > >> Am 09.03.2014 21:05, schrieb Albert ARIBAUD: > >>> On Mon, 3 Mar 2014 08:00:52 +0100, Albert ARIBAUD > >>> <albert.u.boot@aribaud.net> wrote: > >>>> On Sun, 02 Mar 2014 23:00:19 +0100, Andreas Färber > >>>> <afaerber@suse.de> wrote: > >>>>> Am 02.03.2014 21:57, schrieb Andreas Färber: > >>>>>> Am 02.03.2014 20:15, schrieb Albert ARIBAUD: > >>>>>>> On Sun, 02 Mar 2014 18:57:14 +0100, Andreas Färber <afaerber@suse.de> > >>>>>>> wrote: > >>>>>>>> Am 22.02.2014 14:27, schrieb Albert ARIBAUD: > >>>>>>>>> On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD > >>>>>>>>> <albert.u.boot@aribaud.net> wrote: > >>>>>>>>> > >>>>>>>>>> Can you point me to the toolchain you are using, and if you are not > >>>>>>>>>> building mainline code, can you make this code available to me somehow? > >>>>>> [...] > >>>>>>>> Our latest GCC 4.8.2 can be found here: > >>>>>>>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 > >>>>>>>> > >>>>>>>> Matching binutils 2.24 are here: > >>>>>>>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils > >>>>>>>> > >>>>>>>> Our latest U-Boot tarball and patches: > >>>>>>>> https://build.opensuse.org/package/show/Base:System/u-boot > >>>>>>>> Build logs can be found in the u-boot-* packages in the same project, > >>>>>>>> with underscores stripped, e.g.: > >>>>>>>> https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm > >>>>>>> > >>>>>>> Thanks for your reply. Apparently, the problem does not appear for the > >>>>>>> boards in mainline U-Boot which I listed above with the source code > >>>>>>> from our v2014.01 tag and using gcc 4.8.1 from Linaro. I can install > >>>>>>> 4.8.2, but meanwhile, can you try to build v2014.01 for these boards > >>>>>>> with your setup? > >>>>>>> > >>>>>>> am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle > >>>>>>> omap4_panda paz00 rpi_b > >>>>>> > >>>>>> I have commented out the patch in: > >>>>>> https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System > >>>>>> > >>>>>> While there are apparently frequent rebuilds scheduled ATM, it seemed > >>>>>> like the colibri_t20_iris config intermittently built OK without it. > >>>>>> Maybe some gcc 4.8 stable branch update [1] resolved it ... will keep an > >>>>>> eye on the build status to confirm. If everything builds, I'm happy. > >>>>> > >>>>> Nah, still fails without the patch: > >>>>> > >>>>> [ 178s] gcc -E -g -Os -ffunction-sections -fdata-sections > >>>>> -fno-common -ffixed-r9 -msoft-float -D__KERNEL__ > >>>>> -DCONFIG_SYS_TEXT_BASE=0x0010E000 > >>>>> -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/include > >>>>> -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/include > >>>>> -fno-builtin -ffreestanding -nostdinc -isystem > >>>>> /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/include -pipe -DCONFIG_ARM > >>>>> -D__ARM__ -marm -mno-thumb-interwork -mabi=aapcs-linux > >>>>> -mword-relocations -march=armv7-a -include > >>>>> /home/abuild/rpmbuild/BUILD/u-boot-2014.01/include/u-boot/u-boot.lds.h > >>>>> -DCPUDIR=arch/arm/cpu/armv7 -ansi -D__ASSEMBLY__ -P - > >>>>> </home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/cpu/u-boot.lds > >>>>>> u-boot.lds > >>>>> [ 178s] cd /home/abuild/rpmbuild/BUILD/u-boot-2014.01 && ld.bfd -pie > >>>>> -T u-boot.lds --gc-sections -Bstatic -Ttext 0x0010E000 > >>>>> arch/arm/cpu/armv7/start.o --start-group arch/arm/cpu/armv7/built-in.o > >>>>> arch/arm/cpu/armv7/tegra20/built-in.o arch/arm/cpu/built-in.o > >>>>> arch/arm/lib/built-in.o board/toradex/colibri_t20_iris/built-in.o > >>>>> common/built-in.o disk/built-in.o drivers/built-in.o > >>>>> drivers/dma/built-in.o drivers/gpio/built-in.o drivers/i2c/built-in.o > >>>>> drivers/input/built-in.o drivers/mmc/built-in.o drivers/mtd/built-in.o > >>>>> drivers/mtd/nand/built-in.o drivers/mtd/onenand/built-in.o > >>>>> drivers/mtd/spi/built-in.o drivers/net/built-in.o > >>>>> drivers/net/phy/built-in.o drivers/pci/built-in.o > >>>>> drivers/power/battery/built-in.o drivers/power/built-in.o > >>>>> drivers/power/fuel_gauge/built-in.o drivers/power/mfd/built-in.o > >>>>> drivers/power/pmic/built-in.o drivers/serial/built-in.o > >>>>> drivers/spi/built-in.o drivers/usb/eth/built-in.o > >>>>> drivers/usb/gadget/built-in.o drivers/usb/host/built-in.o > >>>>> drivers/usb/musb-new/built-in.o drivers/usb/musb/built-in.o > >>>>> drivers/usb/phy/built-in.o drivers/usb/ulpi/built-in.o fs/built-in.o > >>>>> lib/built-in.o lib/libfdt/built-in.o net/built-in.o test/built-in.o > >>>>> --end-group > >>>>> /home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/lib/eabi_compat.o > >>>>> -L /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8 -lgcc -Map u-boot.map -o > >>>>> u-boot > >>>>> [ 178s] ld.bfd: u-boot: could not find output section .gnu.hash > >>>>> [ 178s] ld.bfd: final link failed: Nonrepresentable section on output > >>>>> [ 178s] Makefile:556: recipe for target 'u-boot' failed > >>>>> [ 178s] make: *** [u-boot] Error 1 > >>>> > >>>> You are trying this with your codebase, right? If so, can you try and > >>>> build vanilla v2014.01 with the exact same build environment? > >> > >> Commented out all our patches at: > >> https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System > >> > >> Failure of any sunxi-added targets is to be expected, of course. > > > > Not sure I'm getting this: if you build vanilla v2014.01, there > > shouldn't be any sunxi target built at all, should it? > > I removed the patches from the spec file in our build service. That > doesn't drop the packages for those no longer patched-in targets, so > failures of those targets are to be expected. I am not building locally. > > Here's a vanilla "highbank" target failing: > https://build.opensuse.org/package/live_build_log/home:a_faerber:branches:Base:System/u-boot-highbank/openSUSE_Factory_ARM/armv7l > > >>> If it > >>>> builds fine, then can you tell me which changes your patch(es) made to > >>>> linker scripts in your tree wrt 2014.01? > >>> > >>> Ping. > >> > >> I had previously pointed to our patches and explained that they do not > >> touch on any existing linker scripts. They merely change CONFIG_ > >> options, tweak environment settings and add the sunxi targets. > > > > I am not asking about changing linker scripts; I am asking about > > trying your build environment on the pristine v2014.01 codebase, e.g. > > build all mainline ARM targets with your toolchains. > > You did ask above "which changes" our patches "made to linker scripts". > And the answer is: None, apart from the already commented-out > gnuhash.patch, which corresponds to this very patch under discussion. Understood -- my question about linker script changes was conditioned to succeeding in building pristine v2014.01, so I had mentally put it aside until v2014.01 build results are known. > >> As for the other open question, OBS does not package build > >> intermediaries of failed builds, so I'll need to reproduce it locally. > >> ATM I'm lacking time because QEMU is about to enter Hard Freeze for 2.0. > > > > Could you just run this in a git clone of U-Boot with v2014.01 checked > > out? > > > > ARCH=arm CROSS_COMPILE=your-toolchain-prefix- ./MAKEALL -a arm > > > > It would build all targets unattended using your toolchain (assuming it > > is in your PATH of course). > > My local ARM machines are all 13.1, not Factory, but I can try running > that command there later. Thanks! > Amicalement, > Andreas Amicalement,
Hi Albert, Andreas, > Hi Andreas, > > On Sun, 09 Mar 2014 21:52:44 +0100, Andreas Färber <afaerber@suse.de> > wrote: > > > Hi, > > > > Am 09.03.2014 21:34, schrieb Albert ARIBAUD: > > > On Sun, 09 Mar 2014 21:22:34 +0100, Andreas Färber > > > <afaerber@suse.de> wrote: > > >> Am 09.03.2014 21:05, schrieb Albert ARIBAUD: > > >>> On Mon, 3 Mar 2014 08:00:52 +0100, Albert ARIBAUD > > >>> <albert.u.boot@aribaud.net> wrote: > > >>>> On Sun, 02 Mar 2014 23:00:19 +0100, Andreas Färber > > >>>> <afaerber@suse.de> wrote: > > >>>>> Am 02.03.2014 21:57, schrieb Andreas Färber: > > >>>>>> Am 02.03.2014 20:15, schrieb Albert ARIBAUD: > > >>>>>>> On Sun, 02 Mar 2014 18:57:14 +0100, Andreas Färber > > >>>>>>> <afaerber@suse.de> wrote: > > >>>>>>>> Am 22.02.2014 14:27, schrieb Albert ARIBAUD: > > >>>>>>>>> On Thu, 13 Feb 2014 12:39:07 +0100, Albert ARIBAUD > > >>>>>>>>> <albert.u.boot@aribaud.net> wrote: > > >>>>>>>>> > > >>>>>>>>>> Can you point me to the toolchain you are using, and if > > >>>>>>>>>> you are not building mainline code, can you make this > > >>>>>>>>>> code available to me somehow? > > >>>>>> [...] > > >>>>>>>> Our latest GCC 4.8.2 can be found here: > > >>>>>>>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gcc48 > > >>>>>>>> > > >>>>>>>> Matching binutils 2.24 are here: > > >>>>>>>> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/binutils > > >>>>>>>> > > >>>>>>>> Our latest U-Boot tarball and patches: > > >>>>>>>> https://build.opensuse.org/package/show/Base:System/u-boot > > >>>>>>>> Build logs can be found in the u-boot-* packages in the > > >>>>>>>> same project, with underscores stripped, e.g.: > > >>>>>>>> https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm > > >>>>>>> > > >>>>>>> Thanks for your reply. Apparently, the problem does not > > >>>>>>> appear for the boards in mainline U-Boot which I listed > > >>>>>>> above with the source code from our v2014.01 tag and using > > >>>>>>> gcc 4.8.1 from Linaro. I can install 4.8.2, but meanwhile, > > >>>>>>> can you try to build v2014.01 for these boards with your > > >>>>>>> setup? > > >>>>>>> > > >>>>>>> am335x_evm colibri_t20_iris highbank mx53loco omap3_beagle > > >>>>>>> omap4_panda paz00 rpi_b > > >>>>>> > > >>>>>> I have commented out the patch in: > > >>>>>> https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System > > >>>>>> > > >>>>>> While there are apparently frequent rebuilds scheduled ATM, > > >>>>>> it seemed like the colibri_t20_iris config intermittently > > >>>>>> built OK without it. Maybe some gcc 4.8 stable branch update > > >>>>>> [1] resolved it ... will keep an eye on the build status to > > >>>>>> confirm. If everything builds, I'm happy. > > >>>>> > > >>>>> Nah, still fails without the patch: > > >>>>> > > >>>>> [ 178s] gcc -E -g -Os -ffunction-sections -fdata-sections > > >>>>> -fno-common -ffixed-r9 -msoft-float -D__KERNEL__ > > >>>>> -DCONFIG_SYS_TEXT_BASE=0x0010E000 > > >>>>> -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/include > > >>>>> -I/home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/include > > >>>>> -fno-builtin -ffreestanding -nostdinc -isystem > > >>>>> /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8/include -pipe > > >>>>> -DCONFIG_ARM -D__ARM__ -marm -mno-thumb-interwork > > >>>>> -mabi=aapcs-linux -mword-relocations -march=armv7-a -include > > >>>>> /home/abuild/rpmbuild/BUILD/u-boot-2014.01/include/u-boot/u-boot.lds.h > > >>>>> -DCPUDIR=arch/arm/cpu/armv7 -ansi -D__ASSEMBLY__ -P - > > >>>>> </home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/cpu/u-boot.lds > > >>>>>> u-boot.lds > > >>>>> [ 178s] cd /home/abuild/rpmbuild/BUILD/u-boot-2014.01 && > > >>>>> ld.bfd -pie -T u-boot.lds --gc-sections -Bstatic -Ttext > > >>>>> 0x0010E000 arch/arm/cpu/armv7/start.o --start-group > > >>>>> arch/arm/cpu/armv7/built-in.o > > >>>>> arch/arm/cpu/armv7/tegra20/built-in.o arch/arm/cpu/built-in.o > > >>>>> arch/arm/lib/built-in.o > > >>>>> board/toradex/colibri_t20_iris/built-in.o common/built-in.o > > >>>>> disk/built-in.o drivers/built-in.o drivers/dma/built-in.o > > >>>>> drivers/gpio/built-in.o drivers/i2c/built-in.o > > >>>>> drivers/input/built-in.o drivers/mmc/built-in.o > > >>>>> drivers/mtd/built-in.o drivers/mtd/nand/built-in.o > > >>>>> drivers/mtd/onenand/built-in.o drivers/mtd/spi/built-in.o > > >>>>> drivers/net/built-in.o drivers/net/phy/built-in.o > > >>>>> drivers/pci/built-in.o drivers/power/battery/built-in.o > > >>>>> drivers/power/built-in.o drivers/power/fuel_gauge/built-in.o > > >>>>> drivers/power/mfd/built-in.o drivers/power/pmic/built-in.o > > >>>>> drivers/serial/built-in.o drivers/spi/built-in.o > > >>>>> drivers/usb/eth/built-in.o drivers/usb/gadget/built-in.o > > >>>>> drivers/usb/host/built-in.o drivers/usb/musb-new/built-in.o > > >>>>> drivers/usb/musb/built-in.o drivers/usb/phy/built-in.o > > >>>>> drivers/usb/ulpi/built-in.o fs/built-in.o lib/built-in.o > > >>>>> lib/libfdt/built-in.o net/built-in.o test/built-in.o > > >>>>> --end-group /home/abuild/rpmbuild/BUILD/u-boot-2014.01/arch/arm/lib/eabi_compat.o > > >>>>> -L /usr/lib/gcc/armv7hl-suse-linux-gnueabi/4.8 -lgcc -Map > > >>>>> u-boot.map -o u-boot [ 178s] ld.bfd: u-boot: could not find > > >>>>> output section .gnu.hash [ 178s] ld.bfd: final link failed: > > >>>>> Nonrepresentable section on output [ 178s] Makefile:556: > > >>>>> recipe for target 'u-boot' failed [ 178s] make: *** [u-boot] > > >>>>> Error 1 > > >>>> > > >>>> You are trying this with your codebase, right? If so, can you > > >>>> try and build vanilla v2014.01 with the exact same build > > >>>> environment? > > >> > > >> Commented out all our patches at: > > >> https://build.opensuse.org/project/show/home:a_faerber:branches:Base:System > > >> > > >> Failure of any sunxi-added targets is to be expected, of course. > > > > > > Not sure I'm getting this: if you build vanilla v2014.01, there > > > shouldn't be any sunxi target built at all, should it? I can report the same issue with OBS build of u-boot. When u-boot is build with qemu emulated environment with gcc-4.8.2 (native armv7l toolchain) in the OBS it needs patch prepared by Andreas. However I can build the same code from u-boot directory (without this patch) with following toolchain: arm-v7a-linux-gnueabi-gcc (OSELAS.Toolchain-2013.12.0 linaro-4.8-2013.11) 4.8.3 20131111 Any ideas how to solve this? > > > > I removed the patches from the spec file in our build service. That > > doesn't drop the packages for those no longer patched-in targets, so > > failures of those targets are to be expected. I am not building > > locally. > > > > Here's a vanilla "highbank" target failing: > > https://build.opensuse.org/package/live_build_log/home:a_faerber:branches:Base:System/u-boot-highbank/openSUSE_Factory_ARM/armv7l > > > > >>> If it > > >>>> builds fine, then can you tell me which changes your patch(es) > > >>>> made to linker scripts in your tree wrt 2014.01? > > >>> > > >>> Ping. > > >> > > >> I had previously pointed to our patches and explained that they > > >> do not touch on any existing linker scripts. They merely change > > >> CONFIG_ options, tweak environment settings and add the sunxi > > >> targets. > > > > > > I am not asking about changing linker scripts; I am asking about > > > trying your build environment on the pristine v2014.01 codebase, > > > e.g. build all mainline ARM targets with your toolchains. > > > > You did ask above "which changes" our patches "made to linker > > scripts". And the answer is: None, apart from the already > > commented-out gnuhash.patch, which corresponds to this very patch > > under discussion. > > Understood -- my question about linker script changes was conditioned > to succeeding in building pristine v2014.01, so I had mentally put it > aside until v2014.01 build results are known. > > > >> As for the other open question, OBS does not package build > > >> intermediaries of failed builds, so I'll need to reproduce it > > >> locally. ATM I'm lacking time because QEMU is about to enter > > >> Hard Freeze for 2.0. > > > > > > Could you just run this in a git clone of U-Boot with v2014.01 > > > checked out? > > > > > > ARCH=arm CROSS_COMPILE=your-toolchain-prefix- ./MAKEALL > > > -a arm > > > > > > It would build all targets unattended using your toolchain > > > (assuming it is in your PATH of course). > > > > My local ARM machines are all 13.1, not Factory, but I can try > > running that command there later. > > Thanks! > > > Amicalement, > > Andreas > > Amicalement,
Hi Lukasz, On Thu, 13 Mar 2014 16:43:09 +0100, Lukasz Majewski <l.majewski@samsung.com> wrote: > I can report the same issue with OBS build of u-boot. > > When u-boot is build with qemu emulated environment with gcc-4.8.2 > (native armv7l toolchain) in the OBS it needs patch prepared by Andreas. Hmm, ok, so maybe I can reproduce this by building U-Boot on native armv7 hardware. Any target which systematically fails building? > However I can build the same code from u-boot directory (without this > patch) with following toolchain: > arm-v7a-linux-gnueabi-gcc (OSELAS.Toolchain-2013.12.0 > linaro-4.8-2013.11) 4.8.3 20131111 Hmm... So it depends on the toolchain. > Any ideas how to solve this? Are both toolchains you used available somewhere so that I can fetch them and experiment locally? Amicalement,
Hi Albert, > Hi Lukasz, > > On Thu, 13 Mar 2014 16:43:09 +0100, Lukasz Majewski > <l.majewski@samsung.com> wrote: > > > I can report the same issue with OBS build of u-boot. > > > > When u-boot is build with qemu emulated environment with gcc-4.8.2 > > (native armv7l toolchain) in the OBS it needs patch prepared by > > Andreas. > > Hmm, ok, so maybe I can reproduce this by building U-Boot on native > armv7 hardware. Any target which systematically fails building? The Trats2 fails to be build. But to me it seems like compiler and linker issue. > > > However I can build the same code from u-boot directory (without > > this patch) with following toolchain: > > arm-v7a-linux-gnueabi-gcc (OSELAS.Toolchain-2013.12.0 > > linaro-4.8-2013.11) 4.8.3 20131111 > > Hmm... So it depends on the toolchain. > > > Any ideas how to solve this? > > Are both toolchains you used available somewhere so that I can fetch > them and experiment locally? Yes they are available. References below: arm-v7a-linux-gnueabi-gcc (OSELAS.Toolchain-2013.12.0linaro-4.8-2013.11) 4.8.3 20131111 linaro-4.8-2013.11) 4.8.3 20131111 http://www.ptxdist.org/software/ptxdist/index_en.html The one which is used in the OBS: gcc-4.8-2.56.armv7l.rpm can be download from: http://download.tizen.org/snapshots/tizen/rd-pq/latest/repos/mobile/armv7l/packages/armv7l/ I hope, that it helps. > > Amicalement,
Hi Lukasz, On Fri, 14 Mar 2014 08:37:00 +0100, Lukasz Majewski <l.majewski@samsung.com> wrote: > Hi Albert, > > > Hi Lukasz, > > > > On Thu, 13 Mar 2014 16:43:09 +0100, Lukasz Majewski > > <l.majewski@samsung.com> wrote: > > > > > I can report the same issue with OBS build of u-boot. > > > > > > When u-boot is build with qemu emulated environment with gcc-4.8.2 > > > (native armv7l toolchain) in the OBS it needs patch prepared by > > > Andreas. > > > > Hmm, ok, so maybe I can reproduce this by building U-Boot on native > > armv7 hardware. Any target which systematically fails building? > > The Trats2 fails to be build. But to me it seems like compiler and > linker issue. > > > > > > However I can build the same code from u-boot directory (without > > > this patch) with following toolchain: > > > arm-v7a-linux-gnueabi-gcc (OSELAS.Toolchain-2013.12.0 > > > linaro-4.8-2013.11) 4.8.3 20131111 > > > > Hmm... So it depends on the toolchain. > > > > > Any ideas how to solve this? > > > > Are both toolchains you used available somewhere so that I can fetch > > them and experiment locally? > > Yes they are available. References below: > > arm-v7a-linux-gnueabi-gcc > (OSELAS.Toolchain-2013.12.0linaro-4.8-2013.11) 4.8.3 20131111 > linaro-4.8-2013.11) 4.8.3 20131111 > http://www.ptxdist.org/software/ptxdist/index_en.html > > > The one which is used in the OBS: > gcc-4.8-2.56.armv7l.rpm > > can be download from: > http://download.tizen.org/snapshots/tizen/rd-pq/latest/repos/mobile/armv7l/packages/armv7l/ > > I hope, that it helps. Thanks -- I'll test these, not today but certainly before next monday. Amicalement,
On 26 January 2014 20:48, Andreas Färber <afaerber@suse.de> wrote: > Avoids "could not find output section .gnu.hash" ld.bfd errors on openSUSE. > > Cc: Albert Aribaud <albert.u.boot@aribaud.net> > Cc: Tom Rini <trini@ti.com> > Signed-off-by: Andreas Färber <afaerber@suse.de> Acked-by: Simon Glass <sjg@chromium.org> Tested on snow Tested-by: Simon Glass <sjg@chromium.org> before: $ crosfw -b daisy Configuring for smdk5250 board... /usr/x86_64-pc-linux-gnu/armv7a-cros-linux-gnueabi/binutils-bin/2.22/ld.bfd.real: u-boot: could not find output section .gnu.hash /usr/x86_64-pc-linux-gnu/armv7a-cros-linux-gnueabi/binutils-bin/2.22/ld.bfd.real: final link failed: Nonrepresentable section on output make[1]: *** [u-boot] Error 1 make[1]: *** Waiting for unfinished jobs.... make: *** [sub-make] Error 2 after: no error Regards, Simon
Hi Andreas, On Mon, 27 Jan 2014 05:48:11 +0100, Andreas Färber <afaerber@suse.de> wrote: > Avoids "could not find output section .gnu.hash" ld.bfd errors on openSUSE. > > Cc: Albert Aribaud <albert.u.boot@aribaud.net> > Cc: Tom Rini <trini@ti.com> > Signed-off-by: Andreas Färber <afaerber@suse.de> > --- > More changes like this may be needed, but these I compile-tested with > v2014.01 (regression from v2013.10). colibri_t20_iris was runtime-tested. > GCC 4.8.2 r206511, binutils 2.24 > > arch/arm/cpu/u-boot.lds | 1 + > board/ti/am335x/u-boot.lds | 1 + > 2 files changed, 2 insertions(+) > > diff --git a/arch/arm/cpu/u-boot.lds b/arch/arm/cpu/u-boot.lds > index 4da5d24..fb8bfaf 100644 > --- a/arch/arm/cpu/u-boot.lds > +++ b/arch/arm/cpu/u-boot.lds > @@ -97,6 +97,7 @@ SECTIONS > .dynamic : { *(.dynamic*) } > .plt : { *(.plt*) } > .interp : { *(.interp*) } > + .gnu.hash : { *(.gnu.hash) } > .gnu : { *(.gnu*) } > .ARM.exidx : { *(.ARM.exidx*) } > .gnu.linkonce.armexidx : { *(.gnu.linkonce.armexidx.*) } > diff --git a/board/ti/am335x/u-boot.lds b/board/ti/am335x/u-boot.lds > index 6a734b3..fec4ccf 100644 > --- a/board/ti/am335x/u-boot.lds > +++ b/board/ti/am335x/u-boot.lds > @@ -113,6 +113,7 @@ SECTIONS > .dynstr : { *(.dynstr*) } > .dynamic : { *(.dynamic*) } > .hash : { *(.hash*) } > + .gnu.hash : { *(.gnu.hash) } > .plt : { *(.plt*) } > .interp : { *(.interp*) } > .gnu : { *(.gnu*) } Applied to u-boot-arm/master, thanks! Amicalement,
diff --git a/arch/arm/cpu/u-boot.lds b/arch/arm/cpu/u-boot.lds index 4da5d24..fb8bfaf 100644 --- a/arch/arm/cpu/u-boot.lds +++ b/arch/arm/cpu/u-boot.lds @@ -97,6 +97,7 @@ SECTIONS .dynamic : { *(.dynamic*) } .plt : { *(.plt*) } .interp : { *(.interp*) } + .gnu.hash : { *(.gnu.hash) } .gnu : { *(.gnu*) } .ARM.exidx : { *(.ARM.exidx*) } .gnu.linkonce.armexidx : { *(.gnu.linkonce.armexidx.*) } diff --git a/board/ti/am335x/u-boot.lds b/board/ti/am335x/u-boot.lds index 6a734b3..fec4ccf 100644 --- a/board/ti/am335x/u-boot.lds +++ b/board/ti/am335x/u-boot.lds @@ -113,6 +113,7 @@ SECTIONS .dynstr : { *(.dynstr*) } .dynamic : { *(.dynamic*) } .hash : { *(.hash*) } + .gnu.hash : { *(.gnu.hash) } .plt : { *(.plt*) } .interp : { *(.interp*) } .gnu : { *(.gnu*) }
Avoids "could not find output section .gnu.hash" ld.bfd errors on openSUSE. Cc: Albert Aribaud <albert.u.boot@aribaud.net> Cc: Tom Rini <trini@ti.com> Signed-off-by: Andreas Färber <afaerber@suse.de> --- More changes like this may be needed, but these I compile-tested with v2014.01 (regression from v2013.10). colibri_t20_iris was runtime-tested. GCC 4.8.2 r206511, binutils 2.24 arch/arm/cpu/u-boot.lds | 1 + board/ti/am335x/u-boot.lds | 1 + 2 files changed, 2 insertions(+)