LinuxSir.cn,穿越时空的Linuxsir!

 找回密码
 注册
搜索
热搜: shell linux mysql
查看: 1730|回复: 16

有的时候,真想放弃LFS。:(。郁闷。

[复制链接]
发表于 2004-12-26 13:23:07 | 显示全部楼层 |阅读模式
今天又LFS+BLFS了一次。
LFS: LFS 6.0
BLFS: 能编译KDE的最小配置。

结果还是出错。是不是偶这辈子就用不了这个该死的KDE了。NND。
神啊,让我编译成功一次好不好。用了LFS6后,没一次编译成功的。真想砸了刻录的LFS6 Booting CD。。。

(相信这几个都是最新的了)
lcms: 1.14
jpeg: 6b
libmng: 1.08
libtiff: 3.7.1
libpng: 1.2.8
libungif: 4.1.3
giflib: 4.1.3
alisa: 1.0.7

KDE: 3.3.90/3.3.2 都试过了。
qt: 3.3.3
X: Xorg 6.8.1
fontconfig: 2.2.3
freetype: 2.1.9

我觉得是lfs6的问题,但是我不确定。所以再一次问问大家,你们的gui是用什么的?

谢谢你们的支持。非常感谢。
发表于 2004-12-26 14:02:25 | 显示全部楼层
估计是 GCC 的问题,用 GCC-3.3.4 试试吧。
发表于 2004-12-26 14:35:14 | 显示全部楼层
blfs-book-cvs-html-2004-12-05
LFS-6.0-testing-20041010
按照这两本文档编译的,我对照lfs-6.0和testing,里面的东西版本都是相同的
不知道还有什么其他的差别没有。
我使用的下面这些版本,编译kde3.3没出现问题
lcms: 1.13
jpeg: 6b
libmng: 1.08
libtiff: 3.7.0
libpng: 1.2.7
libungif: 4.1.3
giflib: 4.1.3
alisa: 1.0.7
KDE: 3.3.0
qt: 3.3.3
X: Xorg 6.8.1
fontconfig: 2.2.3
freetype: 2.1.9
发表于 2004-12-26 15:01:05 | 显示全部楼层
我现在编译安装kde都已经没有问题了。
就是想升级为qt-4.0-b1,但是不知道要怎么改kde,让它可以使用qt-4.0的compat3。
呵呵。
发表于 2004-12-26 17:55:24 | 显示全部楼层
是哪里出错了??

觉得lfs6还是比较稳定的,编译kde也一切顺利
唯一的问题是不能用kdm登录(kde logo 那个加载画面中途会退回到输用户密码界面)
 楼主| 发表于 2004-12-26 20:10:11 | 显示全部楼层
X Protocol Version 11, Revision 0, Release 6.8.1
Build Operating System: Linux 2.6.9 i686 [ELF]
Current Operating System: Linux Fiancee 2.6.9 #1 Sat Dec 25 15:57:50 GMT 2004 i686
Build Date: 26 December 2004
        Before reporting problems, check http://wiki.X.Org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec 26 12:07:47 2004
(==) Using config file: "/etc/X11/xorg.conf"
(WW) RADEON(0): Failed to set up write-combining range (0xe8000000,0x2000000)
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
xset:  bad font path element (#72), possible causes are:
    Directory does not exist or has wrong permissions
    Directory missing fonts.dir
    Incorrect font server address or syntax
startkde: Starting up...
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
KCrash: Application 'ksplash' crashing...
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca: WARNING: 'kcertpart.desktop' specifies undefined mimetype/servicetype 'application/binary-certificate'
kbuildsycoca: WARNING: 'katepart.desktop' specifies undefined mimetype/servicetype 'text/x-fortran'
kbuildsycoca: WARNING: 'knotify.desktop' specifies undefined mimetype/servicetype 'KNotify'
DCOP aborting (delayed) call from 'anonymous-9360' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
KCrash: Application 'kded' crashing...
SetClientVersion: 0 8
KCrash: Application 'kcminit' crashing...
QFont::setPointSize: Point size <= 0 (-3)
KCrash: Application 'kwin' crashing...
Launched ok, pid = 9378
ALSA lib pcm_hw.c:563snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
ALSA lib pcm_hw.c:563snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
ALSA lib pcm_hw.c:563snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
DCOP aborting call from 'anonymous-9379' to 'kdesktop'
ERROR: Communication problem with kdesktop, it probably crashed.
KCrash: Application 'kdesktop' crashing...
kdecore (KAccel): WARNING: KAccelActions::insertLabel( Program:kicker, Panel ): action with same name already present.
DCOP aborting (delayed) call from 'anonymous-9381' to 'kicker'
ERROR: Communication problem with kicker, it probably crashed.
KCrash: Application 'kicker' crashing...
DCOP aborting call from 'anonymous-9386' to 'ktip'
ERROR: Communication problem with ktip, it probably crashed.
KCrash: Application 'ktip' crashing...
knotify: Fatal IO error: client killed
klipper: Fatal IO error: client killed

waiting for X server to shut down Hangup
GOT SIGHUP
startkde: Shutting down...
ksmserver: Fatal IO error: client killed
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
klauncher: Exiting on signal 1
klauncher: Fatal IO error: client killed
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
startkde: Running shutdown scripts...
startkde: Done.
发表于 2004-12-27 10:36:12 | 显示全部楼层
我还没有完全装成LFS,仅完成了全部软件的编译,没有用LFS启动过,
在启动的时候出错,因为我没有条件做,所以在等机会,
不过,就我编译过程中最常见的错误是命令输入错误,前面的错误没有
发觉,影响后面的工作,所以我强烈建议,编写一个脚本来编译LFS,
因为LFS系统的编译时间拖得太长了,用手工输入的方法实在是太慢了,
我觉得先看LFS的参考书,将参考书的命令写成脚本,该脚本中只需要
加入出错退出判断就行了,编译时,每成功一次,成功的几步可以积累
下来,下次编译的时候以前成功的地方绝对不会再出错,这样可以一步
一步走到终点!
 楼主| 发表于 2004-12-27 12:41:57 | 显示全部楼层
呵呵,放心,我输入命令不会错的。。。。。谢谢你的提议:)。
发表于 2004-12-27 18:24:46 | 显示全部楼层
好多crash啊,偶看不出来原因:(
这是xorg的log吗,~/.xsessionerror有啥提示吗
应该是~/.xsession-errors  
 楼主| 发表于 2004-12-27 20:56:53 | 显示全部楼层
这个,似乎。。。。,没生成这个文件。。。。
您需要登录后才可以回帖 登录 | 注册

本版积分规则

快速回复 返回顶部 返回列表