From: John Spencer <maillist-musl@barfooze.de>
To: musl@lists.openwall.com
Cc: Richard Pennington <rich@pennware.com>
Subject: Re: build musl with clang
Date: Thu, 23 Aug 2012 14:24:17 +0200 [thread overview]
Message-ID: <503620F1.7010003@barfooze.de> (raw)
In-Reply-To: <5035E16E.50004@gmail.com>
On 08/23/2012 09:53 AM, agent wrote:
>
> if i use musl's ld-musl (as far as i can notice it is just symlink to
> libc.so) i get a segfault. gdb says:
>
> (gdb) r
> Starting program: /home/agent/dev/musl/musl-0.9.4_clang/lib/t.out
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xb7f9d73a in find_sym () from /lib/ld-musl-i386.so.1
> (gdb) where
> #0 0xb7f9d73a in find_sym () from /lib/ld-musl-i386.so.1
>
> btw, exactly the same things happen when i try it with gcc (4.6.3 from
> ubuntu).
this sounds as if the binary uses gnu hash as opposed to sysv hash. did
you use ./configure ?
see FAQ in http://wiki.musl-libc.org
>
> if i compile statically with gcc the program works fine, but with
> clang it even does not compile (i mean link):
>
> /opt/musl-clang/lib/libc.a(vfprintf.o): In function `printf_core':
> src/stdio/vfprintf.c:(.text+0x1088): undefined reference to `__udivdi3'
> src/stdio/vfprintf.c:(.text+0x10a6): undefined reference to `__umoddi3'
>
these functions are part of libgcc as nsz already stated.
> maybe it is impossible to compile a working musl with clang at this
> stage, maybe a quick fix can be applied (:
>
there is another known bug in clang which will lead to calloc getting
wrongly optimized away, because clang disrespects -ffree-standing.
Richard Pennington wanted to reported this to the LLVM maillist months
ago, but afaik he still hasn't done this.
prev parent reply other threads:[~2012-08-23 12:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 7:53 agent
2012-08-23 9:23 ` Szabolcs Nagy
2012-08-23 10:25 ` agent
2012-08-23 12:24 ` Rich Felker
2012-08-23 13:11 ` agent
2012-08-23 13:56 ` John Spencer
2012-08-23 14:42 ` Szabolcs Nagy
2012-08-23 15:12 ` agent
2012-08-23 17:55 ` Rich Felker
2012-08-24 5:58 ` agent
2012-08-24 6:06 ` Rich Felker
2012-08-24 10:37 ` agent
2012-08-24 11:01 ` Szabolcs Nagy
2012-08-24 12:22 ` agent
2012-08-24 12:35 ` Rich Felker
2012-08-24 12:39 ` agent
2012-08-24 14:59 ` Szabolcs Nagy
2012-08-24 17:51 ` Rich Felker
2012-08-24 18:55 ` agent
2012-08-24 19:04 ` Szabolcs Nagy
2012-08-25 0:09 ` Rich Felker
2012-08-25 5:57 ` agent
2012-08-25 8:03 ` Szabolcs Nagy
2012-08-29 16:21 ` agent
2012-08-29 16:59 ` Rich Felker
2012-08-29 17:50 ` agent
2012-08-24 17:37 ` Luca Barbato
2012-08-24 17:52 ` Rich Felker
2012-08-23 12:24 ` John Spencer [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=503620F1.7010003@barfooze.de \
--to=maillist-musl@barfooze.de \
--cc=musl@lists.openwall.com \
--cc=rich@pennware.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).