mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "writeonce@midipix.org" <writeonce@midipix.org>
To: musl@lists.openwall.com
Subject: Re: libgcc errors
Date: Thu, 09 Oct 2014 18:04:15 -0400	[thread overview]
Message-ID: <5437065F.8010702@midipix.org> (raw)
In-Reply-To: <F7A4EAAB-C958-41BC-804C-14E62C0DE3F8@sholland.net>

On 10/09/2014 05:43 PM, Samuel Holland wrote:
> On October 9, 2014 4:08:35 PM CDT, stephen Turner <stephen.n.turner@gmail.com> wrote:
>> Thanks Samuel,
>> I would use the musl-gcc wrapper (and have) however once gcc is compiled
> >from it then it does not support dynamic linking due to the lack of --host
>> (suggested) or --target (what seems more appropriate to me) specified in
>> the configure flags. If i do specify it then i get all kinds of crazy
>> errors

These errors are partly the result of how gcc passes environment 
variables to the configure scripts and make recipes in its 
sub-directories.  In cbb, such errors were the motivation for 1) not 
using musl-gcc directly, but rather passing -specs=$specs_file to the 
gcc configure script, and 2) using the $script_xgcc_for_specs 
environment variable, and applying the related patch to gcc's Makefile.in.

>> which is why i consulted this mailing list in the first place since
>> i have tried googling my way through documentation for a month prior to
>> asking for help.
> It took me an entire summer to figure this all out.

+1 :)

>> Its my inexperienced opinion that simply switching libs from glibc6 to musl
>> should be relatively easy compared to the full cross compile. To me it
>> seems like it would be as easy as specifying a new lib when rebuilding gcc
>> and that would be all.
> It would be that easy if everything was statically linked.
>
>> let me ask you one quick question. I went to the musl-cross website on
>> bitbucket/gregorr and grabbed the patch for 4.7.3, is that a good working
>> patch and gcc version? (all my errors seem to stem from compiling gcc) and
>> is there any special way to download it or just click the raw button and
>> wget the link  then "patch -Np1 -i file.name.diff"?
> That is the correct file, and there is no special way to download it. Those steps will work. Your problems are not caused by a bad patch, but pollution from your host libc and toolchain. Dynamic linking is hard to get rid of. (I'm trying to avoid a rant here...)
>
> If I might ask, what is your end goal? Maybe you'd have a better time starting with something like Alpine or Sabotage.
>



      parent reply	other threads:[~2014-10-09 22:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 18:54 stephen Turner
2014-10-07 19:51 ` Szabolcs Nagy
2014-10-07 21:32   ` stephen Turner
2014-10-07 22:59     ` Samuel Holland
2014-10-09 12:13       ` Andrew Bradford
2014-10-09 14:46         ` stephen Turner
2014-10-09 15:49           ` stephen Turner
2014-10-09 19:38         ` Samuel Holland
2014-10-09 21:08           ` stephen Turner
2014-10-09 21:43             ` Samuel Holland
2014-10-09 21:55               ` stephen Turner
2014-10-09 22:17                 ` stephen Turner
2014-10-10 21:01                   ` stephen Turner
2014-10-10 21:21                     ` Rich Felker
2014-10-10 21:28                       ` Samuel Holland
2014-10-10 21:30                     ` Samuel Holland
2014-10-16 17:35                       ` stephen Turner
2014-10-09 22:04               ` writeonce [this message]

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=5437065F.8010702@midipix.org \
    --to=writeonce@midipix.org \
    --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).