The usual cause for this is that you're out of memory. Any possibility that's
the case here? Also explains why sometimes it succeeds and sometimes it fails
without you changing anything obvious.
-- Murphy
On Oct 14, 2010, at 12:39 AM, Niky Riga wrote:
Hi,
Attached is the output of a failed build effort.
At some point you will see the error :
mv -f .deps/authenticator_la-user_event.Tpo
.deps/authenticator_la-user_event.Plo
mv -f .deps/authenticator_la-host_event.Tpo
.deps/authenticator_la-host_event.Plo
g++: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See file:///usr/share/doc/gcc-4.4/README.Bugs for instructions.
make[9]: *** [authenticator_la-authenticator_util.lo] Error 1
gcc version :
nr...@kriti:~/test/nox/build$ gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
4.4.1-4ubuntu9' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared
--enable-multiarch --enable-linker-build-id --with-system-zlib
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4
--enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc
--enable-targets=all --disable-werror --with-arch-32=i486 --with-tune=generic
--enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu
--target=i486-linux-gnu
Thread model: posix
gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9)
Hope this helps,
Niky
Niky Riga wrote:
Basically I believe that the authenticator failed to compile.
I think that g++ faced problems while trying to compile it and in the end
all the reported errors were about that.
I know that this is probably not all that helpful :-) I will try and
reproduce it and send you
the output.
Thanks,
Niky
James Murphy McCauley wrote:
If it ended up seeming to work, I think the chances are good that it's
fine. But I'm interested in whatever the problem may have been if you care
to help me understand it a bit more.
Nothing stuck out at me after a quick glance at your attachments, and those
warnings are generally going to be benign if things do end up compiling and
linking (I don't know of any cases off the top of my head where different
versions of XSI have DIFFERENT values/semantics depending on the version,
though there may be some).
Can you say more about how installation failed the first time? Did it fail
to build? Did make install fail to copy things to their intended
destinations? Something else?
-- Murphy
On Oct 13, 2010, at 10:01 PM, Niky Riga wrote:
Hi,
I am running FV 0.6 beta 4 and the zaku release for nox.
I have been having some problems with nox, and I decided to make a clean
installation before posting on the list.
Trying a clean install on a machine running Ubuntu K, didn't go smoothly
so I though I would ask to verify that
the problems I am seeing is not due to installation problems.
I followed all the instructions as listed in :
http://noxrepo.org/noxwiki/index.php/NOX_Installation
The first time the installation failed.
There were several warning of the type :
In file included from /usr/include/python2.6/Python.h:8,
from ../../../src/lib/fault.cc:33:
/usr/include/python2.6/pyconfig.h:1028:1: warning: _POSIX_C_SOURCE
redefined
In file included from
/usr/include/c++/4.4/i486-linux-gnu/bits/os_defines.h:39,
from
/usr/include/c++/4.4/i486-linux-gnu/bits/c++config.h:243,
from /usr/include/c++/4.4/string:40,
from ../../../src/include/fault.hh:21,
from ../../../src/lib/fault.cc:19:
/usr/include/features.h:158:1: warning: this is the location of the
previous definition
In file included from /usr/include/python2.6/Python.h:8,
from ../../../src/lib/fault.cc:33:
/usr/include/python2.6/pyconfig.h:1037:1: warning: _XOPEN_SOURCE
redefined
In file included from
/usr/include/c++/4.4/i486-linux-gnu/bits/os_defines.h:39,
from
/usr/include/c++/4.4/i486-linux-gnu/bits/c++config.h:243,
from /usr/include/c++/4.4/string:40,
from ../../../src/include/fault.hh:21,
from ../../../src/lib/fault.cc:19:
I ran make -j again and this time it's succeeded. Is that fine?
I attach the output of the ../configure command and of the make -j the
time that it succeeded.
Thanks,
niky
make.outconfig.out___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
nox-build.rtf
___
nox-dev
