This is the mail archive of the
mailing list for the GCC project.
Re: Cygwin x86_64 support for GCC 4.8.x
- From: Kai Tietz <ktietz70 at googlemail dot com>
- To: Vasili Galka <vvv444 at gmail dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Sat, 7 Sep 2013 21:07:33 +0200
- Subject: Re: Cygwin x86_64 support for GCC 4.8.x
- Authentication-results: sourceware.org; auth=none
- References: <CA+gZxsMjWn_Sg3FMF_XTPK-mjnHWBzvDb4XqXAyd0mt3+gtSxg at mail dot gmail dot com> <CAEwic4Z57X4QqS6f5qtN9Gbr_jzOo=jn0VfX6OruRvr8666JGA at mail dot gmail dot com> <CA+gZxsMHh7RpdTUrhR1anAdoCZQwsJyT_2v+OrdkbWcQE5HLbw at mail dot gmail dot com>
2013/9/7 Vasili Galka <email@example.com>:
> Hi Kai,
> I see. My apologies, I'm not familiar with the GCC merging policy.
> In any case, where does GCC document the list of supported
> target/host/build configurations?
> I was trying to build GCC 4.8.1 with following configuration: HOST &
> BUILD: Cygwin 64bit, TARGET=arm-none-eabi
> I ended up with successful build/install that generated runtime errors
> which I had to investigate (while same on Cygwin 32 was fine).
> So it shall be either documented that such configuration is not
> supported or (better) it shall generate a warning/error at configure stage.
Why so? A target is supported when it gets mentioned in
release-notes. The gcc 4.8.x doesn't support that target. There is
the 4.8.x version cygwin uses for building cygwin 64-bit. The used
gcc version is locally patched. You can get those patches (actual
back-merge of changes already applied to trunk plus some additions
AFAIK) by the cygwin-folk directly.