Bug#548412: grub-common: cpu and machin /usr/include/grub symlinks are bogus

Robert Millan rmh at aybabtu.com
Thu Oct 8 19:34:57 UTC 2009

On Sat, Sep 26, 2009 at 10:08:56AM +0200, Samuel Thibault wrote:
> Package: grub-common
> Version: 1.97~beta3-1
> Severity: normal
> Hello,
> € ls /usr/include/grub/{cpu,machine} -l
> lrwxrwxrwx 1 root root 46 sep 16 14:57 /usr/include/grub/cpu ->
> /tmp/buildd/grub2-1.97~beta3/include/grub/i386
> lrwxrwxrwx 1 root root 49 sep 16 14:57 /usr/include/grub/machine ->
> /tmp/buildd/grub2-1.97~beta3/include/grub/i386/pc
> these look bogus, shouldn't they -> i386 and -> i386/pc ?

It isn't really such a good idea to use those to build modules externally.

The problem is that GRUB autogenerates a number of .lst files (e.g.
command.lst or fs.lst) in which the facilities implemented by your module
ought to be registered, and if they're built externally you don't get
the benefit of this.

This is why grub-extras was integrated at source level instead.  This is
how we add external components in debian (like zfs).

Maybe what you have in mind would fit in grub-extras?

Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."

More information about the Pkg-grub-devel mailing list