[SM-Discuss] glibc spell status and next ISO

Benoit PAPILLAULT benoit.papillault at sourcemage.org
Mon Feb 14 12:46:28 EST 2005


Arwed von Merkatz a écrit :
> Where does this asm dir come from? Why is it useful? (The headers
> explicitly include stuff in asm-i386, so nothing in that is multi-arch)

The asm is usually a symlink to asm-<ARCH>. But if you are compiling on 
a multi-arch system (ie, a system capable of running binary from 
multiple architecture, like i486 + x86_64), the symlink cannot point at 
the very same time to asm-i386 AND asm-x86_64. The solution was to 
remove the symlink and create a small header file that includes the 
proper headers based on compiler flags (internal defines). Look at 
/usr/include/asm/errno.h for instance.

Since x86_64 is no longer on target, I will remove this from the next 
ISO release.

> The odd thing is that those files _are_ in the glibc-kernel-headers
> install log on the iso but don't get removed when it gets dispelled due
> to the conflict in glibc. And this is not caused by glibc, as the spell
> doesn't edit these logs anymore.

??? If the files are in the install logs, why they are not removed? BTW, 
the glibc spell no longer edit the logs in devel and test, but not in 
stable! :-)

Benoit PAPILLAULT, ISO guru



More information about the SM-Discuss mailing list