6 Jul 2004 21:51
RE: Dtd location??
Johnson, Tony -Research <gjohnson <at> ADMWORLD.com>
2004-07-06 19:51:12 GMT
2004-07-06 19:51:12 GMT
I apologize , I rebounded and dunked my own miss by modifying the bzip2 Makfile from Redhat that creates a
shared library and compiling it...
all: $(OBJS)
$(CC) -G -o libbz2.so.1.0 $(OBJS)
# $(CC) $(CFLAGS) -o bzip2-shared bzip2.c libbz2.so.1.0.2
rm -f libbz2.so.1.0
ln -s libbz2.so.1.0.2 libbz2.so.1.0
The newer gcc that I built on solaris are now only using solaris ld in /usr/ccs/bin/ld (I wish I knew how to
change that) so the makefile had to be modified.
This seemed to produce a bzip2 shared library that kdelibs liked and is now attempting to build the
kdedoctools for the new installation instead of an old installation I had working for a few years.
Tony
-----Original Message-----
From: Johnson, Tony -Research [mailto:gjohnson <at> ADMWORLD.com]
Sent: Tuesday, July 06, 2004 10:35 AM
To: kde-solaris <at> kde.org
Subject: [kde-solaris] Dtd location??
I just had a problem building kdebase. Acutally I was trying to rebuild it after the first successful time
but I got a similar problem trying to build kdeutils, I was trying to find the location for the dtd's and if I
could just simply copy them in a certain location so these builds would complete.
gmake[3]: Nothing to be done for `all'.
gmake[3]: Leaving directory `/export/home/gjohnson/kde323/kdebase-3.2.3/libkonq/pics'
Making all in favicons
gmake[3]: Entering directory `/export/home/gjohnson/kde323/kdebase-3.2.3/libkonq/favicons'
gmake[3]: Nothing to be done for `all'.
(Continue reading)
RSS Feed