mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Shiz <hi@shiz.me>
To: musl@lists.openwall.com
Subject: Re: ./configure compiler-rt patch
Date: Wed, 21 Feb 2018 11:30:07 +0100	[thread overview]
Message-ID: <0A0AC15F-C709-4731-ADC3-8CCCFE35405B@shiz.me> (raw)
In-Reply-To: <20180221021256.GB1436@brightrain.aerifal.cx>

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


> On 21 Feb 2018, at 03:12, Rich Felker <dalias@libc.org> wrote:
> 
> It might be optimal to try the basename produced by
> -print-libgcc-file-name, stripping the "lib" and ".a" parts and using
> it with -l, to see if that works. But it might not actually work for
> anything other than gcc. I know it doesn't (or at least didn't in the
> past) work for pcc.

Sadly, that won’t work for clang, to the best of my knowledge.
Quickly tested on a macOS machine, but I think it’s the same anywhere:

~ » clang -rtlib=compiler-rt -print-libgcc-file-name
/Applications/.../usr/lib/clang/9.0.0/lib/darwin17.4.0/libclang_rt.builtins-x86_64.a
~ » clang -lclang_rt.builtins-x86_64
ld: library not found for -lclang_rt.builtins-x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I’m fairly sure -lcompiler_rt used to work at some point, but it seems
they stripped support, which makes sense given that compiler-rt is
actually multiple things now, and this would refer to the builtins part
of it.

- Shiz

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-02-21 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13 14:53 Matúš Olekšák
2018-02-21  2:12 ` Rich Felker
2018-02-21 10:30   ` Shiz [this message]
2018-02-21 10:58     ` Dmitry Golovin
  -- strict thread matches above, loose matches on Subject: below --
2018-02-06 21:16 Matúš Olekšák

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=0A0AC15F-C709-4731-ADC3-8CCCFE35405B@shiz.me \
    --to=hi@shiz.me \
    --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).