From: Thorsten Glaser <tg@mirbsd.de>
To: musl@lists.openwall.com
Subject: Re: [musl] musl-gcc: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'
Date: Mon, 5 Feb 2024 10:16:21 +0000 (UTC) [thread overview]
Message-ID: <Pine.BSM.4.64L.2402051012350.20814@herc.mirbsd.org> (raw)
In-Reply-To: <Zb_t5jr18pCoSpJ6@voyager>
Markus Wichmann dixit:
>> >, but the gcc wrapper. This is not
>> >the recommended way to use musl except as minimal evaluation setup or
>> >for compiling very simple programs
>>
>> Huh? Where does it say that, and how else is one supposed to do this?
[…]
>musl-gcc (and similar wrappers for other libcs) is in principle limited
>by the fact that the target libraries it links in are still built
>against the system libc.
The target library is exactly libc (musl) though.
>mismatch. Some of GCC's target libraries hook deeply into glibc
>implementation internals once they know to be running on a glibc
>platform, with libstdc++ being probably the worst offender.
Ah, ok, good point. I know libgcc.a doesn’t, and for some reason
libgcc_eh.a is also pulled in, though I don’t see anything using
its functions.
bye,
//mirabilos
--
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh
prev parent reply other threads:[~2024-02-05 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 8:20 [musl] musl: " Thorsten Glaser
2024-02-03 8:37 ` Thorsten Glaser
2024-02-03 19:32 ` Rich Felker
2024-02-04 2:14 ` [musl] musl-gcc: " Thorsten Glaser
2024-02-04 20:04 ` Markus Wichmann
2024-02-05 10:16 ` Thorsten Glaser [this message]
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=Pine.BSM.4.64L.2402051012350.20814@herc.mirbsd.org \
--to=tg@mirbsd.de \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).