[gentoo-dev] what does manual "make" do, portage doesn't ?

[gentoo-dev] what does manual "make" do, portage doesn't ?

[Tibor Rudas]

Hello
I'm currently trying to write an ebuild for mpich (implementation
of MPI) and am stuck with a peculiar error:

when I manually unpack the source and do a
./configure
make
everything works OK...

..._but_:
if I do the same steps in an ebuild:
<snip>
src_compile() {
        ./configure || die

        make || die
}
<snip>
make stops with an "unknown target" error in some subdir.
If I then enter '/scratch/tmp/portage/mpich-1.2.4/work/mpich-1.2.4' and
type "make" it works fine.

I must admit though that the machine is still runing portage-1.9.11. I had to 
freeze a working setup since I need this machine up and running :)

any ideas?

regards tigor

Re: [gentoo-dev] what does manual "make" do, portage doesn't ?

[Todd Heim]

in you ebuild, instead of plain './configure'; try this:

./configure --host=${CHOST} || die

--
Todd Heim

On Tuesday 23 July 2002 10:42 am, Tibor Rudas wrote:
<snip>
> src_compile() {
>         ./configure || die
>
>         make || die
> }
> <snip>
> make stops with an "unknown target" error in some subdir.
> If I then enter '/scratch/tmp/portage/mpich-1.2.4/work/mpich-1.2.4' and
> type "make" it works fine.
...

Re: [gentoo-dev] what does manual "make" do, portage doesn't ?

[Doug Goldstein]

Todd Heim wrote:

>in you ebuild, instead of plain './configure'; try this:
>
>./configure --host=${CHOST} || die
>
>--
>Todd Heim
>
>On Tuesday 23 July 2002 10:42 am, Tibor Rudas wrote:
><snip>
>  
>
>>src_compile() {
>>        ./configure || die
>>
>>        make || die
>>}
>><snip>
>>make stops with an "unknown target" error in some subdir.
>>If I then enter '/scratch/tmp/portage/mpich-1.2.4/work/mpich-1.2.4' and
>>type "make" it works fine.
>>    
>>
>...
>_______________________________________________
>gentoo-dev mailing list
>gentoo-dev@gentoo.org
>http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
>
>  
>
The proper way would be

src_compile() {
    econf || die
    emake || die
}

-- 
Doug Goldstein
Developer (Laptops, WiFi, GCC-3.1)
Gentoo Linux                                http://www.gentoo.org/~cardoe/

Re: [gentoo-dev] what does manual "make" do, portage doesn't ?

[Tibor Rudas]

> >./configure --host=${CHOST} || die

Thanks for the help but I'm afraid this configure is quite nonstandard.
It sports a variety of options concerning MPI but lacks some of the more
common ones. Alas "--host" is one of them.

Alas Todd Heim's idea of using econf does  also not work since the configure
script does not recognize "--with-infodir"...

I think the problem is not in the configure process since I can do a manual
"make" in the build-dir. It is only when make is started by portage that it
aborts.
Another unusual thing is that when I do the manual make in the build-dir
and it completes sucessfully, I can't even build a binary package by
ebuild /usr/portage..../mpich-1.2.4.ebuild package because it starts
the whole configure/make process again (but this could be due to the
older portage version. I'll have to try this at home where I'm - almost - 
up to date :).

thanks
tigor

Re: [gentoo-dev] what does manual "make" do, portage doesn't ?

[Markus Krainer]

Tibor Rudas wrote:

> I think the problem is not in the configure process since I can do a manual
> "make" in the build-dir. It is only when make is started by portage that it
> aborts.

Maybe your MAKEOPTS (in /etc/make.globals) let make break.

> Another unusual thing is that when I do the manual make in the build-dir
> and it completes sucessfully, I can't even build a binary package by
> ebuild /usr/portage..../mpich-1.2.4.ebuild package because it starts
> the whole configure/make process again (but this could be due to the
> older portage version. I'll have to try this at home where I'm - almost - 
> up to date :).

Set FEATURES="noauto" in /etc/make.conf.

hth,
   Markus