crash while doing mkdir (system as of afternon today )

Matthew Dillon dillon at apollo.backplane.com
Sun Apr 4 16:15:08 PDT 2004


:> builds,
:>     but Dave has a good point.  If you are using anything other then 
:> -O to
:They will be inherited by gcc in a self corruption manner if a 
:buildworld
:was performed with -O2 in make.conf. I just ran a small test case 
:machine
:last week and found that the build process would fail in random places
:after running a few build/install worlds in a row with -O2 and -O3 
:settings.
:
:-DR

    Whoop!  You are absolutely right, Dave, and in fact I think this happened
    to me at one point too... my C compiler binaries got corrupted due to -O
    optimizations and then produced bad code.

    So, Tomaz, I recommend you reload your binaries from the ISO CD and turn
    off all -O2 options everywhere.  If you want to try to get things
    operational from the existing installed base, you have to rebuild your
    kernel and world, install both, reboot, rebuild them again, install both
    again, and reboot again... and even that won't guarentee that the compiler
    is clean.

    I do not know if this is the issue but I think there's a good chance that
    it is.

					-Matt
					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>





More information about the Bugs mailing list