Re: Problem with configuring gstep-core010129

[Nicola Pero]

Hi - 

I'm sorry about the problems this is causing.

The packages are now *independent* - you can't build them any longer as a
big entity.

I modified the configure script in the top level directory to abort -
informing the user about this.  I also quickly updated GNUstep-HOWTO to
document the new installation procedure.

To make transition easier, I added a (trivial) shell script to the top
level directory - called `compile-all'.  This script will configure,
compile and install everything for you from the top level dir with a
single command - similar to what you did before with a single
`./configure; make; make install'.  But you need to be root.

So - please try either configuring, compiling and installing each package
in turn - or using the `compile-all' script in the top level directory.

Btw - do a `make distclean' in gui and xgps before compiling.

- now a longer explanation for those who wonder why this hard change we
necessary

We have decided to simplify the dependencies between the core packages -
and we have done it - we have heavily simplified these dependencies - I
know this was a hard change - but it will have lots of benefits in the
long run - first of all it makes binary packaging easy and that's a top
priority now.

The big benefit can be explained as - everything is simple and standard
now.

* configuration is much easier now - so we will spend less time into
makefiles and configuration scripts and have more time to look into the
code.  

* binary packaging is possible now without being hackers/shell masters -
it's not more difficult than packaging any other library on the net now
(it was very difficult before this change) - so this is definitely helpful
to have binary packages - I'm particularly referring to people being
scared by how difficult the big debian scripts were - now we will package
gnustep-make, gnustep-base, gnustep-gui, etc each one on its own and it
should be pretty easy for anyone to take it - they are standard
self-contained packages.  For an example, see core/make/debian/* were I
quickly packaged - as a proof of concept - the gnustep-make package -
ready for any new maintainer to take it, make sure the scripts conform to
the debian guidelines etc

* the whole stuff is more modular, well structured etc.  It was a pain to
have such a project organized in a huge unmanageable core package where
everything's internal configuration depended on everything else's internal
configuration.

> In the last snapshot I found following problem:
> 
> > ./configure
> loading site script /usr/local/GNUstep/System/share/config.site
> Processing GNUstep site configuration
> creating cache ./config.cache
> checking host system type... i386-pc-solaris2.8
> checking target system type... i386-pc-solaris2.8
> checking build system type... i386-pc-solaris2.8
> checking for gcc... gcc
> checking whether the C compiler (gcc   ) works... yes
> checking whether the C compiler (gcc   ) is a cross-compiler... no
> checking whether we are using GNU C... yes
> checking whether gcc accepts -g... yes
> checking how to run the C preprocessor... gcc -E
> updating cache ./config.cache
> creating ./config.status
> creating GNUmakefile
> creating GNUmakefile.local
> linking ./GNUmakefile.local to base/GNUmakefile.local
> linking ./GNUmakefile.local to base/NSTimeZones/GNUmakefile.local
> linking ./GNUmakefile.local to base/Tools/GNUmakefile.local
> linking ./GNUmakefile.local to base/Admin/GNUmakefile.local
> linking ./GNUmakefile.local to base/Testing/GNUmakefile.local
> linking ./GNUmakefile.local to base/Documentation/GNUmakefile.local
> linking ./GNUmakefile.local to base/Examples/GNUmakefile.local
> linking ./GNUmakefile.local to base/Source/GNUmakefile.local
> linking ./GNUmakefile.local to Documentation/GNUmakefile.local
> linking ./GNUmakefile.local to gui/Model/GNUmakefile.local
> linking ./GNUmakefile.local to gui/Panels/GNUmakefile.local
> linking ./GNUmakefile.local to gui/Source/GNUmakefile.local
> linking ./GNUmakefile.local to gui/Testing/GNUmakefile.local
> linking ./GNUmakefile.local to gui/Tools/GNUmakefile.local
> linking ./GNUmakefile.local.service to
> gui/Tools/GNUmakefile.local.service
> linking ./GNUmakefile.local to xgps/Source/GNUmakefile.local
> linking ./GNUmakefile.local to xgps/Tools/GNUmakefile.local
> configuring in make
> running /bin/sh ./configure  --cache-file=.././config.cache --srcdir=.
> loading site script /usr/local/GNUstep/System/share/config.site
> Processing GNUstep site configuration
> loading cache .././config.cache
> checking host system type... (cached) i386-pc-solaris2.8
> checking target system type... (cached) i386-pc-solaris2.8
> checking build system type... (cached) i386-pc-solaris2.8
> checking for ar... ar
> checking for dlltool... no
> checking for ranlib... ranlib
> checking for gcc... (cached) gcc
> checking whether the C compiler (gcc   ) works... yes
> checking whether the C compiler (gcc   ) is a cross-compiler... no
> checking whether we are using GNU C... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking how to run the C preprocessor... (cached) gcc -E
> checking for perl... /usr/bin/perl
> checking for a BSD compatible install... ./install-sh -c
> checking whether ln -s works... yes
> checking for gtar... no
> checking for alternate objc library... NONE
> ./configure:
> LD_LIBRARY_PATH=/export/home/jano/GNUstep/Libraries/ix86/solaris2.8/gnu-gnu-gnu-xgps:/export/home/jano/GNUstep/Libraries/ix86/solaris2.8:/usr/local/GNUstep/Local/Libraries/ix86/solaris2.8/gnu-gnu-gnu-xgps:/usr/local/GNUstep/Local/Libraries/ix86/solaris2.8:/usr/local/GNUstep/System/Libraries/ix86/solaris2.8/gnu-gnu-gnu-xgps:/usr/local/GNUstep/System/Libraries/ix86/solaris2.8:/opt/sfw/lib:/usr/local/lib:/usr/openwin/lib:/usr/local/GNUstep/System/Libraries/ix86/solaris2.8:
> is not an identifier
> configure: error: /bin/sh ./configure failed for make
> 
> What is wrong in my system ? (The configuring of the older snapshots are
> correctly).
> 
> Thanks.
> 
> 
> 
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> http://mail.gnu.org/mailman/listinfo/discuss-gnustep
>