unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH v2 0/4] Add GCC cross compiler for arm-none-eabi.
Date: Thu, 29 Sep 2016 11:24:28 +0200	[thread overview]
Message-ID: <878tubt5xd.fsf@mdc-berlin.de> (raw)
In-Reply-To: <87d1jp90l6.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Hi Theodoros,
>
> Theodoros Foradis <theodoros.for@openmailbox.org> skribis:
>
>> The original patch series was working correctly and producing working binaries. Some
>> flags (that I had been using with 6.2.0) are missing from that version of GCC 4.9,
>> so I added 6.2.0 as an extra option. I have tested it to produce working binaries.
>>
>> Here are some modifications to Ricardo's patches for the arm-none-eabi
>> bare metal cross compiler. The following changes have been made:
>>
>> - I have modified xbinutils to use binutils 2.25.1 from cross-base, as it compiles
>> correctly with it. The version from the svn commit that was used by Ricardo is compiling
>> correct binaries as well. Thus, if it is deemed appropriate, the source for xbinutils can
>> be swapped for the previous one, with (seemingly) no difference.
>>
>> - The xgcc of the original, was failing to find the headers that newlib provided.
>> I have set the native-cross-paths as a workaround. Not sure if there is a better
>> alternative, or if the failure was my mistake.
>>
>> - A package for cross GCC 6.2.0 is added, with appropriate patches for multilib
>> support.
>>
>> - Newlib-arm-none-eabi and newlib-nano-arm-none-eabi have been changed to
>> procedures, taking an xgcc as argument, so as to facilitate building with
>> either version of gcc.
>>
>> - An arm-none-eabi-toolchain procedure is declared, to create toolchain packages
>> for both gcc and newlib version. The four toolchain variables follow. Not sure
>> if it's a mistake to include "nano" in the toolchain version.
>
> This all sounds reasonable to me.  Ricardo was interested in using this
> toolchain for one specific purpose, so maybe we’ll want to check that it
> also works here.  Ricardo: could you comment?

The changes seem reasonable.  I wasn’t happy with using fixed SVN
revisions in my patches, so I’m glad that this can be avoided.

I haven’t yet found the time to apply the proposed changes, build the
toolchain and try it with the Axoloti board.  I hope I’ll be able try on
Sunday to first address your comments, Ludo.  Then I’ll check the
suggested changes made by Theodoros (e.g. using different binutils and
doing without SVN).

Theodoros, I see that your patch set includes some of my patches as
well.  The only changes I can see is the addition of the native search
paths and parameterising newlib with xgcc, both of which I’ll add.
After applying my modified patches I would apply your patches that add
“arm-none-eabi-gcc-6” and the “arm-none-eabi-toolchain”.

Is this acceptable?

~~ Ricardo

  reply	other threads:[~2016-09-29  9:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-18  6:35 [PATCH 0/3] Add GCC cross compiler for arm-none-eabi Ricardo Wurmus
2016-09-18  6:35 ` [PATCH 1/3] gnu: Add arm-none-eabi cross compiler Ricardo Wurmus
2016-09-21  8:34   ` Ludovic Courtès
2016-09-18  6:35 ` [PATCH 2/3] gnu: Add newlib-arm-none-eabi Ricardo Wurmus
2016-09-21  8:38   ` Ludovic Courtès
2016-09-18  6:35 ` [PATCH 3/3] gnu: Add newlib-nano-arm-none-eabi Ricardo Wurmus
2016-09-21  8:40   ` Ludovic Courtès
2016-10-02 18:47     ` Ricardo Wurmus
2016-09-19 20:23 ` [PATCH v2 0/4] Add GCC cross compiler for arm-none-eabi Theodoros Foradis
2016-09-19 20:23   ` [PATCH v2 1/4] gnu: Add arm-none-eabi cross compiler Theodoros Foradis
2016-09-19 20:23   ` [PATCH v2 2/4] gnu: Add arm-none-eabi-gcc-6 and patches Theodoros Foradis
2016-10-10 20:22     ` Ricardo Wurmus
2016-09-19 20:23   ` [PATCH v2 3/4] gnu: Add newlib-arm-none-eabi Theodoros Foradis
2016-09-19 20:23   ` [PATCH v2 4/4] gnu: Add arm-none-eabi-toolchain Theodoros Foradis
2016-09-27  9:03   ` [PATCH v2 0/4] Add GCC cross compiler for arm-none-eabi Ludovic Courtès
2016-09-29  9:24     ` Ricardo Wurmus [this message]
2016-09-29 17:39       ` Theodoros Foradis
2016-10-10 18:09       ` Theodoros Foradis
2016-10-10 18:23         ` Ricardo Wurmus
2016-10-11 15:50           ` theodoros.for
2016-10-16 10:01           ` Ricardo Wurmus
2016-10-23 17:01             ` Theodoros Foradis
2016-11-26  8:55               ` Ricardo Wurmus
2016-09-20 10:50 ` [PATCH v2 0/1] " Theodoros Foradis
2016-09-20 10:50   ` [PATCH v2 1/4] gnu: Add arm-none-eabi cross compiler Theodoros Foradis
2016-09-20 10:50   ` [PATCH v2 2/4] gnu: Add arm-none-eabi-gcc-6 and patches Theodoros Foradis
2016-09-20 10:50   ` [PATCH v2 3/4] gnu: Add newlib-arm-none-eabi Theodoros Foradis
2016-09-20 10:50   ` [PATCH v2 4/4] gnu: Add arm-none-eabi-toolchain Theodoros Foradis
2016-09-21  8:30 ` [PATCH 0/3] Add GCC cross compiler for arm-none-eabi Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878tubt5xd.fsf@mdc-berlin.de \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).