mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: build musl with clang
Date: Thu, 23 Aug 2012 08:24:15 -0400	[thread overview]
Message-ID: <20120823122414.GM27715@brightrain.aerifal.cx> (raw)
In-Reply-To: <5035E16E.50004@gmail.com>

On Thu, Aug 23, 2012 at 01:53:18PM +0600, agent wrote:
> i am trying to build musl with clang 3.0 from ubuntu 12.04. musl
> itself builds fairly fine with some notes on unused command line
> parameters and coding style. but i have some issues compiling a
> simple hello world program against this musl. the code is:
> 
> #include <stdio.h>
> 
> int main(int argc, char **argv) {
>     printf("Hello, World!\n");
>     return 0;
> }
> 
> i have tried to link against musl both dynamically and statically.
> if i compile a program with the default ld-linux.so dynamic linker
> the program runs but fails at the end:

This usage is not intended to work. At present it might be possible to
make it work for programs that don't use dlopen or TLS (which isn't
supported yet anyway), 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.

> (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

Did you change the options musl was compiled/linked with? Naively, my
first guess is that -Bsymbolic-functions was omitted.

Rich


  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 [this message]
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

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=20120823122414.GM27715@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).