From: "Eric S. Johansson" <esj@harvee.org>
To: smohekey@insightful.co.nz
Cc: Barry G <xen@barrygrussling.com>, xen-devel@lists.sourceforge.net
Subject: Re: Re: xenning gentoo
Date: Tue, 15 Feb 2005 08:22:20 -0500 [thread overview]
Message-ID: <4211F78C.1060400@harvee.org> (raw)
In-Reply-To: <4210B397.7010100@harvee.org>
Eric S. Johansson wrote:
> Barry G wrote:
>
>> Not really. It is nice to know that I am not alone though.
>>
>> I updated the gentoo bug report with this information two days
>> ago (http://bugs.gentoo.org/show_bug.cgi?id=70161#c38).
>
>
> went a little further. Repackaged the source tarball so that the
> top-level directory ended in 2.0.4. Build went further but I got
> something I've never seen before:
>
> ACCESS DENIED mkdir: /usr/portage/distfiles/install
> install: cannot create directory `/usr/portage/distfiles/install':
> Permission denied
> make[1]: *** [install] Error 1
went further this morning and posted this series of observations and
questions on the gentoo user mailing list in search of answers:
"""
trying to use the xen ebuild from bugzilla and I've encountered a series
of problems which have overcome in less than ideal ways and I'd like to
try and fix them the right way.
The xen source tarball is delivered with a ./xen-2.0/ path and not with
the version number is part of the path. As a result $(S) is wrong and
I'm wondering what's the right way to handle this?
I worked around the problem by rebuilding the tarball with the version
number in the path and encountered a situation where it was trying to
make a directory in someplace it shouldn't.
(/usr/portage/distfiles/install). looking further into the makefile
generating the error, it appears that $(DESTDIR) is the culprit. My
second question is it legitimate to change DESTFILE or should I create a
patch or dynamically edit makefiles to change DESTFILE. If I change it,
what do I change it to?
"""
Scott, do you want me to update the bugzilla entry?
---eric
--
http://www.salon.com/books/review/2004/12/18/heloise/index.html
The basis of Abelard's philosophy, which he taught to Heloise, was
that logic had to be applied to religion in order to arrive at the
truth.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-15 13:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 0:33 xenning gentoo Eric S. Johansson
2004-12-06 19:25 ` Derek Glidden
2004-12-31 17:11 ` Eric S. Johansson
2004-12-31 19:16 ` Anthony Liguori
2004-12-31 19:44 ` Eric S. Johansson
[not found] ` <41D5C66D.308@insightful.co.nz>
[not found] ` <41F7ECA0.1080205@harvee.org>
2005-01-27 19:12 ` Scott Mohekey
2005-01-28 21:02 ` Jon Mason
2005-01-28 22:22 ` Scott Mohekey
2005-01-28 22:40 ` Jon Mason
2005-01-29 1:38 ` Mark Williamson
[not found] ` <420CC301.8030402@harvee.org>
2005-02-11 20:34 ` Scott Mohekey
2005-02-13 13:57 ` Eric S. Johansson
2005-02-13 20:05 ` Barry G
2005-02-13 20:39 ` Eric S. Johansson
2005-02-13 22:12 ` Eric S. Johansson
2005-02-14 0:51 ` Barry G
2005-02-14 14:20 ` Eric S. Johansson
2005-02-15 13:22 ` Eric S. Johansson [this message]
2005-02-15 13:52 ` B.G. Bruce
2005-01-03 0:54 ` Derek Glidden
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=4211F78C.1060400@harvee.org \
--to=esj@harvee.org \
--cc=smohekey@insightful.co.nz \
--cc=xen-devel@lists.sourceforge.net \
--cc=xen@barrygrussling.com \
/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.