Makefile problems in /usr/ports

Jim Mock mij at soupnazi.org
Mon May 12 21:54:35 PDT 2003


On Monday, May 12, 2003, at 06:35  PM, Paul A. Hoadley wrote:
> On Mon, May 12, 2003 at 05:33:48PM -0700, Jim Mock wrote:
>
>> Two questions:
>>
>> 1) How old is your ports tree?
>
> I always do a cvsup on the subdirectory I'm building in, so it's
> pretty much up to date.  Here's an example of one that's failing:

Ok.

>> grep \$FreeBSD Makefile
> # $FreeBSD: ports/mail/p5-Mail-SpamAssassin/Makefile,v 1.43 2003/04/07
> 00:12:26 dougb Exp $
>
>> 2) Do you have make aliased to gmake in your shell or any other such
>> silliness?
>
> No:
>
>> which make
> /usr/bin/make
>
> Make just doesn't seem to like this kind of construct:
>
> .if ${PERL_LEVEL} < 500600
> RUN_DEPENDS+=   
> ${SITE_PERL}/Pod/Usage.pm:${PORTSDIR}/textproc/p5-PodParser
> BUILD_DEPENDS+= 
> ${SITE_PERL}/Pod/Usage.pm:${PORTSDIR}/textproc/p5-PodParser
> .endif
>
> It responds with:
>
> "Makefile", line 27: Malformed conditional (${PERL_LEVEL} < 500600)
> "Makefile", line 27: Need an operator
> "Makefile", line 30: if-less endif
> "Makefile", line 30: Need an operator
>
> It's a brand new /usr/bin/make built when I upgraded to 4.8-STABLE
> yesterday.

Odd.  I don't have the ports tree on my 4.8 system, but that port works 
on my 5.x machine (same $FreeBSD$ string).  Out of curiousity, what 
happens if you nuke the Makefile, cvsup, and try it again?  I don't 
think it'll help much, but it's worth trying, I suppose.

- jim

-- 
- jim mock  mij@{soupnazi|opendarwin}.org  jim@{bsdnews|FreeBSD}.org -
- editor in chief, BSD News: http://bsdnews.org  http://soupnazi.org -



More information about the freebsd-questions mailing list