Mathieu Sauve-Frankel wrote:
You don't have to do ridiculous stuff like that. USE_GMAKE exists for
a reason.
Thanks for the tip. Playing with my first attempt.
--
Jack J. Woehr
Director of Development
Absolute Performance, Inc.
[EMAIL PROTECTED]
303-443-7000 ext. 527
On Thu, Dec 21, 2006 at 04:46:12PM -0700, Jack Woehr wrote:
> Marc Espie wrote:
> >So, you probably have a cvs conflict in your Makefile...
> >
> Oh, way stupider than that. I'd put Gnu make in my path today
> special to work on a port.
You don't have to do ridiculous stuff like that. USE_GMAKE
Marc Espie wrote:
So, you probably have a cvs conflict in your Makefile...
Oh, way stupider than that. I'd put Gnu make in my path today
special to work on a port.
--
Jack J. Woehr# "If your neighbor prays too loud
http://www.well.com/~jax # in church, go home and lock your
http
On Thu, Dec 21, 2006 at 03:21:42PM -0700, Jack Woehr wrote:
> Just updated to current (kernel, build, ports)
>
> Now in /usr/ports:
>
> $ make search key=rpm
> Makefile:11: *** missing separator. Stop.
Works For Me:
$ sysctl kern.version
kern.version=OpenBSD 4.0-current (GENERIC) #0: Tue Dec 1
On Thu, Dec 21, 2006 at 03:21:42PM -0700, Jack Woehr wrote:
> Just updated to current (kernel, build, ports)
>
> Now in /usr/ports:
>
> $ make search key=rpm
> Makefile:11: *** missing separator. Stop.
So, you probably have a cvs conflict in your Makefile...
(make search key=rpm works for me)
Just updated to current (kernel, build, ports)
Now in /usr/ports:
$ make search key=rpm
Makefile:11: *** missing separator. Stop.
--
Jack J. Woehr# "If your neighbor prays too loud
http://www.well.com/~jax # in church, go home and lock your
http://www.softwoehr.com # smokehouse."