RE: when is next release of setup.exe

["linda w \(cyg\)" <cygwin at tlinx dot org>]

Compiling from a branch?  How did I manage that?
I just have 'gcc' downloaded -- If I install the gcc2 package will
the ./configure script just 'do the right thing' and select
the compiler it works with or will it just use 'gcc' and end up
using the current gcc?

Did I some how manage to download mismatched headers for the
compiler or something?

-l


> -----Original Message-----
> From: Pavel Tsekov [mailto:ptsekov at gmx dot net]
> Sent: Sat, Mar 08, 2003 1:48p
> To: linda w (cyg)
> Cc: cygwin-apps at cygwin dot com
> Subject: RE: when is next release of setup.exe
>
>
> You've obviously compiling from a branch. Branched setup is not
> gcc3 ready. Install gcc-2 package and use gcc-2 + g++-2 to compile
> setup.exe.
>
> On Sat, 8 Mar 2003, linda w (cyg) wrote:
>
> > > -----Original Message-----
> > > From:  Igor Pechtchanski
> >
> > > Cygwin setup compiles fine with Cygwin gcc.
> > ---
> > 	Pardon me, kind sir, but I have a "itty bitty teensie weensie"
> > problem with this:
> >
> > make  all-recursive
> > make[1]: Entering directory `/usr/src/setup-0'
> > Making all in bz2lib
> > make[2]: Entering directory `/usr/src/setup-0/bz2lib'
> > make[2]: Nothing to be done for `all'.
> > make[2]: Leaving directory `/usr/src/setup-0/bz2lib'
> > Making all in zlib
> > make[2]: Entering directory `/usr/src/setup-0/zlib'
> > make[2]: Nothing to be done for `all'.
> > make[2]: Leaving directory `/usr/src/setup-0/zlib'
> > Making all in libgetopt++
> > make[2]: Entering directory `/usr/src/setup-0/libgetopt++'
> > source='src/GetOption.cc' object='src/GetOption.lo' libtool=yes \
> > depfile='src/.deps/GetOption.Plo'
> tmpdepfile='src/.deps/GetOption.TPlo' \
> > depmode=gcc3 /bin/bash ./cfgaux/depcomp \
> > /bin/bash ./libtool --mode=compile g++ -DHAVE_CONFIG_H -I.
> -I. -I./include -I./i
> > nclude    -g -O2 -c -o src/GetOption.lo `test -f
> 'src/GetOption.cc' || echo './'
> > `src/GetOption.cc
> >  g++ -DHAVE_CONFIG_H -I. -I. -I./include -I./include -g -O2
> -c src/GetOption.cc
> > -MT src/GetOption.lo -MD -MP -MF src/.deps/GetOption.TPlo
> -DPIC -o src/.libs/Ge
> > tOption.o
> > In file included from include/getopt++/GetOption.h:19,
> >                  from src/GetOption.cc:19:
> > include/getopt++/OptionSet.h:31: `ostream' was not declared
> in this scope
> > include/getopt++/OptionSet.h:31: parse error before `)' token
> > In file included from src/GetOption.cc:20:
> > include/getopt++/Option.h:33: ISO C++ forbids declaration
> of `string' with no
> >    type
> > include/getopt++/Option.h:33: `string' declared as a `virtual' field
> > include/getopt++/Option.h:33: parse error before `const'
> > include/getopt++/Option.h:35: ISO C++ forbids declaration
> of `string' with no
> >    type
> > include/getopt++/Option.h:35: `string' declared as a `virtual' field
> > include/getopt++/Option.h:35: declaration of `int Option::string'
> > include/getopt++/Option.h:33: conflicts with previous
> declaration `int
> >    Option::string'
> > include/getopt++/Option.h:35: parse error before `const'
> > include/getopt++/Option.h:35: duplicate member `Option::string'
> > make[2]: *** [src/GetOption.lo] Error 1
> > make[2]: Leaving directory `/usr/src/setup-0/libgetopt++'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/usr/src/setup-0'
> > make: *** [all] Error 2
> >
> ==============================================================
> ============
> > Twas all so minorly amused by this discussion as I was
> just about to
> > ask if setup was supposed to be able to be compiled under cygwin.
> > I'm  using "setup-2.249.2.5.tar.bz2"....
> >
> > Not that I'm demanding anything, or anything, and not to be
> disagreeable
> > (though I'm often seen that way)...but could you give me any hints
> > as to why I'm unable to compile -- other than "well, you idjiot
> > (inflected form of idiot), it's obvious that you didn't
> declare ostream
> > in the proper scope!"...:-(.  Very sad.
> >
> > (*wry smile*)
> > -linda
> >
> >
> >
> >
>
>