mailing list of musl libc
 help / color / mirror / code / Atom feed
From: agent <agentprog@gmail.com>
To: musl@lists.openwall.com
Subject: Re: build musl with clang
Date: Thu, 23 Aug 2012 19:11:53 +0600	[thread overview]
Message-ID: <50362C19.5080509@gmail.com> (raw)
In-Reply-To: <20120823122414.GM27715@brightrain.aerifal.cx>

23.08.2012 18:24, Rich Felker пишет:
> but in the long term I think using the GNU dynamic linker is going to 
> get more and more unrealistic, so it's probably best not to even try. 
i didn't want to, at first i missed -dynamic-linker option and it was 
the only somehow working variant.
> Did you change the options musl was compiled/linked with? Naively, my
> first guess is that -Bsymbolic-functions was omitted.
i was using

CC=clang ./configure --prefix=...

and other things were default. no changes to any files.

23.08.2012 18:24, John Spencer пишет:
> 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
i didn't use any build systems, just a shell script with commands. that 
was just a hello world. i was able to compile it and if i encounter any 
problems in future, i'll try the solution from FAQ.
btw, there was no link to this wiki from main site
> 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.
i was investigating the possibility of using clang + musl for writing a 
new program, not for porting existing software, so it may be possible to 
avoid using some functions in reasonable scale, or change any component 
in this bundle.
and does that bug affect a whole *alloc family or just calloc?



  reply	other threads:[~2012-08-23 13:11 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 [this message]
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

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=50362C19.5080509@gmail.com \
    --to=agentprog@gmail.com \
    --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).