Github messages for voidlinux
 help / color / mirror / Atom feed
From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] elfutils: cross build failure
Date: Tue, 17 Jan 2023 23:59:26 +0100	[thread overview]
Message-ID: <20230117225926.IyxdfoOv6hv4hV8tlnmpeEk72v3n5VOoCxv4SGco4p0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41704@inbox.vuxu.org>

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

Closed issue by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/41704

Description:
In config.log, I can see that it passed `-Wno-error=deprecated-declarations-Wno-error` to gcc which is not a valid option, so it failed.

```
%: ./xbps-src pkg -a armv6l-musl elfutils
...
=> elfutils-0.187_1: running do_configure ...
configure: WARNING: unrecognized options: --with-sysroot, --with-libtool-sysroot
checking for a BSD-compatible install... /builddir/.xbps-elfutils/wrappers/install -c
checking whether build environment is sane... yes
checking for arm-linux-musleabihf-strip... arm-linux-musleabihf-strip
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether make supports nested variables... (cached) yes
checking build system type... x86_64-unknown-linux-musl
checking host system type... arm-unknown-linux-musleabihf
checking whether make supports the include directive... yes (GNU style)
checking for arm-linux-musleabihf-gcc... arm-linux-musleabihf-gcc
checking whether the C compiler works... no
configure: error: in `/builddir/elfutils-0.187':
configure: error: C compiler cannot create executables
See `config.log' for more details
=> ERROR: elfutils-0.187_1: do_configure: '${configure_script} ${configure_args}' exited with 77
=> ERROR:   in do_configure() at common/build-style/gnu-configure.sh:8
```

  reply	other threads:[~2023-01-17 22:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 21:44 [ISSUE] " paper42
2023-01-17 22:59 ` Johnnynator [this message]
2023-01-17 22:59 ` Johnnynator

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=20230117225926.IyxdfoOv6hv4hV8tlnmpeEk72v3n5VOoCxv4SGco4p0@z \
    --to=johnnynator@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).