[gentoo-user] kde compile ends in unusal error - fs problem?

[gentoo-user] kde compile ends in unusal error - fs problem?

[Harry Putnam]

I've had an `emerge -v kde' running for hours and this morning I find
it has errored out while compiling kdenetwork.  I can't really figure
out what this error might mean but it appears it might be somekind of
fs problem in /tmp.  I've inlined a hefty snipped from the tail of
output below but first let me ask something more simple.

What should permissions on /tmp look like in a normal system?
I see tmp is chmod 755 but shouldn't it be something like 1777?

I've umounted /tmp ran mkfs.ext3 re mounted then chmod 1777 and now
running what appears to be a successfull (so far) compile of
kdenetwork.

Anyone recognize this error output?

[...]

-no-undefined -Wl,--no-undefined -Wl,--allow-shlib-undefined -R
/usr/kde/3.4/lib -R /usr/kde/3.4/lib -R /usr/qt/3/lib -R /usr/lib
latexplugin.lo latexconfig.lo ../../libkopete/libkopete.la rm -rf
latexprefsbase.h; /usr/qt/3/bin/uic -L
/usr/kde/3.4/lib/kde3/plugins/designer -nounload ./latexprefsbase.ui |
/usr/bin/perl -pi -e "s,public QWizard,public KWizard,g; s,#include
<qwizard.h>,#include <kwizard.h>,g" >> latexprefsbase.h ;
/usr/qt/3/bin/moc ./latexpreferences.h -o latexpreferences.moc /bin/sh
../../../libtool --silent --tag=CXX --mode=compile i686-pc-linux-gnu-g++
-DHAVE_CONFIG_H -I. -I. -I../../..  -I../../../kopete/libkopete
-I../../../kopete/libkopete/ui -I../../../kopete/libkopete/ui
-I/usr/kde/3.4/include -I/usr/qt/3/include -I.  -DQT_THREAD_SUPPORT
-D_REENTRANT -D_FILE_OFFSET_BITS=64 -Wnon-virtual-dtor -Wno-long-long
-Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align
-Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings
-DNDEBUG -DNO_DEBUG -O2 -Os -march=pentium4 -pipe -Wformat-security
-Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common
-fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE
-DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o

[HERE] latexpreferences.lo latexpreferences.cpp ext3_abort called.  EXT3-fs

error (device hdb5): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only ../../../libtool: line 1059: cannot
create temp file for here document: Read-only file system
../../../libtool: line 1138: cannot create temp file for here document:
Read-only file system /usr/qt/3/bin/moc latexprefsbase.h -o
latexprefsbase.moc rm -f latexprefsbase.cpp echo '#include <kdialog.h>'
> latexprefsbase.cpp echo '#include <klocale.h>' >> latexprefsbase.cpp
/usr/qt/3/bin/uic -L /usr/kde/3.4/lib/kde3/plugins/designer -nounload
-tr tr2i18n -i latexprefsbase.h ./latexprefsbase.ui >
latexprefsbase.cpp.temp ; ret=$?; \ /usr/bin/perl -pe "s,tr2i18n( \"\"
),QString::null,g" latexprefsbase.cpp.temp | /usr/bin/perl -pe
"s,tr2i18n( \"\"\, \"\" ),QString::null,g" | /usr/bin/perl -pe
"s,image([0-9][0-9]*)_data,img\$1_latexprefsbase,g" | /usr/bin/perl -pe
"s,: QWizard\(,: KWizard(,g" >> latexprefsbase.cpp ;\ rm -f
latexprefsbase.cpp.temp ;\ if test "$ret" = 0; then echo '#include
"latexprefsbase.moc"' >> latexprefsbase.cpp; else rm -f
latexprefsbase.cpp ; exit $ret ; fi /bin/sh ../../../libtool --silent
--tag=CXX --mode=compile i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H
-I. -I. -I../../..  -I../../../kopete/libkopete
-I../../../kopete/libkopete/ui -I../../../kopete/libkopete/ui
-I/usr/kde/3.4/include -I/usr/qt/3/include -I.  -DQT_THREAD_SUPPORT
-D_REENTRANT -D_FILE_OFFSET_BITS=64 -Wnon-virtual-dtor -Wno-long-long
-Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align
-Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings
-DNDEBUG -DNO_DEBUG -O2 -Os -march=pentium4 -pipe -Wformat-security
-Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common
-fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE
-DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o
latexprefsbase.lo latexprefsbase.cpp ../../../libtool: line 982: cannot
create temp file for here document: Read-only file system
../../../libtool: line 1059: cannot create temp file for here document:
Read-only file system ../../../libtool: line 1138: cannot create temp
file for here document: Read-only file system /bin/sh ../../../libtool
--silent --tag=CXX --mode=link i686-pc-linux-gnu-g++ -Wnon-virtual-dtor
-Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE
-Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith
-Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -Os -march=pentium4 -pipe
-Wformat-security -Wmissing-format-attribute -fno-exceptions
-fno-check-new -fno-common -fno-exceptions -fno-check-new -fno-common
-DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT
-DQT_NO_TRANSLATION -o kcm_kopete_latex.la -rpath /usr/kde/3.4/lib/kde3
-module -no-undefined -Wl,--no-undefined -Wl,--allow-shlib-undefined
-avoid-version -module -no-undefined -Wl,--no-undefined
-Wl,--allow-shlib-undefined -R /usr/kde/3.4/lib -R /usr/kde/3.4/lib -R
/usr/qt/3/lib -R /usr/lib -L/usr/kde/3.4/lib -L/usr/qt/3/lib -L/usr/lib
latexpreferences.lo latexprefsbase.lo latexconfig.lo -lkutils libtool:
link: `latexprefsbase.lo' is not a valid libtool object make[5]: ***
[kcm_kopete_latex.la] Error 1 make[5]: Leaving directory
`/var/tmp/portage/kdenetwork-3.4.1-r1/work/kdenetwork-3.4.1/kopete/plugins/latex'
make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory
`/var/tmp/portage/kdenetwork-3.4.1-r1/work/kdenetwork-3.4.1/kopete/plugins/latex'
make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory
`/var/tmp/portage/kdenetwork-3.4.1-r1/work/kdenetwork-3.4.1/kopete/plugins'
make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory
`/var/tmp/portage/kdenetwork-3.4.1-r1/work/kdenetwork-3.4.1/kopete'
make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory
`/var/tmp/portage/kdenetwork-3.4.1-r1/work/kdenetwork-3.4.1' make: ***
[all] Error 2

!!! ERROR: kde-base/kdenetwork-3.4.1-r1 failed.  !!! Function
kde_src_compile, Line 173, Exitcode 2 !!! died running emake,
kde_src_compile:make !!! If you need support, post the topmost build
error, NOT this status message.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] kde compile ends in unusal error - fs problem?

[Petteri Räty]

[-- Attachment #1: Type: text/plain, Size: 254 bytes --]

Harry Putnam wrote:
> 
> What should permissions on /tmp look like in a normal system?
> I see tmp is chmod 755 but shouldn't it be something like 1777?
> 

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=4#doc_chap5

Regards,
Petteri

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

Re: [gentoo-user] kde compile ends in unusal error - fs problem?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 553 bytes --]

On Sat, 10 Dec 2005 08:04:51 -0600, Harry Putnam wrote:

> What should permissions on /tmp look like in a normal system?
> I see tmp is chmod 755 but shouldn't it be something like 1777?

It should, but it makes no difference to emerging, which is done as root.
1777 is more secure, it stops one user removing another user's files, but
is not the cause of your problem.

How much free space is on /tmp? What does "df -Th /tmp" show?


-- 
Neil Bothwick

"Bother" said Rue, as his paranoia spread across the publicly accessible
archives

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: kde compile ends in unusal error - fs problem?

[Harry Putnam]

Neil Bothwick <neil@digimed.co.uk> writes:

> On Sat, 10 Dec 2005 08:04:51 -0600, Harry Putnam wrote:
>
>> What should permissions on /tmp look like in a normal system?
>> I see tmp is chmod 755 but shouldn't it be something like 1777?
>
> It should, but it makes no difference to emerging, which is done as root.
> 1777 is more secure, it stops one user removing another user's files, but
> is not the cause of your problem.
>
> How much free space is on /tmp? What does "df -Th /tmp" show?

There was plenty of room there.  It turned out to be something
mechanical.  I'm not really sure still exactly what but changing the
ribbon connector from mobo to master and slave drives (one of which
held tmp) seems to have fixed it.   (at least for now)

What got me looking at that was hearing the drive clicking after
restarting kde compile.  Not many but a few widely spaced that seemed
wrong. 

Then in the coures of tinkering I noticed that on bootup hda was
loosing its IRQ repeatedly. 

All seems to be ok now with the ribbon being changed out.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: kde compile ends in unusal error - fs problem?

[Stroller]

On Dec 10, 2005, at 4:35 pm, Harry Putnam wrote:
>
> ...What got me looking at that was hearing the drive clicking after
> restarting kde compile.  Not many but a few widely spaced that seemed
> wrong.

Sounds to me like the hard-drive's on the way out. If there's important 
data on there I'd replace it.

Stroller.

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: kde compile ends in unusal error - fs problem?

[reader]

Stroller <stroller@stellar.eclipse.co.uk> writes:

>> ...What got me looking at that was hearing the drive clicking after
>> restarting kde compile.  Not many but a few widely spaced that seemed
>> wrong.
>
> Sounds to me like the hard-drive's on the way out. If there's
> important data on there I'd replace it.

It seems to have been fixed by changing out the connector ribbon for
the master slave combo that /tmp was on.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: kde compile ends in unusal error - fs problem?

[Stroller]

On Dec 11, 2005, at 12:12 am, reader@newsguy.com wrote:

> Stroller <stroller@stellar.eclipse.co.uk> writes:
>
>>> ...What got me looking at that was hearing the drive clicking after
>>> restarting kde compile.  Not many but a few widely spaced that seemed
>>> wrong.
>>
>> Sounds to me like the hard-drive's on the way out. If there's
>> important data on there I'd replace it.
>
> It seems to have been fixed by changing out the connector ribbon for
> the master slave combo that /tmp was on.

The ribbon made the hard-drive click? Or like, maybe something 
mechanical & intermittent inside the drive itself?

This may amuse: http://tinyurl.com/34y47

Stroller.

-- 
gentoo-user@gentoo.org mailing list