From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Mircea Ciocan <m.ciocan@ppc-ag.de>
Cc: ptxdist <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] OSELAS Toolchain 2023.07.0 fails to build clang
Date: Thu, 19 Oct 2023 09:16:47 +0200 [thread overview]
Message-ID: <ZTDX3zP1uaPSbVyL@pengutronix.de> (raw)
In-Reply-To: <1451693282.147394.1697624744897.JavaMail.zimbra@ppc-ag.de>
On Wed, Oct 18, 2023 at 12:25:44PM +0200, Mircea Ciocan wrote:
> ----- Ursprüngliche Mail -----
> Hi,
>
> On Tue, Oct 17, 2023 at 11:45:22AM +0200, Mircea Ciocan wrote:
> > I was trying to compile the OSELAS-2023.07.0 from the original sources on a Ubuntu 22.04 and got the following error:
> >
> > ---------------------------
> > target: cross-clang.extract
> > ---------------------------
> >
> > extract: pkg_src=OSELAS.Toolchain-2023.07.0x/src/clang-16.0.6.src.tar.xz
> > extract: pkg_extract_dir=OSELAS.Toolchain-2023.07.0x/platform-arm-v7a-linux-gnueabihf-gcc-13.1.1-clang-16.0.6-glibc-2.37-binutils-2.40-kernel-6.3.6-sanitized/build-cross/clang-16.0.6
> > patchin: no patches found
> > finished target cross-clang.extract
> > make: *** No rule to make target '/home/dev/Software/Toolchain/OSELAS.Toolchain-2023.07.0x/platform-arm-v7a-linux-gnueabihf-gcc-13.1.1-clang-16.0.6-glibc-2.37-binutils-2.40-kernel-6.3.6-sanitized/sysroot-cross/bin/llvm-config', needed by '/home/dev/Software/Toolchain/OSELAS.Toolchain-2023.07.0x/platform-arm-v7a-linux-gnueabihf-gcc-13.1.1-clang-16.0.6-glibc-2.37-binutils-2.40-kernel-6.3.6-sanitized/state/cross-llvm.prepare'. Stop.
> > make: *** [build_all_v2.mk:44: gstate/arm-v7a-linux-gnueabihf-gcc-13.1.1-clang-16.0.6-glibc-2.37-binutils-2.40-kernel-6.3.6-sanitized.build] Error 2
> >
> > It seems that the build directory is not even created.
> > Do you have any idea what can I do ?
>
> Just a wild guess: You're using ptxdist-2023.10.0 to build the toolchain.
> Don't do that. Use ptxdist-2023.07.0 as specified in the config files.
>
> Regards,
> Michael
>
> Hello Michael and thanks for the answer,
> should I stay then 2023.07.0 or should go to 2023.07.1, I remember it was a regression, is that relevant for the toolchain project ?
Either one works. The issue is mostly cosmetic anyways and you're probably
not affected by that anyways.
Regards,
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 |
prev parent reply other threads:[~2023-10-19 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1015967027.165350.1697535922582.JavaMail.zimbra@ppc-ag.de>
2023-10-18 5:48 ` Michael Olbrich
2023-10-18 10:25 ` Mircea Ciocan
2023-10-19 7:16 ` 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=ZTDX3zP1uaPSbVyL@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=m.ciocan@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