gforge port

Clement Laforet sheepkiller at
Tue Nov 25 11:01:06 PST 2003

On Tue, 25 Nov 2003 14:20:47 -0400 (AST)
"Marc G. Fournier" <scrappy at> wrote:

Hi Marc !

Thanks for the report !
> Several issues, apparently, with the gforge port ...
> www# make
> CONFIGURE_ARGS+=: not found
> *** Error code 127
> Stop in /usr/ports/www/gforge.
> removing the tab in front of hte line with --sys-name in it appears to
> fix that ...

Unfortunalty I noticed this this night, when I rebuilt my gforge test
jail. Since I don't know if portmgr would approuve the diff, I decided
to wait ports freeze end to propose the patch I working on. If portmgr
team is OK, I can submit a fix for 5.2.

> but then configure itself generates a bunch of 'test' related errors:
They are md5 program detection and harmless. The configure script is
just a "quick start", I choose to use it to permit users to easily get
familiar with gforge.


More information about the freebsd-ports mailing list