Hi Loren I do not have a direct answer to your question. I did experience some compile errors when I was compiling kdebase for this version. My solution was to compile and install as much recommended and optional packages as possible and finally I successfully compiled all the core kde packages, including kdebase.
Mfundisi Dumisa -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Rick Shelton Sent: 02 July 2009 02:12 PM To: BLFS Support List Subject: Re: Kdebase-3.5.10 Compile error On Thu, Jul 2, 2009 at 2:41 AM, Loren Foret<[email protected]> wrote: > I hope someone can help me with this. I have been following the LFS svn and > BLFS pre 6.4 tracks and now I am having issues compiling kdebase > > Here is my base config (notice I pushed gcc to the svn release to try to > rule it out) > > root [ ~ ]# uname -r > 2.6.26 > root [ ~ ]# cc -v > Using built-in specs. > Target: i686-pc-linux-gnu > Configured with: ./configure --prefix=/usr > Thread model: posix > gcc version 4.4.1 20090623 (prerelease) (GCC) > > And a snip of the compile log where it failed: > > Making all in kfontinst > make[4]: Entering directory > `/root/Desktop/kdebase-3.5.10/kcontrol/kfontinst/kfontinst' > g++ -DHAVE_CONFIG_H -I. -I../../.. -DOS_Linux -I./../lib -I./../../fonts > -I/opt/kde/include -I/opt/qt/include -I. -I/usr/include/freetype2 > -DQT_THREAD_SUPPORT -D_REENTRANT -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES=1 > -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align > -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 > -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor > -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE > -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION > -D_GNU_SOURCE -c -o Fontmap.o Fontmap.cpp > Fontmap.cpp: In function 'bool parseLine(const char*, QString&, QString&, > bool&)': > Fontmap.cpp:68: error: invalid conversion from 'const char*' to 'char*' > Fontmap.cpp: In function 'void addEntry(QStringList&, const QString&, const > QString&, const QString&)': > Fontmap.cpp:199: warning: suggest explicit braces to avoid ambiguous 'else' > Fontmap.cpp: In function 'QString locateFile(const char*, const char*, > int)': > Fontmap.cpp:256: warning: suggest explicit braces to avoid ambiguous 'else' > make[4]: *** [Fontmap.o] Error 1 > make[4]: Leaving directory > `/root/Desktop/kdebase-3.5.10/kcontrol/kfontinst/kfontinst' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory `/root/Desktop/kdebase-3.5.10/kcontrol/kfontinst' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/root/Desktop/kdebase-3.5.10/kcontrol' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/root/Desktop/kdebase-3.5.10 > > > I looked at this code segment in question in Fontmap.cpp and at line 68 I > see this: > > char *slash1=strchr(line, '/'), > *space1=slash1 ? findSpace(slash1) : NULL, //strchr(slash1, ' > > I couldn't figure out how to change this particular line so further up I see > > static bool parseLine(const char *line, QString &ps, QString &fname, bool > &isAlias) > > And attempted to change it to: > > static bool parseLine(char *line, QString &ps, QString &fname, bool > &isAlias) > > And it compiles fine but now I think by doing this I am damaging KDE. > Konqueror crashes when I visit any site but google and Firefox 3.5.11 > displays everything in huge fonts. I tried a userChrome.css script to fix > firefox but that does not work. If my memory serves me right wasn't there a > lot of C++ rule changes after gcc 3.3? I doubt this is a programming error > but I am not good enough to figure this out > > Help please o wise and kind group > > Loren Foret > [email protected] > > > -- > http://linuxfromscratch.org/mailman/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > Well it looks like you correctly identified the offensive line of code, but this is more likely an issue with the kdebase package as a whole. This may be a not-ready-for-prime-time version of kdebase. Have you checked for patches for this version of this package on the kde site? I would actually suggest rolling back to stable release versions of both gcc and kde. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
