Jiri Novak wrote:
The error always occur at the same place, in ports (it was firefox and
mplayer
for sure, not quite sure about others) and in buildworld, so I don't
suspect faulty hardware.
No useful messages in /var/log/messages...
Well, it seems that I'm doomed :(
--
Jiri Novak
I hate to follo
Jiri Novak wrote:
The error always occur at the same place, in ports (it was firefox and
mplayer
for sure, not quite sure about others) and in buildworld, so I don't
suspect faulty hardware.
No useful messages in /var/log/messages...
Well, it seems that I'm doomed :(
--
Jiri Novak
I hate to follo
Jiri Novak wrote:
The error always occur at the same place, in ports (it was firefox and
mplayer
for sure, not quite sure about others) and in buildworld, so I don't
suspect faulty hardware.
No useful messages in /var/log/messages...
Well, it seems that I'm doomed :(
--
Jiri Novak
I hate to follo
Alex Zbyslaw wrote:
Jiri Novak wrote:
and I have noticed that lots of ports fail to build because of
"internal compiler error" from GCC...
Does the error always occur in the same place? If not, then it is
possible you have a hardware fault.
A segmentation fault results from bad memory access,
Jiri Novak wrote:
and I have noticed that lots of ports fail to build because of
"internal compiler error" from GCC...
Does the error always occur in the same place? If not, then it is
possible you have a hardware fault.
A segmentation fault results from bad memory access, which could be a
pr
Hello,
I have system running:
FreeBSD wopice.valleyofdeath.net 5.3-STABLE FreeBSD 5.3-STABLE #0: Wed
Feb 16 13:05:24 CET 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/WOPICE i386
and I have noticed that lots of ports fail to build because of "internal
compiler error" from GCC... Okay, so I supposed
