From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6288 Path: news.gmane.org!not-for-mail From: Samuel Holland Newsgroups: gmane.linux.lib.musl.general Subject: Re: libgcc errors Date: Thu, 09 Oct 2014 21:43:34 +0000 Message-ID: References: <20141007195156.GV21835@port70.net> <5434704E.8080504@sholland.net> <54367BF6.80203@bradfordembedded.com> <263E3217-740D-44F2-BC2A-BDCA4AFB38B8@sholland.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1412891035 29461 80.91.229.3 (9 Oct 2014 21:43:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 9 Oct 2014 21:43:55 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6301-gllmg-musl=m.gmane.org@lists.openwall.com Thu Oct 09 23:43:50 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1XcLUz-0005tX-KS for gllmg-musl@plane.gmane.org; Thu, 09 Oct 2014 23:43:49 +0200 Original-Received: (qmail 3159 invoked by uid 550); 9 Oct 2014 21:43:48 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 3149 invoked from network); 9 Oct 2014 21:43:48 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sholland.net; s=key1; t=1412890978; bh=Wzk9tp1SdvvSdQloHZnxbjYrKe8MCt6H4pXjkiNFx9k=; h=In-Reply-To:References:Subject:From:Date:To; b=F2zK+P0NHyKdx6a9KKQXxUDfo7khg+3vvwVWcaYvuVDBIAjY85TJZ+PJ8d82PwHZ3 03ssCL83MIOdkFHHyHgFV+U8yLsbDrix5jgArYiW+8qA34c9Q0761jBiklT6j4Pegl 3WaOTnV4oMIsnU8wPJ72c4Lv6HPFSG6ObTwiCQTs= In-Reply-To: Xref: news.gmane.org gmane.linux.lib.musl.general:6288 Archived-At: On October 9, 2014 4:08:35 PM CDT, stephen Turner 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 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. >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. -- Regards, Samuel Holland