Mail Archives: cygwin/2000/07/26/20:06:07
> There is no way to build everything at once. That is not the way that
> the distribution was made. You've probably seen individual announcments
> for individual packages, i.e., each piece was built individually.
>
> Some pieces may fit together, like you may be able to drop gcc, gdb,
> binutils, fileutils, and winsup into a directory and type
> 'configure/make' but you're going to run into problems because of the
> various versions of Makefile.in, libiberty, and other common files and
> directories that will be found in each directory.
>
> >All I really want is the equivelent instructions found in the FAQ for
> >b20.1 for rebuilding the tools. Also links to get the tex2html and
> >other tools which some of the packages need in order to do make install
> >and so fourth.
>
> The instructions are still generally correct for GNU packages. Since
> we're now including more stuff than the B20.1 net release and we
> are no longer doing monolithic releases, there is no longer a
> "one size fits all" set of instructions for rebuilding.
>
> As far as finding tools, I'd suggest looking at ftp.gnu.org and
> http://www.freshmeat.net/ .
>
> >The simple and straightforward instuctions for compiling and setting up
> >everything. BTW does the "latest" directory even get a version number?
>
> There are no simple instructions possible. Sorry.
>
> I don't know what you are referring to about latest but if you are asking
> if the latest directory is somehow cygwin "B23" then the answer is "no".
> We abandoned the monolithic versioning scheme several months ago. The
> cygwin DLL is version 1.1.2 (soon to be 1.1.3). All of the other packages
> have their own version numbers.
>
> (FAQ ALERT)
Indeed you should add this information to the FAQ. I am satisfied
now. I was just wondering if I was making it harder than it was
since 20.1 was monolithic.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -