-malign-double problem
Reported by: |
gerard@… |
Owned by: |
lfs-book@… |
Priority:
|
high
|
Milestone:
|
|
Component:
|
Book
|
Version:
|
CVS
|
Severity:
|
normal
|
Keywords:
|
|
Cc:
|
|
|
|
From: "Jean-Pierre Schwickerath" <email@…>
To: "LFS-Dev" <lfs-dev@…>
Subject: Fileutils
Date: 30 Sep 2001 19:30:49 CEST
I had a kinda nasty experience after compiling fileutils shared. The rm command
gave the following error:
--snip--
root:/usr/src/packages/fileutils-4.1# cd ..
root:/usr/src/packages# rm -rf fileutils-4.1/
rm: ERROR: the directory `fileutils-4.1' initially had device/inode
numbers 2050/134523408, but now (after a chdir into it), the numbers for `.'
are 2050/3221224556. That means that while rm was running, the directory
was replaced with either another directory or a link to another directory.
root:/usr/src/packages#
--snap--
I first thought it was reiserfs that I was using for the 1st time and so I
reformated the partition with ext2 and began from scratch again.
I had the same error. Then I saw that I had -malign-double in my CFLAGS.
I removed it, recompiled fileutils package and... it worked!
Bash has a similar behaviour, when it's compiled with -malign-double, it says
it ignores null-byte-files and then issues a seg fault.
We might warn users about using -malign-double in the optimization hint or even
the book...
Not going to do this. We've established by now that using optimization is done at own risc. We can't begin to list all the different problems that _might_ appear when using certain kind of options.