From: Egor Shestakov <vedingrot@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: m4-native configure fails
Date: Tue, 17 Mar 2026 17:44:16 +0000 [thread overview]
Message-ID: <abmS8Bk0sFZOKY2f@silver> (raw)
Hi, List!
I'm trying to follow the Quick Build instruction under ALT Linux, build
fails on m4-native do_configure(). Do you have some idea what is could be?
It looks like a missed dependency but gcc in the configure script uses
sysroot.
Part of config.log:
```
configure:6795: $? = 1
configure:6815: checking whether the C compiler works
configure:6837: gcc -isystem/home/ved_b/yocto_build/bitbake-builds/poky-master/build/tmp/work/x86_64-linux/m4-native/1.4.20/recipe-sysroot-native/usr/include -O2 -pipe -isystem/home/ved_b/yocto_build/bitbake-builds/poky-master/build/tmp/work/x86_64-linux/m4-native/1.4.20/recipe-sysroot-native/usr/include -L/home/ved_b/yocto_build/bitbake-builds/poky-master/build/tmp/work/x86_64-linux/m4-native/1.4.20/recipe-sysroot-native/usr/lib -L/home/ved_b/yocto_build/bitbake-builds/poky-master/build/tmp/work/x86_64-linux/m4-native/1.4.20/recipe-sysroot-native/lib -Wl,--enable-new-dtags -Wl,-rpath-link,/home/ved_b/yocto_build/bitbake-builds/poky-master/build/tmp/work/x86_64-linux/m4-native/1.4.20/recipe-sysroot-native/usr/lib -Wl,-rpath-link,/home/ved_b/yocto_build/bitbake-builds/poky-master/build/tmp/work/x86_64-linux/m4-native/1.4.20/recipe-sysroot-native/lib -Wl,-rpath,/home/ved_b/yocto_build/bitbake-builds/poky-master/build/tmp/work/x86_64-linux/m4-native/1.4.20/recipe-sysroot-native/usr/lib -Wl,-rpath,/home/ved_b/yocto_build/bitbake-builds/poky-master/build/tmp/work/x86_64-linux/m4-native/1.4.20/recipe-sysroot-native/lib -Wl,-O1 -Wl,--allow-shlib-undefined -Wl,--dynamic-linker=/home/ved_b/yocto_build/bitbake-builds/poky-master/build/tmp/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2 -pthread conftest.c >&5
x86_64-alt-linux-gcc: fatal error: cannot execute 'cc1': posix_spawnp: No such file or directory
compilation terminated.
configure:6841: $? = 1
configure:6882: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "GNU M4"
| #define PACKAGE_TARNAME "m4"
| #define PACKAGE_VERSION "1.4.20"
| #define PACKAGE_STRING "GNU M4 1.4.20"
| #define PACKAGE_BUGREPORT "bug-m4@gnu.org"
| #define PACKAGE_URL "https://www.gnu.org/software/m4/"
| #define PACKAGE "m4"
| #define VERSION "1.4.20"
| /* end confdefs.h. */
|
| int
| main (void)
| {
|
| ;
| return 0;
| }
configure:6887: error: in '/home/ved_b/yocto_build/bitbake-builds/poky-master/build/tmp/work/x86_64-linux/m4-native/1.4.20/build':
configure:6889: error: C compiler cannot create executables
See 'config.log' for more details
```
Also, I have some strange failure messages, although they don't look fatal.
```
gcc version 14.3.1 20251017 (ALT Sisyphus 14.3.1-alt2) (GCC)
configure:6795: $? = 0
configure:6784: gcc -V >&5
x86_64-alt-linux-gcc: error: unrecognized command-line option '-V'
x86_64-alt-linux-gcc: fatal error: no input files
compilation terminated.
configure:6795: $? = 1
configure:6784: gcc -qversion >&5
x86_64-alt-linux-gcc: error: unrecognized command-line option '-qversion'; did you mean '--version'?
x86_64-alt-linux-gcc: fatal error: no input files
compilation terminated.
configure:6795: $? = 1
configure:6784: gcc -version >&5
x86_64-alt-linux-gcc: error: unrecognized command-line option '-version'
x86_64-alt-linux-gcc: fatal error: no input files
compilation terminated.
```
config.log:
https://pastebin.com/vaBmnqhk
log.do_configure:
https://pastebin.com/7UkJwtjh
Thanks in advance!
--
Egor Shestakov
vedingrot ascii(0x40) gmail ascii(0x2E) com
reply other threads:[~2026-03-17 17:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=abmS8Bk0sFZOKY2f@silver \
--to=vedingrot@gmail.com \
--cc=yocto@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.