mailing list of musl libc
 help / color / mirror / code / Atom feed
From: stephen Turner <stephen.n.turner@gmail.com>
To: musl@lists.openwall.com
Subject: Re: converting gcc from glibc to musl
Date: Thu, 2 Oct 2014 18:40:49 -0400	[thread overview]
Message-ID: <CAA7aPHgyaTU37PqYZsWwqCy6JuGbn26Bw3P1x+aDnE2ceVoiKw@mail.gmail.com> (raw)
In-Reply-To: <568b5df17f2616f03b76474101240cbe@mail.sholland.net>

[-- Attachment #1: Type: text/plain, Size: 1642 bytes --]

Gcc is dying with /bin/bash i686-linux-musl-gcc command not found about
half to 3/4 way through build.  I know this is not enough info to help
diagnose the issue but unlike errors during config, its not pointing me to
a compile error log. I will be more than happy to provide anything you need
just let me know what that is.

thanks for your help.

On Thu, Oct 2, 2014 at 4:47 PM, Samuel Holland <samuel@sholland.net> wrote:

> On 2014-10-02 15:31, stephen Turner wrote:
>
>> since patching with the recommended patch (the one i had wasnt a full
>> patch
>> apparently) i have been able to use this option --host=i686-linux-musl
>> however now when i compile i run into new issues.
>>
>> Firstly gmp, mpfr, and mpc do not like this flag obviously since they do
>> not have the musl settings patched in so i cant compile with the musl
>> wrapper because i cannot include those math libraries and when i try to
>> prebuild them and use the flag --with-mpfr=/target/location it errors out
>> saying it cant find any compatible versions of these libs/headers.
>>
>
> Overriding the host is really only necessary for a few programs like gcc.
> Most
> will work fine with musl, even though they detect your system as
> "i686-pc-linux-gnu".
> That said, if you want to use --host on all of your programs, all you need
> is a
> patch like the one here[0]. There are four or five different variations of
> the patch
> though, depending on what version/configuration of autotools the project
> uses.
>
> [0] https://github.com/smaeul/starch/blob/master/pkgbuilds/
> libmpfr/libmpfr-musl.patch
>
> --
> Regards,
> Samuel Holland <samuel@sholland.net>
>

[-- Attachment #2: Type: text/html, Size: 2317 bytes --]

  reply	other threads:[~2014-10-02 22:40 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
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 [this message]
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=CAA7aPHgyaTU37PqYZsWwqCy6JuGbn26Bw3P1x+aDnE2ceVoiKw@mail.gmail.com \
    --to=stephen.n.turner@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).