From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libtool: fix include paths when cross compiling
Date: Wed, 15 Feb 2023 07:20:20 +0100 [thread overview]
Message-ID: <20230215062020.B5bC8GkHLwSoNJLhspPwDteLcE6ce7YkH8mRois0qU4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40606@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/40606#issuecomment-1430811971
Comment:
Alright, I think I see the issue.
`libtool: link: cc -fPIC -DPIC -shared -nostdlib /usr/lib/../lib64/crti.o ...` is supposed to be `libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/../lib64/crti.o`
That seems to be due to it being sed'ed to the form of `CC=${CC:=c++}` which is just a regular assignment when compiled natively.
The latest commit works for me, feel free to verify when you are available @dkwo
next prev parent reply other threads:[~2023-02-15 6:20 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 8:10 [PR PATCH] " oreo639
2022-11-19 22:17 ` dkwo
2022-11-19 22:18 ` dkwo
2022-11-19 22:18 ` dkwo
2022-11-19 22:29 ` oreo639
2022-11-19 22:30 ` oreo639
2022-11-20 14:37 ` dkwo
2022-11-20 18:41 ` paper42
2022-11-20 20:25 ` oreo639
2022-11-20 20:37 ` [PR PATCH] [Updated] " oreo639
2022-11-20 21:05 ` oreo639
2022-11-20 21:08 ` oreo639
2022-11-21 15:38 ` dkwo
2022-11-21 17:21 ` oreo639
2022-11-21 17:21 ` oreo639
2022-11-21 18:30 ` dkwo
2022-11-21 18:31 ` oreo639
2022-11-21 18:33 ` dkwo
2023-02-06 20:17 ` dkwo
2023-02-06 20:18 ` dkwo
2023-02-06 20:19 ` paper42
2023-02-15 4:21 ` [PR PATCH] [Updated] " oreo639
2023-02-15 4:29 ` oreo639
2023-02-15 4:34 ` oreo639
2023-02-15 5:26 ` oreo639
2023-02-15 6:08 ` oreo639
2023-02-15 6:20 ` oreo639 [this message]
2023-02-15 6:20 ` oreo639
2023-02-15 6:23 ` [PR PATCH] [Updated] " oreo639
2023-02-15 6:24 ` oreo639
2023-02-15 6:26 ` [PR PATCH] [Updated] " oreo639
2023-02-15 6:27 ` oreo639
2023-02-15 6:56 ` oreo639
2023-02-15 7:04 ` oreo639
2023-02-15 7:13 ` oreo639
2023-02-15 7:18 ` oreo639
2023-02-15 7:30 ` oreo639
2023-02-15 7:30 ` oreo639
2023-02-15 8:48 ` oreo639
2023-02-15 10:57 ` oreo639
2023-02-15 20:06 ` dkwo
2023-02-15 20:09 ` [PR PATCH] [Updated] " oreo639
2023-02-25 1:35 ` oreo639
2023-02-25 1:35 ` oreo639
2023-02-26 10:15 ` [PR PATCH] [Merged]: " paper42
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=20230215062020.B5bC8GkHLwSoNJLhspPwDteLcE6ce7YkH8mRois0qU4@z \
--to=oreo639@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).