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 18:10:21 +0200	[thread overview]
Message-ID: <20141001161020.GO21835@port70.net> (raw)
In-Reply-To: <CAA7aPHi0toKpKg=SRkJT0xBkUk=oW5ngUK8Tm36BRE4oEtpeUA@mail.gmail.com>

* stephen Turner <stephen.n.turner@gmail.com> [2014-10-01 11:37:22 -0400]:
> Im having a really hard time getting this working correctly. Long story
> short i have probobly made every mistake possible but now i have a system
> with busybox, make, bash, musl (no wrapper) 3.2 headers (using 3.2 debian
> kernel) and a patched binutils-2.24 and gcc-4.6.4 (with math libs)
> 
> I compile everything static and use the musl-gcc wrapper installed on by
> host system to compile binutils and gcc. everything runs in the target
> system but i get a error when running configure that talks about the a.out
> file is not executable and gcc cannot compile programs (it does make the
> a.out file though it just cant run)
> 

do you have a static linked gcc with musl support on the target?
does the configure script run on the target?
you need to be more clear and provide more information like:

- can gcc compile a minimal program (empty main)?
- where does gcc/ld fail, how were they invoked (gcc -v)?
- in the executable is the loader properly set up (readelf)?
- check if the loader/libc at the right path
- can you run the executable with the loader explicitly?
- strace the executable, where does it fail?

> would this be an issue with my headers/libs or binutils/gcc ?
> 
> The end goal here is to create the most vanilla system possible that can
> dynamically use musl. albiet ive chosen some rather un-vanilla programs for
> the base.


  reply	other threads:[~2014-10-01 16:10 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 [this message]
2014-10-01 17:54   ` stephen Turner
2014-10-01 18:13     ` Szabolcs Nagy
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=20141001161020.GO21835@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).