From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: ptxdist <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] nodejs build problems
Date: Wed, 10 Jul 2024 08:31:53 +0200 [thread overview]
Message-ID: <Zo4q2SoL42ITK8K2@pengutronix.de> (raw)
In-Reply-To: <5397b601-b66b-4a08-8076-e38a660fe227@mev.co.uk>
On Tue, Jul 09, 2024 at 03:45:31PM +0100, Ian Abbott wrote:
> Hello folks,
>
> This is my first time trying to build nodejs for arm-v7a-linux-gnueabif and
> I'm not having much luck. It's failing at the "nodejs.prepare" stage in the
> `try_check_compiler(CXX, 'c++)` call in "configure.py:
>
> ---------------------[8<]------------------------
>
> Traceback (most recent call last):
> File "/mnt/lindata/work/abbotti/ptxdist/projects/its-ipt4-demo/platform-its-ipt4v2/build-target/node-v20.11.0/./configure",
> line 29, in <module>
> Node.js configure: Found Python 3.11.2...
> import configure
> File "/mnt/lindata/work/abbotti/ptxdist/projects/its-ipt4-demo/platform-its-ipt4v2/build-target/node-v20.11.0/configure.py",
> line 2026, in <module>
> check_compiler(output)
> File "/mnt/lindata/work/abbotti/ptxdist/projects/its-ipt4-demo/platform-its-ipt4v2/build-target/node-v20.11.0/configure.py",
> line 1038, in check_compiler
> ok, is_clang, clang_version, gcc_version = try_check_compiler(CXX,
> 'c++')
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/mnt/lindata/work/abbotti/ptxdist/projects/its-ipt4-demo/platform-its-ipt4v2/build-target/node-v20.11.0/configure.py",
> line 944, in try_check_compiler
> gcc_version = tuple(map(int, values[1:1+3]))
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ValueError: invalid literal for int() with base 10: '__STDC__'
> make: *** [/usr/local/lib/ptxdist-2024.03.0/rules/nodejs.make:84: /mnt/lindata/work/abbotti/ptxdist/projects/its-ipt4-demo/platform-its-ipt4v2/state/nodejs.prepare]
> Error 1
> ---------------------[>8]------------------------
>
> This is being built in a Debian 12 ("bookworm") schroot. (I also get the
> same problem when building in my usual Debian "testing" environment.)
>
> As you can see, I am using ptxdist-2024.03.0. The selected_toolchain is
> `/opt/OSELAS.Toolchain-2023.07.1/arm-v7a-linux-gnueabihf/gcc-13.2.1-clang-16.0.6-glibc-2.37-binutils-2.40-kernel-6.3.6-sanitized/bin`.
>
> I tried downgrading to the nodejs-v18.13.0 rules and patch series from
> ptxdist-2024.01.0, but it fails in the same way, so I think there is some
> incompatibility between that `try_check_compiler` function and the
> toolchain.
>
> I'm wondering if anyone else has seen the same problem and managed to solve
> it?
Hmmm, I've not seen this in my build tests. And I'm testing that
combination as well. If you run ptxdist with '-v' then the whole compiler
commandline is recorded in the logfile (with a 'wrapper:' prefix). Maybe
call it manually to see what actually happens here.
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 |
next prev parent reply other threads:[~2024-07-10 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 14:45 Ian Abbott
2024-07-10 6:31 ` Michael Olbrich [this message]
2024-07-10 11:38 ` Ian Abbott
2024-07-10 16:45 ` Ian Abbott
2024-07-11 6:53 ` Michael Olbrich
2024-07-11 9:47 ` Ian Abbott
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=Zo4q2SoL42ITK8K2@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=abbotti@mev.co.uk \
--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