grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Xen and all_video.mod
Date: Tue, 20 Sep 2016 06:46:23 +0300	[thread overview]
Message-ID: <686b83d2-4160-c794-c613-787c6beba7e9@gmail.com> (raw)
In-Reply-To: <20160919172800.GB13998@riva.ucam.org>

19.09.2016 20:28, Colin Watson пишет:
> Current master fails like this when configured with --with-platform=xen
> and using binutils 2.27:
> 
>   TARGET_OBJ2ELF= sh genmod.sh moddep.lst all_video.module build-grub-module-verifier all_video.mod
>   build-grub-module-verifier: error: no symbol table and no .moddeps section.
>   Makefile:42584: recipe for target 'all_video.mod' failed
> 
> There's no video driver configured for Xen in
> grub-core/Makefile.core.def, so this makes a certain amount of sense:
> it's an empty module with no dependencies, which is what
> 67dba97e4598eaf2deb14da044fbfb1c119cf76f purports to prevent.  On the
> other hand, that does make Xen unbuildable at least with some binutils
> versions (2.26.1 seems to work fine; more specifically, I can build
> --with-platform=xen on Ubuntu xenial but not on Debian unstable).  I
> considered just adding the cirrus driver for Xen to pacify this, but
> that uses PCI symbols that aren't built for Xen at the moment.
> 
> What's the best answer here?  Is there some reasonable way to weaken
> this test so that this module is allowed to be useless on this platform?
> 

Yes, that's what openSUSE is using currently, see also
http://savannah.gnu.org/bugs/?49012

I hoped there is some trick to skip building this module generically,
but then we also have potential issue with config scripts.

What about changing all_video to actually load modules at run time based
on video.lst? The code itself is trivial.


      reply	other threads:[~2016-09-20  3:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 17:28 Xen and all_video.mod Colin Watson
2016-09-20  3:46 ` Andrei Borzenkov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=686b83d2-4160-c794-c613-787c6beba7e9@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).