public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: reader@newsguy.com
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: More ebuild failing (install step)
Date: Thu, 07 Sep 2006 10:59:35 -0500	[thread overview]
Message-ID: <87r6yn8y6w.fsf@newsguy.com> (raw)
In-Reply-To: 7573e9640609062234o4094da1ex74d4a3c4d90f4d6e@mail.gmail.com

"Richard Fish" <bigfish@asmallpond.org> writes:

>> In my meager knowledge Makefile.in is used to create a Makefile but
>> which one guides the overall build?
>>
>> ./pcp/Makefile
>> ./source/tdb/Makefile
>> ./source/iniparser/test/Makefile
>> ./source/iniparser/Makefile
>> ./source/Makefile.in
>> ./examples/VFS/Makefile.in
>
> ...but it seems you ran this between unpack and compile steps?
> Because you have no source/Makefile.
>

No, I ran find between `compile' and `install', and that must be the
problem.  ./source/Makefile disappears when I run `ebuild install'. Checking now:

I've stepped thru these:

  digest
  unpack
  compile

And now there is a Makefile in source
find . -iname '*makefile*'
./pcp/Makefile
./source/tdb/Makefile
./source/Makefile
./source/iniparser/test/Makefile
./source/iniparser/Makefile
./source/Makefile.in
./examples/VFS/Makefile.in

[...]

But once I've run `ebuild install' (and it fails as posted) it
disappears: 
find . -iname '*makefile*'
./pcp/Makefile
./source/tdb/Makefile
./source/iniparser/test/Makefile
./source/iniparser/Makefile
./source/Makefile.in
./examples/VFS/Makefile.in
./examples/pdb/Makefile

[...]

I used the samba-3.0.23a.ebuild now on portage as base.  The only
changes I've made were to illimintate torture

These two lines at line 127

  #     einfo "make rpctorture"
  #     emake rpctorture || ewarn "rpctorture didn't build"

And the change you suggested at line 148 

<       make DESTDIR=${D} install-everything || die
---
>       make DESTDIR=${D} install || die

I've since restored intall-everything

 I've diffed my ebuild against the one now on 
  portage samba-3.0.23a.ebuild for your convenience and inlined the
  resulting patch derived with diff -u (unified style output)

But first, the reason for commenting out those two line about torture
was because the compile phase broke on compiling torture and I
couldn't determine why.  I was told torture was an antiquated and
little used tool so decided to just try to leave it out.

Also the full edited ebuild is here:
  http://www.jtan.com/~reader/samba-3.0.23c.ebuild
but a diff is posted below.

diff -u samba-3.0.23a.ebuild samba-3.0.23c.ebuild
========================================================
--- samba-3.0.23a.ebuild        2006-09-07 09:49:39.000000000 -0500
+++ samba-3.0.23c.ebuild        2006-09-07 10:43:38.000000000 -0500
@@ -123,8 +123,8 @@
        emake proto || die "SAMBA make proto error"
        emake everything || die "SAMBA make everything error"
 
-       einfo "make rpctorture"
-       emake rpctorture || ewarn "rpctorture didn't build"
+#      einfo "make rpctorture"
+#      emake rpctorture || ewarn "rpctorture didn't build"
 
        if use python ; then
                python python/setup.py build

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-09-07 16:11 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 [this message]
2006-09-07 19:03         ` Richard Fish
2006-09-07 19:25           ` reader
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=87r6yn8y6w.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