crossbuild cygwin-1.7.6-1 on linux x64
Thu Aug 26 12:50:00 GMT 2010
> On Wed, Aug 25, 2010 at 06:30:15PM -0400, Charles Wilson wrote:
>>Well, that's what I thought, too, since I've built them for other
>>$targets many times, with no problems. But...for whatever reason...it
>>seems that cygwin is, as usual, special. :-(
> Even though it began its life beinb built solely as a cross-build
> environment and was meant to be cross-compiled even without a sysroot...
At the risk of extending this thread, on the wrong list...
I have only tried to build a working toolchain and hello world. And
libtool, to exercise its new cross support, which was the reason I'm
even doing this at all -- since in 18 months nobody who DOES have a
working linux->cygwin toolchain ever responded to my call for test:
[CFT] libtool on nix->cygwin cross, with wine
(Don't bother now; I did at least discover that wine+cygwin-1.7
is...problematic, at best. Even little old cygpath segfaults.)
I haven't even attempted to use my borked cross compiler to build the
cygwin dll itself. When I said it appears cygwin is "special", I meant
that something seems to be trickier than usual when trying to build a
working crossgcc for cygwin as a $target, as opposed to some other $target.
Yes, I know that cygwin was originally developed using a cross compiler,
and you guys routinely build it and other official cygwin packages that
way even today. OBVIOUSLY that means it is possible to build a working
crossgcc for target=cygwin.
That's why it is kinda surprising that (a) there is apparently no
documentation anywhere on how one should properly build such a
toolchain, (b) no existing downloadable version anywhere -- not even
from un-approved, non-cygwin.com sites, and (c) that the only responses
I've gotten on these two threads are from somebody else whose procedure
ALSO produces a broken toolchain, or metadiscussions like this subthread.
More information about the Cygwin-developers