building gcc under redhat cygwin

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Hi, I don't think that it is necessary to add any further information. The
problem is quite clearly defined.
On 3 Jan 2016 08:22, "Launchpad Janitor" <
<email address hidden>> wrote:

> Your question #279606 on GCC ARM Embedded changed:
> https://answers.launchpad.net/gcc-arm-embedded/+question/279606
>
> Status: Open => Expired
>
> Launchpad Janitor expired the question:
> This question was expired because it remained in the 'Open' state
> without activity for the last 15 days.
>
> --
> If you're still having this problem, you can reopen your question either
> by replying to this email or by going to the following page and
> entering more information about your problem:
> https://answers.launchpad.net/gcc-arm-embedded/+question/279606
>
> You received this question notification because you asked the question.
>

Hi Kirem,

"I understand that the scripts provided to build gcc are only compatible ubuntu.

I am trying to cross compile gcc for windows.

As there is a distribution for windows would it be possible to make the build script available?"

We use the provided buildscript to cross compile gcc for windows, this will always happen as long as you __DO_NOT__ pass --skip_steps=mingw32.

As for your error, could you post the full build log and the scripts you used to build it? As is I do not have enough information to provide you with useful help.

I have never attempted to build our toolchain on a redhat distribution before. Have you tried using the provided build scripts? You will need to install the dependencies noted on the How-to-build-toolchain.pdf(section 1.2.3), though you will need to use the Redhat Package Manager (RPM) instead of apt-get for this.

The error you get is expecting arm-none-eabi-gcc to be built somewhere and reachable by PATH, I suspect this might be during some library construction phase or something of the sorts, but the current information is not enough for us to help you figure out where the build is going wrong.

Cheers,
Andre

Hi Kirem,

This is caused by the following line in gcc/Makefile.in in the gcc source:

$(GCC_FOR_TARGET) -dumpspecs > specs

replacing $(GCC_FOR_TARGET) by ./xgcc should work but I'm not yet sure of the consequence of doing so. We'll keep you posted.

Best regards.

I think a safer change would rather be to edit build-toolchain.sh and change the definition of the *_FOR_TARGET variable in Task IV-3 to the following:

saveenvvar AR_FOR_TARGET $INSTALLDIR_MINGW/bin/$TARGET-ar
and same for the other macros.

Best regards.

Hi again,

Looking into build-toolchain.sh a bit deeper I noticed that the toolchain should be in the PATH as a result of prepend_path at the beginning of Task IV-1. Therefore there shouldn't be a need to touch the *_FOR_TARGET macro. Could you give us the full log (compressed to save space) of build-toolchain.sh run?

Best regards.

Hi Guys,

Thanks for the input so far. Please see the files here:

https://drive.google.com/folderview?id=0B3SKPqIM-IKDeVZOaXVOc2R5ajQ&usp=sharing

I found the build script provided to complicated to understand, so I attempted to make a build script.

I would appreciate any analysis of the buildlog.

Best Regards, Kirem

Hi Thomas,
Thanks for the reply, I will try your suggestions.

Thanks Thomas Preud'homme, that solved my question.

I have the same problem with my cygwin installation using the original build script. The script fials with the same error message during task [III-1]. As I understand correctly in this stage of the build the arm-none-eabi-gcc is not present yet (it cannot be found in the folder install-native/bin).
Why is the Makefile calling an executable it does not have yet? Available is the xgcc executable in the folder build-native/gcc-first/gcc.