From: ludo@gnu.org (Ludovic Courtès)
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: avr-gcc
Date: Fri, 20 Nov 2015 15:20:26 +0100 [thread overview]
Message-ID: <87ziy8g3bp.fsf@gnu.org> (raw)
In-Reply-To: <CAJ=RwfYYA5P-JymwM_J1gfq4dSikZLhM1hggo33pixrAj+msqw@mail.gmail.com> (David Thompson's message of "Wed, 18 Nov 2015 20:54:23 -0500")
"Thompson, David" <dthompson2@worcester.edu> skribis:
> Not quite. The avr-gcc build only provides a single version of
> libgcc.a, whereas Debian's avr-gcc provides a separate libgcc.a for
> each supported AVR family (avr2, avr3, avr35, etc.) Mark thought it
> might be the fault of the --disable-multilib configure flag, so I
> removed it but it didn't solve anything. I'm not sure what to do now.
> I have no idea what flag or patch could be signalling to the gcc build
> system that it shouldn't try to compile libraries for all of the
> various AVR models.
Are you sure the removal of --disable-multilib was effective?
Otherwise no specific idea. :-/ We’ll have to thoroughly study the
(avr-)gcc doc.
Ludo’.
next prev parent reply other threads:[~2015-11-20 14:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 15:25 avr-gcc Ricardo Wurmus
2015-11-17 15:59 ` avr-gcc Ricardo Wurmus
2015-11-17 21:32 ` avr-gcc Ludovic Courtès
2015-11-18 3:53 ` avr-gcc Thompson, David
2015-11-18 11:03 ` avr-gcc Ludovic Courtès
2015-11-19 1:54 ` avr-gcc Thompson, David
2015-11-20 14:20 ` Ludovic Courtès [this message]
2016-04-12 18:21 ` avr-gcc Thompson, David
2016-04-12 20:14 ` avr-gcc Thompson, David
2016-04-13 20:42 ` avr-gcc Ludovic Courtès
2016-04-14 5:47 ` avr-gcc Jan Nieuwenhuizen
2016-04-14 16:47 ` avr-gcc Ludovic Courtès
2016-04-15 8:09 ` avr-gcc Jan Nieuwenhuizen
2016-04-15 9:01 ` avr-gcc Andy Wingo
2016-04-15 12:44 ` avr-gcc Jan Nieuwenhuizen
2016-04-15 13:13 ` avr-gcc Andy Wingo
2016-04-15 21:06 ` avr-gcc Ludovic Courtès
2016-04-15 21:10 ` avr-gcc Ludovic Courtès
2016-04-16 19:55 ` avr-gcc Jan Nieuwenhuizen
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=87ziy8g3bp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@gnu.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.