From: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] possible bug with 2.1 alpha?
Date: Sun, 2 Oct 2005 20:31:33 +0200 [thread overview]
Message-ID: <20051002203133.11eadac1@eusebe> (raw)
In-Reply-To: <20051002173537.GA31467@linux1.home>
On Sun, 2 Oct 2005 12:35:37 -0500
William Hubbs <williamh@gentoo.org> wrote:
> install: all
> $(INSTALL) $(BINARIES) $(DESTDIR)$(PREFIX)/bin
...
> install: installing multiple files, but last argument,
> `/var/tmp/portage/speakup-utils-1.0/image//usr/bin' is not a
> directory
Seems that it simply lacks creation of the target directory.
I would either add an "$(INSTALL) -d $(DESTDIR)$(PREFIX)/bin" in the
makefile, or workaround it with a "dodir /usr/bin" in the ebuild.
But i don't think it's related to portage CVS.
--
TGL.
--
gentoo-portage-dev@gentoo.org mailing list
prev parent reply other threads:[~2011-10-31 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-02 17:35 [gentoo-portage-dev] possible bug with 2.1 alpha? William Hubbs
2005-10-02 18:21 ` Alec Warner
2005-10-02 18:31 ` Thomas de Grenier de Latour [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=20051002203133.11eadac1@eusebe \
--to=degrenier@easyconnect.fr \
--cc=gentoo-portage-dev@lists.gentoo.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