Hi Theodoros,

Theodoros Foradis <theodoros....@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?

FWIW I had commented on Ricardo’s patch series here:

  https://lists.gnu.org/archive/html/guix-devel/2016-09/msg01379.html

> This is the first patch that I send in guix-devel, so please bear with me.

Welcome!  Sorry that it already took a bit long, but hopefully we’ll
converge real soon!  :-)

Thanks,
Ludo’.

Reply via email to