qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Mateusz Loskot <mateusz@loskot.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Missing roms/seabios/Makefile and roms/vgabios/Makefile
Date: Thu, 20 Jan 2011 10:58:31 +0000	[thread overview]
Message-ID: <20110120105759.GA27019@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <4D3813A5.6090206@loskot.net>

On Thu, Jan 20, 2011 at 10:51:17AM +0000, Mateusz Loskot wrote:
> On 19/01/11 18:07, Blue Swirl wrote:
> >On Wed, Jan 19, 2011 at 12:44 PM, Mateusz Loskot<mateusz@loskot.net>  wrote:
> >>Hi,
> >>
> >>Running ./configure (under MinGW/MSYS) and symlink gives up trying to
> >>create links to non-existing Makefiles in
> >>roms/seabios/Makefile
> >>roms/vgabios/Makefile
> >
> >Those directiories are actually git submodules, when you run 'git
> >submodule update', they get populated.
> 
> Something is not quite working and I don't get anything populated.
> Here I tried under MinGW
> 
> mloskot@dog /g/src/qemu/_git/master
> $ git pull
> Already up-to-date.
> 
> mloskot@dog /g/src/qemu/_git/master
> $ git submodule update
> 
> mloskot@dog /g/src/qemu/_git/master
> $ ls roms/seabios/
> config.mak

Make sure roms/{vgabios,seabios} are empty directories.

$ git submodule init
$ git submodule update

This should clone the vgabios and seabios repos and checkout the correct
commit.  After this completes successfully you should have source trees
under roms/{vgabios,seabios}.

Stefan

  reply	other threads:[~2011-01-20 10:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19 12:44 [Qemu-devel] Missing roms/seabios/Makefile and roms/vgabios/Makefile Mateusz Loskot
2011-01-19 18:07 ` Blue Swirl
2011-01-20 10:51   ` Mateusz Loskot
2011-01-20 10:58     ` Stefan Hajnoczi [this message]
2011-01-20 14:15       ` Mateusz Loskot

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=20110120105759.GA27019@stefanha-thinkpad.localdomain \
    --to=stefanha@gmail.com \
    --cc=mateusz@loskot.net \
    --cc=qemu-devel@nongnu.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).