| View previous topic :: View next topic |
| Author |
Message |
jbuberel
n00b
Joined: 02 Feb 2003
Posts: 31
Location: Sunnyvale, CA
|
 Posted: Fri Apr 11, 2003 4:57 pm Post subject: OpenOffice 1.0.3 build problems |
 |
|
Did an emerge sync and update last night, and noticed there was a new OpenOffice ebuild available (1.0.3). Since I had not been able to get 1.0.2-r2 to successfully build/install on my machine, I decided to try and get 1.0.3 installed. (NOTE: I did get both 1.0.2-r2 and 1.0.3 to build and install without error on my wife's Athlon based machine running the exact same up-to-date versions of gentoo-1.4 packages).
The error I am getting is:
| Code: | ********************************************************************
* *
* Checking the platform pre-requisites. *
* *
********************************************************************
checking for mawk... no
checking for gawk... gawk
checking for gawk... /bin/gawk
checking the operating system... checked (Linux)
checking for sed... /bin/sed
checking for unzip... /usr/bin/unzip
checking for zip... /usr/bin/zip
checking for sed... (cached) /bin/sed
checking for unzip... (cached) /usr/bin/unzip
checking for zip... (cached) /usr/bin/zip
checking for gcc... /usr/bin/ccache gcc
checking whether the C compiler (/usr/bin/ccache gcc -DTT_CONFIG_OPTION_BYTECODE_INTERPRETER ) works... no
configure: error: installation or configuration problem: C compiler cannot create executables.
!!! ERROR: app-office/openoffice-1.0.3 failed.
!!! Function src_compile, Line 404, Exitcode 1
!!! (no error message) |
I have tried ratcheting down my CFLAGS and CXXFLAGS down to nothing. The original CFLAGS value in /etc/make.conf was:
| Code: | | CFLAGS="-march=pentium3 -O3 -pipe" |
But before the above build attempt I unset my build flags after receiving the same error with the original CFLAGS values noted above:
| Code: | unset CFLAGS
unset CXXFLAGS |
My emerge --info is:
| Code: | # emerge --info
Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r4)
=================================================================
System uname: 2.4.20-gentoo-r2 i686 Pentium III (Coppermine)
GENTOO_MIRRORS="http://gentoo.oregonstate.edu/ http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb:/usr/kde/3.1/share/config:/usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg gnome libg++ libwww mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib alsa gdbm berkdb slang readline arts svga java guile X sdl gpm tcpd pam ssl perl python esd imlib oggvorbis gtk qt kde motif opengl mozilla cdr"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS=""
CXXFLAGS=""
ACCEPT_KEYWORDS="x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache" |
Everythig else on my machine is completely up-to-date as of 10PM PST April 10th, 2003.
Any suggestions would be greatly appreciated.
-jason |
|
| Back to top |
|
 |
AlterEgo
Veteran
Joined: 25 Apr 2002
Posts: 1619
|
| Posted: Fri Apr 11, 2003 5:20 pm Post subject: |
|
|
I had this problem once when distcc was enabled.
Disabling distcc took care of it.
I was unable to figure out why this happened, because I have also built OOo with distcc enabled on other boxes without problems (not that it makes a lot of difference in compile speed, if any).
In your case, ccache might be the trouble-maker, if I have a loot at the error message. |
|
| Back to top |
|
|
jbuberel
n00b
Joined: 02 Feb 2003
Posts: 31
Location: Sunnyvale, CA
|
| Posted: Fri Apr 11, 2003 5:32 pm Post subject: About that 'distcc' thig yo mention... |
|
|
Hmm,
| Quote: | | Disabling distcc took care of it. |
So how would one go about disabling 'distcc'?
And about that ccache stuff:
| Quote: | | In your case, ccache might be the trouble-maker |
And what is ccache for exactly? Can I disable that too?
Thanks,
jason |
|
| Back to top |
|
|
AlterEgo
Veteran
Joined: 25 Apr 2002
Posts: 1619
|
| Posted: Fri Apr 11, 2003 5:44 pm Post subject: |
|
|
distcc can be disabled (if necessary) in /etc/make.conf:
FEATURES="ccache distcc "
Remove it from there.
Ccache caches prevoiously compiled code, so that identical code will be processed/compiled more quickly a next time.
How to disable (if neccessary; your error message suggests you're using ccache, and so doe your flags) it: same as distcc. |
|
| Back to top |
|
|
jbuberel
n00b
Joined: 02 Feb 2003
Posts: 31
Location: Sunnyvale, CA
|
| Posted: Fri Apr 11, 2003 5:46 pm Post subject: The plot thickens... |
|
|
So I start poking around for this 'ccache' thingy:
| Code: | # cd /usr/bin
# ls -la | grep cc
-rwxr-xr-x 1 root root 5432 Mar 7 22:42 cc
drwxr-xr-x 2 root root 264 Feb 23 06:03 ccache
[snip other stuff...]
# cd ccache/
# ls -la
total 25
drwxr-xr-x 2 root root 264 Feb 23 06:03 .
drwxr-xr-x 3 root root 25040 Apr 10 23:45 ..
lrwxrwxrwx 1 root root 6 Mar 7 20:30 c++ -> ccache
lrwxrwxrwx 1 root root 6 Mar 7 20:30 cc -> ccache
lrwxrwxrwx 1 root root 6 Mar 7 20:30 g++ -> ccache
lrwxrwxrwx 1 root root 6 Mar 7 20:30 gcc -> ccache
lrwxrwxrwx 1 root root 6 Mar 7 20:30 i586-pc-linux-gnu-c++ -> ccache
lrwxrwxrwx 1 root root 6 Mar 7 20:30 i586-pc-linux-gnu-g++ -> ccache
lrwxrwxrwx 1 root root 6 Mar 7 20:30 i586-pc-linux-gnu-gcc -> ccache
# ./cc
-bash: ./cc: No such file or directory
thumper ccache # cd cc
-bash: cd: cc: No such file or directory
thumper ccache # |
Which tells me that this whole /usr/bin/ccache directory has some seriously borken symlinks in it. I will try to figure out what put these links here, and remerge to to fix them.
Yet more hilarity ensues in the /usr/bin/ccache directory.
| Code: | # ls
c++ cc g++ gcc i586-pc-linux-gnu-c++ i586-pc-linux-gnu-g++ i586-pc-linux-gnu-gcc
thumper ccache # qpkg -f gcc
sys-devel/gcc *
thumper ccache # qpkg -f cc
thumper ccache # qpkg -f g++
sys-devel/gcc *
thumper ccache # qpkg -f i586-pc-linux-gnu-gcc
thumper ccache # cd ../
thumper bin # qpkg -f cc
thumper bin # ./cc
gcc: no input files |
So as far as my system is concerned, nobody owns the 'cc' files in this directory. And the gcc stuff is owned by 'gcc', as you might expect. In either case, seems like it's time to remerge some compilers. The funny thing is that the sync I did just before this (the kde-3.1.1a updates) completed succesfully. |
|
| Back to top |
|
|
AlterEgo
Veteran
Joined: 25 Apr 2002
Posts: 1619
|
| Posted: Fri Apr 11, 2003 5:51 pm Post subject: |
|
|
Why don't you just unmerge ccache, and try and fix your openoffice problem by just doing that  |
|
| Back to top |
|
|
jbuberel
n00b
Joined: 02 Feb 2003
Posts: 31
Location: Sunnyvale, CA
|
| Posted: Fri Apr 11, 2003 6:06 pm Post subject: Oddly enough... |
|
|
My system claimed that 'distcc' was not even installed. Running 'qpkg --info distcc' reported no installed versions. So I just removed the /usr/bin/ccache directory, and the openoffice build was able to get past the above error.
Thanks, |
|
| Back to top |
|
|
jbuberel
n00b
Joined: 02 Feb 2003
Posts: 31
Location: Sunnyvale, CA
|
| Posted: Fri Apr 11, 2003 6:14 pm Post subject: Now back to the real compile errors... |
|
|
The error message below is eerily similar to what I was getting when trying to install openoffice-1.0.2-r2 on this same system:
| Code: | /var/tmp/portage/openoffice-1.0.3/work/oo_1.0.3_src/external/w4w
mkout -- version: 1.3
------------------------------
Making: ../unxlngi4.pro/misc/w4w.dpc
dmake subdmake=true product="full" depend=t ALLDPC
mkout -- version: 1.3
mkout: ERROR: can't determine module
../unxlngi4.pro/inc/myworld.mk: No such file or directory.
------------------------------
No Dependencies
../unxlngi4.pro/misc/w4w.dpc: No such file or directory.
dmake: Error code 1, while making 'ALLDPC'
---* TARGET.MK *---
dmake: Error code 255, while making '../unxlngi4.pro/misc/w4w.dpc'
---* TG_SLO.MK *---
ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-1.0.3/work/oo_1.0.3_src/external/w4w
* Building OpenOffice.org...
* Scanning for a open DISPLAY to start Xvfb...
* Starting Xvfb on $DISPLAY=1 ...
build -- version: 1.41.2.1
=============
Building project freetype
=============
/var/tmp/portage/openoffice-1.0.3/work/oo_1.0.3_src/freetype
mkout -- version: 1.3
------------------------------
Making: ./unxlngi4.pro/misc/so_freetype.dpc
dmake subdmake=true product="full" depend=t ALLDPC
mkout -- version: 1.3
mkout: ERROR: can't determine module
./unxlngi4.pro/inc/myworld.mk: No such file or directory.
------------------------------
No Dependencies
./unxlngi4.pro/misc/so_freetype.dpc: No such file or directory.
dmake: Error code 1, while making 'ALLDPC'
---* TARGET.MK *---
dmake: Error code 255, while making './unxlngi4.pro/misc/so_freetype.dpc'
---* TG_SLO.MK *---
ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-1.0.3/work/oo_1.0.3_src/freetype
!!! ERROR: app-office/openoffice-1.0.3 failed.
!!! Function src_compile, Line 487, Exitcode 1
!!! Build failed!
|
|
|
| Back to top |
|
|
AlterEgo
Veteran
Joined: 25 Apr 2002
Posts: 1619
|
| Posted: Fri Apr 11, 2003 6:48 pm Post subject: |
|
|
Search the forums for "65280".
Good luck, it's a nasty one. |
|
| Back to top |
|
|
jbuberel
n00b
Joined: 02 Feb 2003
Posts: 31
Location: Sunnyvale, CA
|
|
| Back to top |
|
|
rizzo
Retired Dev
Joined: 30 Apr 2002
Posts: 1067
Location: Manitowoc, WI, USA
|
| Posted: Fri Apr 11, 2003 7:38 pm Post subject: |
|
|
| Check out my post at bug 19155. I believe it is a bug in the 1.0.3 ebuild and how it checks for ccache. |
|
| Back to top |
|
|
jbuberel
n00b
Joined: 02 Feb 2003
Posts: 31
Location: Sunnyvale, CA
|
| Posted: Fri Apr 11, 2003 7:43 pm Post subject: And when I got past that one... |
|
|
Yeah. I didn't even have distcc installed on my machine, so I removed the /usr/bin/ccache directory and got past that error.
Sadly, I then ran into the now infamous "65280 error", which does not seem to have a simple resolution. |
|
| Back to top |
|
|
rizzo
Retired Dev
Joined: 30 Apr 2002
Posts: 1067
Location: Manitowoc, WI, USA
|
| Posted: Fri Apr 11, 2003 7:49 pm Post subject: |
|
|
| WTF? Overheating? |
|
| Back to top |
|
|
calcwatch
n00b
Joined: 17 Dec 2002
Posts: 41
Location: Silicon Valley, USA
|
| Posted: Sun May 11, 2003 8:30 pm Post subject: |
|
|
I'm not sure if this problem is related, but I'm getting error 65280 too. It seems like the build is working perfectly up until this point:
| Code: |
=============
Building project stlport
=============
/var/tmp/portage/openoffice-1.0.3/work/oo_1.0.3_src/stlport
-------------
mkdir ./unxlngi4.pro/misc/build/STLport-4.5.3/src
mkdir: cannot create directory `./unxlngi4.pro/misc/build/STLport-4.5.3/src': File exists
cd ./unxlngi4.pro/misc/build/STLport-4.5.3/src && make -f gcc-3.0.mak -j1 && touch so_built
g++-3.2 -D_REENTRANT -fexceptions -I../stlport -Wall -W -Wno-sign-compare -Wno-unused -Wno-uninitialized -ftemplate-depth-32 -O2 -fPIC dll_main.cpp -c -o ../lib/obj/GCCx86/ReleaseD/dll_main.o
In file included from stlport_prefix.h:28,
from dll_main.cpp:29:
../stlport/ctime:25:44: ../g++-v3/ctime: No such file or directory
In file included from stlport_prefix.h:28,
from dll_main.cpp:29:
../stlport/ctime:32: `size_t' not declared
../stlport/ctime:33: `clock_t' not declared
../stlport/ctime:34: `time_t' not declared
../stlport/ctime:35: `tm' not declared
../stlport/ctime:37: `clock' not declared
../stlport/ctime:38: `asctime' not declared
../stlport/ctime:39: `ctime' not declared
../stlport/ctime:40: `gmtime' not declared
../stlport/ctime:41: `difftime' not declared
../stlport/ctime:42: `mktime' not declared
../stlport/ctime:43: `localtime' not declared
../stlport/ctime:44: `strftime' not declared
../stlport/ctime:45: `time' not declared
In file included from dll_main.cpp:29:
stlport_prefix.h:30: `time_t' not declared
In file included from ../stlport/stl/debug/_debug.c:160,
from ../stlport/stl/debug/_debug.h:418,
from ../stlport/utility:36,
from dll_main.cpp:35:
../stlport/cstdlib:25:46: ../g++-v3/cstdlib: No such file or directory
In file included from ../stlport/stl/debug/_debug.c:160,
from ../stlport/stl/debug/_debug.h:418,
from ../stlport/utility:36,
from dll_main.cpp:35:
[... more "not declared" errors, etc ...]
../stlport/stl/_threads.c:52: `_STL::_STLP_mutex_base
_Swap_lock_struct<__dummy>::_S_swap_lock' is not a static member of `struct
_Swap_lock_struct<__dummy>'
../stlport/stl/_threads.c:52: template definition of non-template `
_STL::_STLP_mutex_base _Swap_lock_struct<__dummy>::_S_swap_lock'
../stlport/stl/_threads.c:102: parse error before `*' token
In file included from ../stlport/stl/_construct.h:43,
from ../stlport/stl/_alloc.h:68,
from ../stlport/memory:28,
from dll_main.cpp:38:
../stlport/stl/_iterator_base.h:50: parse error before `,' token
../stlport/stl/_iterator_base.h:54: template declaration of `typedef _Tp
_STL::value_type'
../stlport/stl/_iterator_base.h:54: confused by earlier errors, bailing out
make: *** [../lib/obj/GCCx86/ReleaseD/dll_main.o] Error 1
dmake: Error code 2, while making './unxlngi4.pro/misc/build/so_built'
---* TG_SLO.MK *---
ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-1.0.3/work/oo_1.0.3_src/stlport
!!! ERROR: app-office/openoffice-1.0.3 failed.
!!! Function src_compile, Line 487, Exitcode 1
!!! Build failed! |
Could this be an overheating problem too, or does it look like something simpler? |
|
| Back to top |
|
|
jbuberel
n00b
Joined: 02 Feb 2003
Posts: 31
Location: Sunnyvale, CA
|
| Posted: Sun May 11, 2003 11:48 pm Post subject: my personal belief... |
|
|
My belief on this one is that it is memory related because the 65280 error always occurs at the same exact point in the compile (at least for me). Heat related problems are generally more sporadic and less repeatable. What is very mysterious is that it only occurs in the openoffice 1.0.3 build.
You could argue that it could be caused by physical memory corruption, but it's not as though the 1.0.3 compilation of oOo is significantly more memory intensive than the 1.0.2 compilation (which worked fine for me).
Therefore, I think it is a very platform/hardware specific memory related build bug that was introduced in oOo 1.0.3 itself. For now, you can just emerge openoffice-bin and be done with it. |
|
| Back to top |
|
|
|
Desktop Environments
