From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] meson build style prints wrong `Host machine` information
Date: Thu, 17 Jun 2021 04:24:04 +0200 [thread overview]
Message-ID: <20210617022404.bTsNrxM1CrQjm0cdiwa-y5NilGaTKqRvW-PkmSZDsG8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31527@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2075 bytes --]
Closed issue by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/31527
Description:
With the same cross file generated by `xbps-src -a armv6l-musl`
In a build inside `xbps-src`, for example `wlroots`:
```
Using 'CFLAGS' from environment with value: '-fstack-clash-protection -D_FORTIFY_SOURCE=2 -O2 -pipe -march=armv6 -mfpu=vfp -mfloat-abi=hard -I/usr/arm-linux-musleabihf/usr/include'
Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now -Wl,--as-needed -L/usr/arm-linux-musleabihf/usr/lib'
Using 'CPPFLAGS' from environment with value: ' '
C compiler for the host machine: arm-linux-musleabihf-gcc (gcc 10.2.1 "arm-linux-musleabihf-gcc (GCC) 10.2.1 20201203")
C linker for the host machine: arm-linux-musleabihf-gcc ld.bfd 2.35.1
Using 'CC_FOR_BUILD' from environment with value: 'cc'
Using 'CFLAGS_FOR_BUILD' from environment with value: '-O2 -pipe'
Using 'LDFLAGS_FOR_BUILD' from environment with value: ''
Using 'CPPFLAGS_FOR_BUILD' from environment with value: ''
C compiler for the build machine: cc (gcc 10.2.1 "cc (GCC) 10.2.1 20201203")
C linker for the build machine: cc ld.bfd 2.35.1
Build machine cpu family: x86_64
Build machine cpu: x86_64
Host machine cpu family: x86_64
Host machine cpu: x86_64
Target machine cpu family: arm
Target machine cpu: armv6l
```
In a build outside `xbps-src`:
```
C compiler for the host machine: arm-linux-musleabihf-gcc (gcc 10.2.1 "arm-linux-musleabihf-gcc (GCC) 10.2.1 20201203")
C linker for the host machine: arm-linux-musleabihf-gcc ld.bfd 2.35.1
C compiler for the build machine: cc (gcc 10.2.1 "cc (GCC) 10.2.1 20201203")
C linker for the build machine: cc ld.bfd 2.35.1
Build machine cpu family: x86_64
Build machine cpu: x86_64
Host machine cpu family: arm
Host machine cpu: armv6l
Target machine cpu family: arm
Target machine cpu: armv6l
```
It shouldn't be a huge issue and I think things are still working correctly (since it's using the correct compiler), would mostly just like to understand what's wrong.
next prev parent reply other threads:[~2021-06-17 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 16:36 [ISSUE] " ericonr
2021-06-16 18:28 ` Johnnynator
2021-06-17 2:24 ` ericonr [this message]
2021-06-17 2:24 ` ericonr
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=20210617022404.bTsNrxM1CrQjm0cdiwa-y5NilGaTKqRvW-PkmSZDsG8@z \
--to=ericonr@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).