mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Samuel Holland <samuel@sholland.net>
To: musl@lists.openwall.com
Subject: Re: libgcc errors
Date: Fri, 10 Oct 2014 21:28:39 +0000	[thread overview]
Message-ID: <895AC2B7-DB55-4384-BE00-4CA6C011810C@sholland.net> (raw)
In-Reply-To: <20141010212136.GC23797@brightrain.aerifal.cx>

On October 10, 2014 4:21:36 PM CDT, Rich Felker <dalias@libc.org> wrote:
>If you just use Gregor's scripts directly, everything should work
>fine. Have you tried just running the musl-cross build unchanged and
>seeing if it succeeds? This would tell you right away whether you have
>a problem with your build environment/packages, or with your own
>custom commands. Then, assuming it's the latter, you can try making
>controlled changes until you figure out what you're doing wrong.

I think he's got everything correct now. He's just missing telling musl where to find shared libs.

>Rich

-- 
Regards,
Samuel Holland <samuel@sholland.net>


  reply	other threads:[~2014-10-10 21:28 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 [this message]
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=895AC2B7-DB55-4384-BE00-4CA6C011810C@sholland.net \
    --to=samuel@sholland.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).