mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: "Luis Grünewald" <l.gruenewald@ppc-ag.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] OSELAS Toolchain for ARM-v7em with newlib and c++ support
Date: Fri, 31 Mar 2023 10:45:06 +0200	[thread overview]
Message-ID: <ZCadko004DpE8lhf@pengutronix.de> (raw)
In-Reply-To: <1550513112.87110.1680075606632.JavaMail.zimbra@ppc-ag.de>

Hi,

On Wed, Mar 29, 2023 at 09:40:06AM +0200, Luis Grünewald wrote:
> I am trying to build the Oselas-Toolchain using the following setup:
> 
> - HOST-OS: Ubuntu 22.04.2 LTS
> - HOST-CPU: 11th Gen Intel(R) Core (TM) i7-1165G7 @ 2.80GHz × 8
> - Osleas project: OSELAS.Toolchain-2022.10.0 (https://git.pengutronix.de/cgit/OSELAS.Toolchain/tag/?h=v2022.10.0)
> - Ptxdist Version: ptxdist-2023.01.0 (https://public.pengutronix.de/software/ptxdist/)

Not the cause of your specific problem, but in general, you should always
use the ptxdist version that is specified in the ptxconfig files. 2022.10.0
in this case. Using a newer version can cause problems.

> 
> To build the toolchain I am doing the following steps:
> 
> 1. Selecting the ptxconfig : arm-v7em-eabihf_gcc-12.2.1_newlib-4.2.0.20211231_binutils-2.39
> 2. using "ptxdist migrate" to update .ptxconfg
> 3. Since I need support for C++, I add C++ as an "Additional supported language" using "ptxdist menuconfig"
> 4. unsing the "build_one.sh arm-v7em-eabihf_gcc-12.2.1_newlib-4.2.0.20211231_binutils-2.39" to build the toolchain
> 
> build_one.sh fails with the following error:
> 
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> checking whether printf hooks are supported... no
> checking whether nl_langinfo should be used... no
> checking whether nl_langinfo should be used for wide char locale info... yes
> checking what to include in include/gstdint.h... stdint.h (already complete)
> checking for GNU c++filt... /usr/bin/c++filt
> checking for shared libgcc... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
> no
> checking whether localeconv should be used... make[1]: *** [Makefile:12209: configure-target-libstdc++-v3] Error 1
> make[1]: *** Waiting for unfinished jobs....
> .
> .
> .
> .
> config.status: executing depfiles commands
> config.status: executing libtool commands
> make[1]: Leaving directory '/home/l.gruenewald/projects/m4Communication/toolchain_test/test3/OSELAS.Toolchain-2022.10.0/platform-arm-v7em-eabihf-gcc-12.2.1-newlib-4.2.0.20211231-binutils-2.39/build-cross/gcc-12-20221022-build'
> make: *** [Makefile:1027: all] Error 2
> make: Leaving directory '/home/l.gruenewald/projects/m4Communication/toolchain_test/test3/OSELAS.Toolchain-2022.10.0/platform-arm-v7em-eabihf-gcc-12.2.1-newlib-4.2.0.20211231-binutils-2.39/build-cross/gcc-12-20221022-build'
> make: *** [/home/l.gruenewald/projects/m4Communication/toolchain_test/test3/ptxdist-2023.01.0/rules/post/ptxd_make_world_compile.make:20: /home/l.gruenewald/projects/m4Communication/toolchain_test/test3/OSELAS.Toolchain-2022.10.0/platform-arm-v7em-eabihf-gcc-12.2.1-newlib-4.2.0.20211231-binutils-2.39/state/cross-gcc.compile] Error 2
> make: *** [/home/l.gruenewald/projects/m4Communication/toolchain_test/test3/OSELAS.Toolchain-2022.10.0/build_all_v2.mk:44: gstate/arm-v7em-eabihf-gcc-12.2.1-newlib-4.2.0.20211231-binutils-2.39.build] Fehler 2
> 
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 
> 
> More Errors can be found in <OSELAS.Toolchain-2022.10.0/platform-arm-v7em-eabihf-gcc-12.2.1-newlib-4.2.0.20211231-binutils-2.39/build-cross/gcc-12-20221022-build/arm-v7em-eabihf/libstdc++-v3/config.log>.
> Here is a link to my libstdc++-v3/config.log : https://controlc.com/a342dcd8
> 
> Building the toolchain using the "arm-v7em-eabihf_gcc-12.2.1_newlib-4.2.0.20211231_binutils-2.39.ptxconfig" without any changes works fine.
> But after using "debain/bin/build.sh" to build the .deb package, in the /bin folder the link called "arm-v7em-eabihf-g++" is broken.
> 
> Do you have any suggestion how to build the Oslastoolchain using the "arm-v7em-eabihf_gcc-12.2.1_newlib-4.2.0.20211231_binutils-2.39.ptxconfig" so that in the end the "g++" compiler will be included ?

Sorry, not really. The C++ compiler is disabled for all newlib toolchains.
I think there is something broken there in general, but I've not looked
into that for a long time.

Michael

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2023-03-31  8:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  7:40 Luis Grünewald
2023-03-31  8:45 ` Michael Olbrich [this message]

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=ZCadko004DpE8lhf@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=l.gruenewald@ppc-ag.de \
    --cc=ptxdist@pengutronix.de \
    /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