Date: Tue, 18 Sep 2007 07:40:30 -0700 From: "David O'Brien" <obrien@FreeBSD.org> To: Sergey Matveychuk <sem@FreeBSD.org> Cc: cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/lang Makefile ports/lang/pcc Makefile distinfo pkg-descr ports/lang/pcc/files ccconfig.h f77config.h patch-configure patch-cpp-Makefile.in Message-ID: <20070918144030.GB67357@dragon.NUXI.org> In-Reply-To: <46EFC2E3.5000708@FreeBSD.org> References: <200709180248.l8I2mqbI049227@repoman.freebsd.org> <46EFC2E3.5000708@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 18, 2007 at 04:21:55PM +0400, Sergey Matveychuk wrote: > David E. O'Brien пишет: > >obrien 2007-09-18 02:48:52 UTC > > > > FreeBSD ports repository > > > > Modified files: > > lang Makefile > > Added files: > > lang/pcc Makefile distinfo pkg-descr > > lang/pcc/files ccconfig.h f77config.h patch-configure > > patch-cpp-Makefile.in > > Log: > > C99 modernization of the original Portable C Compiler by S. C. Johnson, > > written in the late 70's. > > Just wonder why commit an unbuildable port? Adding USE_GMAKE=yes line > fixes the problem. It built for me as I was testing(tm). It seems that with bmake it builds sometimes and not other times. There is nothing I see in pcc*/Makefile that is Gmake specific. In fact, if you 'make configure' and then (cd work/pcc* ; make) it builds fine. -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? Let's not play "Jeopardy-style quoting"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070918144030.GB67357>