Re: Problem building Cygwin from CVS

On 12/17/2012 4:53 AM, Corinna Vinschen wrote: Yes, don't try to build tcl/tk from the sourceware repo. It's old, it's unmaintained. Corinna Ok, thanks. Are there any other parts of the CVS source tree that I should be wary of? -- Chris J. Breisch -- Problem

Re: building cygwin from cvs

On Dec 17 11:00, marco atzeri wrote: > Corinna, > trying to build the cygwin dll from cvs with just > configure and build stop here : > > checking whether we are cross compiling... no > checking for suffix of object files... (cached) o > checking whether we are using the GNU C compiler... (cached)

building cygwin from cvs

Corinna, trying to build the cygwin dll from cvs with just configure and build stop here : checking whether we are cross compiling... no checking for suffix of object files... (cached) o checking whether we are using the GNU C compiler... (cached) yes checking whether gcc -L/pub/cygwin/cvs/build

Re: Problem building Cygwin from CVS

On Dec 15 15:20, Chris J. Breisch wrote: > I'm having difficulty building the Cygwin tree. My cygcheck.out is > attached. > > I have the "Default" Cygwin set up, with the following additions: > gcc4, make, perl, cocom, bison, flex, vim, m4, and libiconv. > > I've checked the archives for similar

Problem building Cygwin from CVS

I'm having difficulty building the Cygwin tree. My cygcheck.out is attached. I have the "Default" Cygwin set up, with the following additions: gcc4, make, perl, cocom, bison, flex, vim, m4, and libiconv. I've checked the archives for similar issues and have found none. After my research, it

Re: Building Cygwin from CVS

On Thu, Jan 26, 2006 at 09:52:34PM -0800, Joshua Daniel Franklin wrote: >On 1/26/06, Joshua Daniel Franklin wrote: >>OK, the full text of winsup/README is now: >> >>THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED >>WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRA

Re: Building Cygwin from CVS

On 1/26/06, Joshua Daniel Franklin wrote: > OK, the full text of winsup/README is now: > > THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR > IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED > WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. > > Cygwi

Re: Building Cygwin from CVS

On 1/26/06, Corinna Vinschen wrote: > On Jan 26 13:44, Christopher Faylor wrote: > > On Thu, Jan 26, 2006 at 10:12:07AM +0100, Corinna Vinschen wrote: > > >On Jan 25 20:41, Joshua Daniel Franklin wrote: > > >>I've added this info to > > >>http://cygwin.com/faq/faq.programming.html#faq.programming.b

Re: Building Cygwin from CVS

On Jan 26 13:44, Christopher Faylor wrote: > On Thu, Jan 26, 2006 at 10:12:07AM +0100, Corinna Vinschen wrote: > >On Jan 25 20:41, Joshua Daniel Franklin wrote: > >>I've added this info to > >>http://cygwin.com/faq/faq.programming.html#faq.programming.building-cygwin > >>and I'd like to put it in a

Re: Building Cygwin from CVS

On Thu, Jan 26, 2006 at 10:12:07AM +0100, Corinna Vinschen wrote: >On Jan 25 20:41, Joshua Daniel Franklin wrote: >>On 1/20/06, Brian Dessent wrote: >>>Joshua Daniel Franklin wrote: >>> gcc make binutils cocom dejagnu >>> >>>gcc depends on binutils, so there's no need to list it as requirement.

Re: Building Cygwin from CVS

On Jan 25 20:41, Joshua Daniel Franklin wrote: > On 1/20/06, Brian Dessent wrote: > > Joshua Daniel Franklin wrote: > > > > > gcc make binutils cocom dejagnu > > > > gcc depends on binutils, so there's no need to list it as requirement. > > Perl is used in the build process as well. > > > > http://

Re: Building Cygwin from CVS

On 1/20/06, Brian Dessent wrote: > Joshua Daniel Franklin wrote: > > > gcc make binutils cocom dejagnu > > gcc depends on binutils, so there's no need to list it as requirement. > Perl is used in the build process as well. > > http://cygwin.com/ml/cygwin/2005-01/msg01266.html Thanks Brian, I think

Re: Building Cygwin from CVS

Joshua Daniel Franklin wrote: > gcc make binutils cocom dejagnu gcc depends on binutils, so there's no need to list it as requirement. Perl is used in the build process as well. http://cygwin.com/ml/cygwin/2005-01/msg01266.html Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe

Re: Building Cygwin from CVS

On Fri, Jan 20, 2006 at 10:21:35AM +0100, Corinna Vinschen wrote: >On Jan 20 09:10, Cliff Hones wrote: >> Christopher Faylor wrote: >> > Before we do that can we please find out WHAT is actually wrong? There >> > is no description of the problem beyond the above. I run the testsuite >> > several

RE: Building Cygwin from CVS

Joshua Daniel Franklin wrote: > > I think I'd tried to come up with a list before but never figured it > out since I'd > long ago installed what was needed. Is this a complete enough list? > > gcc make binutils cocom dejagnu > > This might even be worth adding to a winsup/README file. I bel

Re: Building Cygwin from CVS

On Jan 20 09:10, Cliff Hones wrote: > Christopher Faylor wrote: > > Before we do that can we please find out WHAT is actually wrong? There > > is no description of the problem beyond the above. I run the testsuite > > several times a day by cd'ing to winsup/testsuite so I know that works. > > Let

Re: Building Cygwin from CVS

Christopher Faylor wrote: > On Thu, Jan 19, 2006 at 08:53:26PM -0800, Joshua Daniel Franklin wrote: > >>> . The FAQ info describing how to run the tests is wrong. It worked for >>>me when I ran "make check" in the i686-pc-cygwin/winsup subdirectory of >>>my build directory. >> >>OK, I'll

Re: Building Cygwin from CVS

On Thu, Jan 19, 2006 at 08:53:26PM -0800, Joshua Daniel Franklin wrote: >> . The FAQ info describing how to run the tests is wrong. It worked for >> me when I ran "make check" in the i686-pc-cygwin/winsup subdirectory of >> my build directory. > >OK, I'll fix that. Before we do that can

Re: Building Cygwin from CVS

On 1/18/06, Cliff Hones wrote: > It's rather a long time since I tried building my own cygwin from CVS. With > the new release out, I thought I'd give it a try, as I imagine HEAD is very > close to 1.5.19-2. I followed the instructions in the FAQ: > http://cygwin.com/faq/faq.programming.html

RE: Building Cygwin from CVS

Dave Korn wrote: > Hmm. My local copy of devices.cc regenerated itself today as well, > although I didn't notice it fly past in the build. Mystery solved. Cgf updated devices.h and regenerated devices.cc back in December, but overlooked doing the regenerate when he reverted the change the

RE: Building Cygwin from CVS

Brian Dessent wrote: > Cliff Hones wrote: > >> Well, maybe it is a timestamp problem, but the make did fail trying to >> regenerate devices.cc using the gendevices script. After I'd installed >> cocom it worked, and overwrote devices.cc in the src/winsup/cygwin >> directory. > > That does sound

Re: Building Cygwin from CVS

Cliff Hones wrote: > Well, maybe it is a timestamp problem, but the make did fail trying to > regenerate > devices.cc using the gendevices script. After I'd installed cocom it worked, > and overwrote devices.cc in the src/winsup/cygwin directory. That does sound like a timestamp issue then.

Re: Building Cygwin from CVS

Corinna Vinschen wrote: > Do you want to write a few words yourself and send an appropriate docs > patch to the cygwin-patches list? You know, http://cygwin.com/acronyms#PTC If anyone feels like rewording that section, it might be a good time to mention the peculiarities of the sourceware CVS mo

Re: Building Cygwin from CVS

Brian Dessent wrote: > Cliff Hones wrote: > >> . It would be useful to mention in the FAQ which packages need to be >> installed >>to perform the build. I expect everyone will realise make, gcc, binutils >> etc. >>are required, but I found I needed cocom (for shilka) which I'd not come

Re: Building Cygwin from CVS

Dave Korn wrote: > Cliff Hones wrote: > >> . When I ran the tests, I got five unexpected failures (devdsp, >>msgtest, pthread-cancel1, semtest and shmtest). Is this to >>be expected :-). > > Is the smiley there to indicate that you already understand perfectly well > that these tests

Re: Building Cygwin from CVS

Cliff Hones wrote: > . It would be useful to mention in the FAQ which packages need to be > installed > to perform the build. I expect everyone will realise make, gcc, binutils > etc. > are required, but I found I needed cocom (for shilka) which I'd not come > across > before, an

RE: Building Cygwin from CVS

Cliff Hones wrote: > > . When I ran the tests, I got five unexpected failures (devdsp, > msgtest, pthread-cancel1, semtest and shmtest). Is this to > be expected :-). Is the smiley there to indicate that you already understand perfectly well that these tests would require cygserver

Re: Building Cygwin from CVS

On Jan 18 18:28, Cliff Hones wrote: > It's rather a long time since I tried building my own cygwin from CVS. With > the new release out, I thought I'd give it a try, as I imagine HEAD is very > close to 1.5.19-2. I followed the instructions in the FAQ: > http://cygwin.com/faq/faq.programming.

Building Cygwin from CVS

It's rather a long time since I tried building my own cygwin from CVS. With the new release out, I thought I'd give it a try, as I imagine HEAD is very close to 1.5.19-2. I followed the instructions in the FAQ: http://cygwin.com/faq/faq.programming.html#faq.programming.building-cygwin A few