The xml for individual packages occasionally
contains architecture dependencies. It would
be nice to abstract these out to the extent
possible - perhaps to definitions in
entities/packages?
Here are the two files I'm aware of at the moment:
kernel.xml:
<make>
<base>
&build_dir;/&linux-directory;
</base>
<param>bzImage</param>
</make>
bzImage is not necessarily the correct build target
for other architectures besides ia32. The target could
be an externally defined entity. Later:
<postbuild>
<copy>
<base>
&build_dir;/&linux-directory;
</base>
<source>
arch/i386/boot/bzImage
</source>
<destination>
/boot/vmlinuz-&linux-version;
</destination>
</copy>
For example, on Itanium, the bootable image ends up being
vmlinux.gz at the top level of the kernel tree (after doing
a "make compressed")...again, this could be an externally
defined entity.
In glibc.xml:
<search_replace>
<base>&build_dir;/&glibc-directory;/sysdeps/unix/sysv/linux/i386/</base>
<file>ldconfig.h</file>
<find>ld-linux.so.2</find>
<replace>ld-lsb.so.1</replace>
</search_replace>
The Itanium is odd, for legacy reasons it uses a
different dynamic linker (ld-linux is the one that
handles 32-bit binaries), and so the LSB dynamic linker
is different, too. This is a place where this one
platform is different from the others so maybe
generalizing is not appropriate.
But the path to the architecture-dependent directory
could be generalized to an externally defined entity.
Mats
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with subject of "unsubscribe". Trouble? Email [EMAIL PROTECTED]
