From: reader@newsguy.com
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: More ebuild failing (install step)
Date: Thu, 07 Sep 2006 14:25:08 -0500 [thread overview]
Message-ID: <87odtr5vjf.fsf@newsguy.com> (raw)
In-Reply-To: 7573e9640609071203n7f5e225axb3c4910695aaa7ef@mail.gmail.com
"Richard Fish" <bigfish@asmallpond.org> writes:
> On 9/7/06, reader@newsguy.com <reader@newsguy.com> wrote:
>> No, I ran find between `compile' and `install', and that must be the
>> problem. ./source/Makefile disappears when I run `ebuild install'. Checking now:
>
> Ok, I'm getting the same error. If you do an unpack and then compile,
> do you get the following at the start of the compile? How about at
> the start of the install?
>
> * checking samba-3.0.23c.tar.gz ;-) ... [ ok ]
> * checking samba-3-gentoo-0.3.14.tar.bz2 ;-) ... [ ok ]
>>>> Checking samba-3.0.23c.tar.gz's mtime...
>>>> samba-3.0.23c.tar.gz has been updated; recreating WORKDIR...
>>>> /usr/local/portage/net-fs/samba/samba-3.0.23c.ebuild has been
> updated; recreating WORKDIR...
>>>> Unpacking source...
>
> This would be a real problem for install, as it would result in the
> source tree being removed and recreated...obviuosly in an unconfigured
> and uncompiled state.
>
> This is odd, and I'm still looking for the solution...
Yeah, it hadn't dawned on me what that meant or that I should take it
literally. It appears to do everything all over again at each step.
And of course since source has been replaced and is now in uncompiled
state the make error makes sense.
>From `install'
root # ebuild samba-3.0.23c.ebuild install
* samba-3-gentoo-0.3.14.tar.bz2 MD5 ;-) ... [ ok ]
* samba-3-gentoo-0.3.14.tar.bz2 RMD160 ;-) ... [ ok ]
* samba-3-gentoo-0.3.14.tar.bz2 SHA1 ;-) ... [ ok ]
* samba-3-gentoo-0.3.14.tar.bz2 SHA256 ;-) ... [ ok ]
* samba-3-gentoo-0.3.14.tar.bz2 size ;-) ... [ ok ]
* samba-3.0.23c.tar.gz MD5 ;-) ... [ ok ]
* samba-3.0.23c.tar.gz RMD160 ;-) ... [ ok ]
* samba-3.0.23c.tar.gz SHA1 ;-) ... [ ok ]
* samba-3.0.23c.tar.gz SHA256 ;-) ... [ ok ]
* samba-3.0.23c.tar.gz size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
* checking samba-3.0.23c.tar.gz ;-) ... [ ok ]
* checking samba-3-gentoo-0.3.14.tar.bz2 ;-) ... [ ok ]
>>> Checking samba-3.0.23c.tar.gz's mtime...
>>> samba-3.0.23c.tar.gz has been updated; recreating WORKDIR...
>>> /usr/local/portage/net-fs/samba/samba-3.0.23c.ebuild has been updated; recreating WORKDIR...
>>> Unpacking source...
>>> Unpacking samba-3.0.23c.tar.gz to /var/tmp/portage/samba-3.0.23c/work
>>> Unpacking samba-3-gentoo-0.3.14.tar.bz2 to /var/tmp/portage/samba-3.0.23c/work
* Applying various patches (bugfixes/updates) ...
* 002_all_samba-3.0.x-smbumount-uid32.patch ... [ ok ]
* 003_all_samba-3.0.x-libdirsymlink.patch ... [ ok ]
* 004_all_samba-2.2.8-statfs.patch ... [ ok ]
* 010_all_samba-3.0.x-extrabins.patch ... [ ok ]
* 011_all_samba-3.0.x-subins-configure.patch ... [ ok ]
* 012_all_samba-3.0.x-subins-makefile.patch ... [ ok ]
* 030_all_samba-3.0.x-cross-compile.patch ... [ ok ]
* 040_all_samba-3.0.22-autoconf-2.60-fix.patch ... [ ok ]
* Done with patching
>>> Source unpacked.
>>> It appears that samba is already compiled; skipping.
>>> (clean to force compilation)
>>> It appears that samba has already been tested; skipping.
>>> Install samba-3.0.23c into /var/tmp/portage/samba-3.0.23c/image/ category net-fs
make: *** No rule to make target `install-everything'. Stop.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-07 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 13:23 [gentoo-user] More ebuild failing (install step) reader
2006-09-06 20:24 ` Richard Fish
2006-09-07 1:57 ` [gentoo-user] " reader
2006-09-07 5:34 ` Richard Fish
2006-09-07 15:59 ` reader
2006-09-07 19:03 ` Richard Fish
2006-09-07 19:25 ` reader [this message]
2006-09-07 19:28 ` reader
2006-09-08 7:08 ` Richard Fish
2006-09-08 19:01 ` reader
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=87odtr5vjf.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=gentoo-user@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