From: "Andrew Crabtree" <andrewc AT rosemail DOT rose DOT hp DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Any luck builing libg++-2.8.0 or libstdg++-2.8.0 ??
Date: Fri, 30 Jan 1998 09:25:06 -0800
Organization: Hewlett Packard
Lines: 36
Message-ID: <6at2dj$dsm$1@rosenews.rose.hp.com>
References: <34D0B775 DOT 15F21D45 AT no DOT spam DOT mcs DOT nl> <6aqghk$s16$1 AT rosenews DOT rose DOT hp DOT com> <34D20172 DOT 369E5D09 AT no DOT spam DOT mcs DOT nl>
NNTP-Posting-Host: ros51675cra.rose.hp.com
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk


>> you could download pg++ 1.0.1 from www.goof.com, it comes with
>> which should be identical to the ones gcc 2.8 provides.
>pg++ probably has pentium compiled libīs and as i don't have a pentium
>this might not be such a good idea :)....

Not really.  Everything I provide is compiled with only -O2 enabled, which
means it is basically the same optimization that stock gcc 2.8 will provide.
This is to make sure that no screwy optimization bugs get into the resultant
compiler or libs.  Probably easiest if you just grab these.  Especially with
an official DJ 2.8 release due in the next month or so.

>bash$ ./djconfig.sh
>Configuring for a i386-pc-msdosdjgpp host.
>*** This configuration is not supported in the following subdirectories:
>     texinfo

I wasn't aware that changes to support this target had been send in.  Is it
possible that some directories
still have the old config info (i386-go32-msdos), so that is why the target
is not found.

>Configure in /gnu/obj/libiberty failed, exiting.

>I can build libiberty.a manually by renaming/copying alloca_manu.h to
>alloca_manual.h and then run configure.bat and then make it... it
>works... but doesn't seem to help when I rerun djconfig.sh...
>So I'm not really anywhere yet..
Yuck.  This is why I compile everything on a unix system.  I have found it
easier to build a cross-compiler or
bootstrap a compiler than it is to get the scripts to work on a dos machine.
I suppose you could try
deleting the directories that configure is having a problem in (libibert), I
don't think its needed if you are just building the c++ lib.  I typically do
this with the fortran and obj-c directories so they don't break configure.