From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: gcc-static: Remove -lgcc_s from GNU_USER_TARGET_LIB_SPEC
Date: Wed, 07 Jan 2015 18:15:55 +0100 [thread overview]
Message-ID: <87egr64ilw.fsf@gnu.org> (raw)
In-Reply-To: <87k30y1uca.fsf_-_@netris.org> (Mark H. Weaver's message of "Wed, 07 Jan 2015 10:30:45 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> Here's my proposed patch to fix our generated bootstrap gcc to not try
> to link with the nonexistent -lgcc_s. I used this to create the current
> set of 'armhf-linux' bootstrap tarballs and to bootstrap my initial
> system (including 'emacs').
>
> What do you think?
I looks like the right thing to do at the moment. Can you apply it to
core-updates?
I’ll look at the other patches from wip-armhf that we can include.
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-01-07 17:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 17:31 Preliminary 'wip-armhf' branch pushed Mark H Weaver
2014-12-31 17:47 ` John Darrington
2014-12-31 19:23 ` Mark H Weaver
2014-12-31 20:20 ` John Darrington
2014-12-31 23:40 ` Mark H Weaver
2015-01-01 6:14 ` John Darrington
2015-01-01 7:11 ` Mark H Weaver
2015-01-01 7:24 ` John Darrington
2015-01-01 18:22 ` Mark H Weaver
2015-01-01 19:04 ` John Darrington
2015-01-02 20:48 ` Ludovic Courtès
2015-01-02 22:07 ` Mark H Weaver
2015-01-03 19:07 ` Ludovic Courtès
2014-12-31 22:24 ` Mark H Weaver
2014-12-31 22:55 ` Mark H Weaver
2015-01-01 18:53 ` Problem with natively-built armhf bootstrap compiler Mark H Weaver
2015-01-02 2:19 ` Mark H Weaver
2015-01-02 4:56 ` Mark H Weaver
2015-01-02 21:06 ` Ludovic Courtès
2015-01-03 18:37 ` Mark H Weaver
2015-01-07 13:15 ` Ludovic Courtès
2015-01-07 15:15 ` Mark H Weaver
2015-01-07 15:30 ` [PATCH] gnu: gcc-static: Remove -lgcc_s from GNU_USER_TARGET_LIB_SPEC Mark H Weaver
2015-01-07 17:15 ` Ludovic Courtès [this message]
2015-01-02 20:45 ` Preliminary 'wip-armhf' branch pushed Ludovic Courtès
2015-01-03 18:49 ` Mark H Weaver
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=87egr64ilw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.