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: libgcc errors
Date: Thu, 9 Oct 2014 10:46:58 -0400	[thread overview]
Message-ID: <CAA7aPHic+msex0KR=59J7nxw7PvYiQ+bp_1r3utMGmMEXfPR1Q@mail.gmail.com> (raw)
In-Reply-To: <54367BF6.80203@bradfordembedded.com>

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

Would someone be so kind as to refer me to the preferred musl gcc patch
repository? I am having soo many difficulties that i'm inclined to believe
i'm missing something other than the commands here.

Currently i run into one of two issues, I use --target and receive errors
with libgcc  or i use --host and receive errors with libiberty.  I will be
starting over from scratch including the host system in an attempt to
ensure a clean build environment.

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

  reply	other threads:[~2014-10-09 14:46 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 [this message]
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

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='CAA7aPHic+msex0KR=59J7nxw7PvYiQ+bp_1r3utMGmMEXfPR1Q@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).