All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sourabh Hegde" <hrsourabh011@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: coreutils-native-8.32-r0 do_configure: configure failed
Date: Mon, 21 Feb 2022 05:14:12 -0800	[thread overview]
Message-ID: <FtDJ.1645449252258283472.8QNX@lists.yoctoproject.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]

Hello All,

I am facing an issue while building images for Raspberry Pi CM4. Earlier I was working with Dunfell release and now upgraded to Honister. And now I am getting an error like:

.
.
checking whether mkdir handles trailing slash... yes
checking whether mkdir handles trailing dot... yes
checking for mkfifo... yes
checking whether mkfifo rejects trailing slashes... yes
checking whether mknod can create fifo without root privileges... configure: error: in `/home/raspcm4/build-rauc/tmp-glibc/work/x86_64-linux/coreutils-native/8.32-r0/build':
configure: error: you should not run configure as root (set FORCE_UNSAFE_CONFIGURE=1 in environment to bypass this check)
See `config.log' for more details
NOTE: The following config.log files may provide further information.
NOTE: /home/raspcm4/build-rauc/tmp-glibc/work/x86_64-linux/coreutils-native/8.32-r0/build/config.log
ERROR: configure failed
WARNING: exit code 1 from a shell command.
.
.

I have set "export FORCE_UNSAFE_CONFIGURE=1" but still getting same error.

I am building from "/home/ dir and not "/root/" dir.

Can someone please let me know how to resolve this issue?

Your help will be much appreciated.

Thanks in advance.

[-- Attachment #2: Type: text/html, Size: 1337 bytes --]

             reply	other threads:[~2022-02-21 13:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 13:14 Sourabh Hegde [this message]
2022-02-21 15:59 ` [yocto] coreutils-native-8.32-r0 do_configure: configure failed Ross Burton

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=FtDJ.1645449252258283472.8QNX@lists.yoctoproject.org \
    --to=hrsourabh011@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.