Robert Eckhoff wrote on 08 April 2008 17:41:
> Below are the errors I received before I made their
> associated changes.
> Dave Korn wrote:
>> Robert Eckhoff wrote on 05 April 2008 22:39:
>>
>>
>>> directories. Winsup also had some source problems that I corrected.
>>>
>>> ~/cygwin-1.5.25-11/wi
Below are the errors I received before I made their associated changes.
Dave Korn wrote:
Robert Eckhoff wrote on 05 April 2008 22:39:
directories. Winsup also had some source problems that I corrected.
~/cygwin-1.5.25-11/winsup/cygwin/winsup.h:276
-extern bool wsock_started;
+extern "C" boo
Robert Eckhoff wrote on 05 April 2008 22:39:
> directories. Winsup also had some source problems that I corrected.
>
> ~/cygwin-1.5.25-11/winsup/cygwin/winsup.h:276
> -extern bool wsock_started;
> +extern "C" bool wsock_started;
>
> ~/cygwin-1.5.25-11/winsup/cygwin/winsup.h:156
> -extern int __a
On Sun, Apr 06, 2008 at 12:18:16PM -0700, Brian Dessent wrote:
>Chris Game wrote:
>>>I can assure you that many of us cross compile Cygwin on Linux
>>>regularly...
>>
>>Er, why?
>
>Because as I said it's significantly faster, and because the developers
>tend to have Linux machines around anyway bec
Chris Game wrote:
> > I can assure you that many of us cross compile Cygwin on Linux
> > regularly...
>
> Er, why?
Because as I said it's significantly faster, and because the developers
tend to have Linux machines around anyway because of
work/preference/etc.
Brian
--
Unsubscribe info: h
On Sat, 05 Apr 2008 00:29:06 -0700, Brian Dessent wrote:
> I can assure you that many of us cross compile Cygwin on Linux
> regularly...
Er, why?
--
Chris Game
If at first you don't succeed, call it version 1.0
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem report
Thanks again,
I managed to get clean cygwin binaries hosted by x86_64-linux using the
existing cygwin binaries (w/headers). Additional binaries, libiconv and
w32api, needed to be installed into the sysroot directory to get
compilation to work. Furthemore, w32api's libs and includes needed to be
Hi Brian,
Thank you for your help. I was waiting for someone to say, "what
you're doing is silly, here's how you do it." I really wanted to
bootstrap from scratch, hence the persistence. The amount of
documentation on linux embedded systems kept my hope up for cygwin.
Again, thanks
Robert Eckhoff wrote:
> /*rant
> I've been trying to boot strap a cygwin/gcc system for essentially 3
> weeks now. I am _frustrated_. I have copied files around, linked
> directories from gcc into cygwin, linked directories from cygwin into
> gcc. I have copied include files from various pla
Robert Eckhoff wrote:
> ~/build_cygwin$ export CC=i686-pc-cygwin-gcc
Don't set this. Leave CC set to the host, not target, compiler.
> ~/build_cygwin$ ~/cygwin-1.5.25-11/configure
> --prefix=/home/rpeckhoff/boot_system/ --host=i686-pc-cygwin
> --build=x86_64-unknown-linux-gnu -v
10 matches
Mail list logo
