wyy's mutt says that on Wed, Jul 11, 2001 at 10:55:42PM +0800, Federico Sevilla III
wrote:
> [ WARNING: Long message. Details of problem first, then some ranting ]
> [ about Debian and a request for distribution comments after. I hope ]
> [ everyone will find time to help me out and/or read my rants. :) ]
>
> Hi everyone,
>
hello good friend!
> Today I noticed that gcc-3.0 is segfaulting. I found this out when I
> attempted to recompile my kernel and it failed sa simula pa lang. I did an
> strace of gcc and got the following:
>
>
> jijo@gusi:~$ strace gcc-3.0 -V
> execve("/usr/bin/gcc-3.0", ["gcc-3.0", "-V"], [/* 21 vars */]) = 0
> uname({sys="Linux", node="gusi", ...}) = 0
> brk(0) = 0x805b37c
> old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) = 0x40015000
> open("/etc/ld.so.preload", O_RDONLY) = 3
> fstat64(3, {st_mode=S_IFREG|0644, st_size=1, ...}) = 0
> old_mmap(NULL, 1, PROT_READ|PROT_WRITE, MAP_PRIVATE, 3, 0) = 0x40016000
> close(3) = 0
> munmap(0x40016000, 1) = 0
> --- SIGSEGV (Segmentation fault) ---
> +++ killed by SIGSEGV +++
>
>
this does not look good. i have been using my gcc-3.0 build for about
a week and a little more. btw, for those who did not read my posts i
have RPMS, SRPMS, spec file for gcc-3.0.
i compile a lot. i built a cross compiler system for sparc-linux and
have been writing some code for some projects.
no segfaults yet. why not build it from source? maybe be a library
problems because 2.95.3, 2.96, 3.0 have different libstdc++ abi's
this means that there cannot be binary compatibility among them. this
may not be the problem but it could be.
>
> It's only now, BTW, that I have an /etc/ld.so.preload. Previous straces
> showed that gcc was segfaulting right after it couldn't find ld.so.preload
> so I installed the ld.so.preload-manager and libsafe packages.
>
what is that? i do not have that?
<snip>
hmmm. no idea.
<snip>
jijo is leaving debian? hmmm..... but not back to redhat i presume.
i use redhat 7.1 as a personal workstation with all the goodies like
gcc-3.0, new binutils, glibc, ximian and etc.... i like redhat simply
because i know it quite well and that is why i am sticking to it. not
because it is better than other distros.
i think this rule should apply to others too. the squid developers
recommend this. choose the OS/distribution you know best.
about bleeding edge, redhat...debian...mandrake are bleeding
edge enough for me. redhat has rawhide, mandrake has freq and debian has
unstable. take your pick.
about, updates i subscribe to BUGTRAQ. and grab the sources.
btw, i am a source person. to the purist, i am a SOURCE RPM person.
>
> Also, to those who use RPM-based distributions (this probably accounts for
> 99% of PLUG): does RPM have some sort of capability to allow the sysad to
> decide whether an updated configuration file should be upgraded or not?
> dpkg prompts users before updating configuration files and I've found this
> very useful. I despise having to search for the rpmsaves or whatever
> they're called now.
>
as far as i know, it always keeps the old config.
--------------------------------------
William Emmanuel S. Yu
Ateneo Cervini-Eliazo Networks (ACENT)
email : [EMAIL PROTECTED]
web : http://cersa.admu.edu.ph/
phone : 63(2)4266001-5925/5904
Be careful when a loop exits to the same place from side and bottom.
PGP signature
