mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: converting gcc from glibc to musl
Date: Wed, 1 Oct 2014 20:13:56 +0200	[thread overview]
Message-ID: <20141001181356.GQ21835@port70.net> (raw)
In-Reply-To: <CAA7aPHj4dkTXeEJVZXz=pch=SqA181KA7w1mP9pE=Eov=ZOEew@mail.gmail.com>

* stephen Turner <stephen.n.turner@gmail.com> [2014-10-01 13:54:25 -0400]:
> On Wed, Oct 1, 2014 at 12:10 PM, Szabolcs Nagy <nsz@port70.net> wrote:
> > - can gcc compile a minimal program (empty main)?
> >
> 
> I can compile the following program sucessfully to a.out but cannot run it.
> 
> # include <stdio.h>
> main()
> {
> printf("hello world\n");
> }
> 
> gcc test.c && chmod +x a.out && ./a.out
> 
> 
> > - where does gcc/ld fail, how were they invoked (gcc -v)?
> 
> 
> configure:2078: loading cache /dev/null
...

i meant running

 gcc -v test.c

not the configure thing

(so we know if the compiler works at all before
starting to debug the configure script)

> - in the executable is the loader properly set up (readelf)?
> 

check if the machine type/abi is ok:

 readelf -h a.out

check if the musl loader is set up as expected:

 readelf -l a.out

(in case of dynamic linking the interpreter should be
/lib/ld-musl-ARCH.so.1 otherwise there should be no
interpreter)


> - check if the loader/libc at the right path
> 

ls -l /lib/ld-musl-*

> - can you run the executable with the loader explicitly?

run

/lib/ld-musl-ARCH.so.1 ./a.out

> > - strace the executable, where does it fail?

strace ./a.out

> 
> I dont know how to do what your asking here is there a site i can ref on
> these troubleshooting steps?

if you are not experienced with toolchains i'd try
alpine or sabotage linux first
you might be able to customize them to your liking


  reply	other threads:[~2014-10-01 18:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 15:37 stephen Turner
2014-10-01 16:10 ` Szabolcs Nagy
2014-10-01 17:54   ` stephen Turner
2014-10-01 18:13     ` Szabolcs Nagy [this message]
2014-10-01 19:11       ` stephen Turner
2014-10-01 20:44         ` Szabolcs Nagy
2014-10-01 19:00     ` Samuel Holland
2014-10-01 19:13       ` stephen Turner
2014-10-01 19:35         ` Samuel Holland
2014-10-01 19:44           ` stephen Turner
2014-10-01 20:17             ` Samuel Holland
2014-10-01 20:34               ` stephen Turner
2014-10-01 20:43                 ` stephen Turner
2014-10-01 20:54                 ` Samuel Holland
2014-10-02 20:31                   ` stephen Turner
2014-10-02 20:47                     ` Samuel Holland
2014-10-02 22:40                       ` stephen Turner
2014-10-03 13:51                         ` stephen Turner

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=20141001181356.GQ21835@port70.net \
    --to=nsz@port70.net \
    --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).