It looks like the problems was a combination of not having enough of the X
development stuff in place, and also the cache. After deleting
config.cache (and after installing the ubuntu packages I mentioned in my
last email), without any kludged symlinks or special argument to configure
it ran to completion. I was able to make, install and check gwm.
> That could be down to the cache. Remove it, but, as I said to check
> something out like this it's easier to just play with one component. So cd
> to gwm and do:
>
> ./bootstrap
> ./configure
> make
> make install
> make check
>
> until it works. Running bootstrap and configure like this removes any
> dependency on the global settings, so you should be free of any caching
> issues (it will bake in the settings for STARCONF_DEFAULT_PREFIX, so will
> still look in the right place for any dependencies).
Now I'm running into another problem with g95 that I remember from a year
ago when I was building on a redhat fc4 64bit machine:
cd libraries/chr \
&& (make && make install) >make.log 2>make.log.err || { cat
make.log.err; false; }
ld:
/home/echapin/g95-install/bin/../lib/gcc-lib/x86_64-unknown-linux-gnu/4.0.1//libf95.a(transfer.o):
relocation R_X86_64_32S against `a local symbol' can not be used when
making a shared object; recompile with -fPIC
/home/echapin/g95-install/bin/../lib/gcc-lib/x86_64-unknown-linux-gnu/4.0.1//libf95.a:
could not read symbols: Bad value
make[2]: *** [libchr.la] Error 1
make[1]: *** [all] Error 2
make: *** [/stardev/manifests/chr] Error 1
Does this ring a bell? I seem to remember that I need to set some CFLAGS
or something like that.
cheers,
Ed
|