From: Waldemar Brodkorb <wbx@openadk.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Waldemar Brodkorb <wbx@openadk.org>, libc-help@sourceware.org
Subject: Re: cross-toolchain for x86 fails to compile
Date: Mon, 7 Feb 2022 16:16:57 +0100 [thread overview]
Message-ID: <YgE36Z/3DZ+p8HPJ@waldemar-brodkorb.de> (raw)
In-Reply-To: <2c31877a-ae19-8e6a-e99f-e2f687df89fd@linaro.org>
Hi,
Adhemerval Zanella wrote,
>
>
> On 04/02/2022 21:35, Waldemar Brodkorb wrote:
> > Hi,
> >
> > I am doing my regular update in OpenADK and updated to glibc 2.35.
> > All toolchains are build fine except x86.
> >
> > I am getting following error with binutils 2.37 and gcc 11.2:
> > /home/wbx/embedded-test/openadk/toolchain_qemu-x86_glibc/usr/bin/i686-openadk-linux-gnu-gcc
> > -o
> > /home/wbx/embedded-test/openadk/toolchain_build_qemu-x86_glibc/w-glibc-2.35-1/glibc-2.35-final/support/test-run-command
> > -nostdlib -nostartfiles -static -static-pie
> > /home/wbx/embedded-test/openadk/toolchain_build_qemu-x86_glibc/w-glibc-2.35-1/glibc-2.35-final/csu/rcrt1.o
> > /home/wbx/embedded-test/openadk/toolchain_build_qemu-x86_glibc/w-glibc-2.35-1/glibc-2.35-final/csu/crti.o
> > `/home/wbx/embedded-test/openadk/toolchain_qemu-x86_glibc/usr/bin/i686-openadk-linux-gnu-gcc
> > --print-file-name=crtbeginS.o`
> > /home/wbx/embedded-test/openadk/toolchain_build_qemu-x86_glibc/w-glibc-2.35-1/glibc-2.35-final/support/test-run-command.o
> > /home/wbx/embedded-test/openadk/toolchain_build_qemu-x86_glibc/w-glibc-2.35-1/glibc-2.35-final/elf/static-stubs.o
> > /home/wbx/embedded-test/openadk/toolchain_build_qemu-x86_glibc/w-glibc-2.35-1/glibc-2.35-final/support/libsupport_nonshared.a
> > -Wl,--start-group
> > /home/wbx/embedded-test/openadk/toolchain_build_qemu-x86_glibc/w-glibc-2.35-1/glibc-2.35-final/libc.a
> > -lgcc -Wl,--end-group
> > `/home/wbx/embedded-test/openadk/toolchain_qemu-x86_glibc/usr/bin/i686-openadk-linux-gnu-gcc
> > --print-file-name=crtendS.o`
> > /home/wbx/embedded-test/openadk/toolchain_build_qemu-x86_glibc/w-glibc-2.35-1/glibc-2.35-final/csu/crtn.o
> > /home/wbx/embedded-test/openadk/toolchain_qemu-x86_glibc/usr/lib/gcc/i686-openadk-linux-gnu/11.2.0/../../../../i686-openadk-linux-gnu/bin/ld:
> > /home/wbx/embedded-test/openadk/toolchain_build_qemu-x86_glibc/w-glibc-2.35-1/glibc-2.35-final/libc.a(setlocale.o):
> > relocation R_386_GOT32 against absolute symbol
> > `_nl_current_LC_CTYPE_used' in section `__libc_freeres_fn' is
> > disallowed
> > collect2: error: ld returned 1 exit status
> > gmake[8]: *** [../Rules:293:
> > /home/wbx/embedded-test/openadk/toolchain_build_qemu-x86_glibc/w-glibc-2.35-1/glibc-2.35-final/support/test-run-command]
> > Error 1
> > gmake[7]: *** [Makefile:483: support/others] Error 2
> > gmake[6]: *** [Makefile:9: all] Error 2
> > gmake[5]: *** [Makefile:62:
> > /home/wbx/embedded-test/openadk/toolchain_build_qemu-x86_glibc/w-glibc-2.35-1/glibc-2.35/.compiled]
> > Error 2
> > gmake[4]: *** [Makefile:106: glibc-compile] Error 2
> > gmake[3]: *** [mk/build.mk:228: toolchain/final] Error 2
> > gmake[2]: *** [/home/wbx/embedded-test/openadk/mk/build.mk:177:
> > world] Error 2
> > gmake[1]: *** [Makefile.adk:25: all] Error 2
> > make: *** [Makefile:22: all] Error 2
> > build failed
> >
> > Is it a known bug in binutils or glibc?
>
> None we are aware of and we do build check on i686 constantly. I just did a build
> with gcc 11.2 and binutins 2.37 and I haven't see any issue. How did you build
> gcc and binutils?
Thanks for your response. It seems TARGET CFLAGS are not allowed to
be -Os or any machine specific optimizations for x86. Forcing -O2
did work.
best regards
Waldemar
next prev parent reply other threads:[~2022-02-07 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 0:35 Waldemar Brodkorb
2022-02-07 12:09 ` Adhemerval Zanella
2022-02-07 15:16 ` Waldemar Brodkorb [this message]
2022-02-07 17:08 ` Adhemerval Zanella
2022-02-07 22:59 ` H.J. Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YgE36Z/3DZ+p8HPJ@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-help@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).