From: Paul Larson <plars@linuxtestproject.org>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: 2.0-testing.bk
Date: Tue, 25 Jan 2005 12:38:45 -0600 [thread overview]
Message-ID: <1106678325.5366.14.camel@localhost.localdomain> (raw)
In-Reply-To: <1106674780.5366.9.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
The previous build failure when latex not installed seems to have been
fixed. However the patch from yesterday to create symlinks to the
kernels in /boot is circumvented now that the files aren't copied from
dist/install/* as before.
-install-kernels:
- cp -a $(DESTDIR)/boot/* /boot/
- cp -a $(DESTDIR)/lib/modules/* /lib/modules/
- cp -dR $(DESTDIR)/boot/*$(LINUX_VER)* $(prefix)/boot/
- cp -dR $(DESTDIR)/lib/modules/* $(prefix)/lib/modules/
I can easily work around this by doing make dist and calling install.sh
manually, but if anyone wanted the symlinks to be created when doing a
make install, that won't happen anymore.
--
Thanks,
Paul Larson
plars@linuxtestproject.org
http://www.linuxtestproject.org
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-25 18:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 15:00 2.0-testing.bk Nicholas Berry
2005-01-25 15:43 ` 2.0-testing.bk Ian Pratt
2005-01-25 17:39 ` 2.0-testing.bk Paul Larson
2005-01-25 17:45 ` 2.0-testing.bk Keir Fraser
2005-01-25 18:38 ` Paul Larson [this message]
2005-01-25 16:53 ` 2.0-testing.bk Keir Fraser
2005-01-25 22:08 ` 2.0-testing.bk Kip Macy
2005-01-25 22:22 ` 2.0-testing.bk Keir Fraser
2005-01-25 22:26 ` 2.0-testing.bk Kip Macy
2005-01-26 0:01 ` 2.0-testing.bk Kip Macy
-- strict thread matches above, loose matches on Subject: below --
2005-01-25 13:17 2.0-testing.bk Ian Pratt
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=1106678325.5366.14.camel@localhost.localdomain \
--to=plars@linuxtestproject.org \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.