On Mon, 09 Jun 2008 21:54:56 -0500, Dave Uhring wrote:
> On Mon, 09 Jun 2008 18:25:38 -0700, AGT wrote:
>> On Mon, 09 Jun 2008 15:42:20 -0500, Dave Uhring wrote:
>> Anyway I guess my point is that you have to be prepared for all kinds of
>> nonsense with this "configure" rubbish. But anyone working with GNU stuff
>> on Solaris knows this already.
> Normally the GNU autoconf generated configure scripts are pretty well
> behaved and produce usable Makefiles and config.h. Version 4 of gcc is
> anything but well behaved.

WHICH autoconf? : > Lest we forget that 'developers' quite often
make that a prerequisite as well : < Anyway there is no such thing as
normal with this stuff. But sometimes we get lucky and configure 'just
works'

>> Hours have passed and Im now at a c++ 32 bit shared build stage.. So
>> setting LDFLAGS turned the trick it seems. So far.
>
> You may yet find a problem in building libstdc++ when the build produces
> 64 bit objects but expects to link them with 32 bit objects.

Didnt happen : >
I could try compiling openssh in 64 bit to see if 64 bit
works at ALL. Im not terribly hopeful. But I suppose
I should take a run at building an x86 version before I go there..

> I did try building gcc-4 only as an exercise. The GNU compiler which
> ships with Solaris is quite adequate for building even the latest version
> of the qt library, KDE and everything else which I wanted available and
> which would not build with Studio12. qt will build with Studio12 but KDE
> pukes with Sun's compiler.

Agreed - sometimes the code is so BAD only gcc will compile it : >