[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Adding Hurd architecture/os to dpkg and packaging scripts.

Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> writes:

> I want to add the Hurd architecture to dpkg and some debian/rules files.
> The following issues have to be resolved, and I am confused by these
> options:
> * dpkg --print-installation-architecture

This is the target for which a package is being compiled. Often used in
rules files because it permits cross compiling. For cross compiling from
linux-i386 to hurd-i386, it will stay the same - i386.

> * dpkg --print-architecture

This is the host which is compiling a package.

> * dpkg --print-gnu-build-architecture

This is the gnu version of the target architecture - for example when you do
gcc -v on i386 linux it reports:
Reading specs from /usr/lib/gcc-lib/i486-linux/
So for i386 the gnu build architecture is i486.

> We use the "hurd-i386" tag for packages, and "i386-gnu" or "i386-pc-gnu" is
> the GNU name of the system.

To extend it consistently you want some options like:

dpkg --print-installation-os

OS of the target system. linux or hurd.

dpkg --print-gnu-build-os

GNU OS of the target system - linux or gnu.

dpkg --print-os

This should return the name of the host os - similar to uname I think.

> Please let me know what you think, and if you know what the various options
> really mean. This issue is semi important, and should be resolved soon, so
> we can start sending patches for the rules files.

Yes, this is important for the hurd.


Reply to: