On Fri, 28 Aug 2015, the wise A.J. "Fonz" van Werven wrote:
That *looks* like files being included in an incorrect order. Can you
send me a tarball of the port directory as you have it now? With any
luck I might be able to track down the problem more easily then.
Yes, this was it. Seems to bu
Marco Beishuizen wrote:
> Adding results in less, but fatal errors as well:
[snip]
> --- mem_freebsd.o ---
> In file included from mem_freebsd.c:18:
> /usr/include/vm/vm_param.h:94:2: error: unknown type name 'u_int'
> u_int xsw_version;
> ^
> /usr/include/vm/vm_param.h:95:2: er
On Fri, 28 Aug 2015, the wise A.J. "Fonz" van Werven wrote:
Hmm,
It seems like uses types such as u_int and dev_t without
including , which is where those types are defined. I'm not
sure whether that's a bug in FreeBSD or it's supposed to be this way,
but in the meantime, does it help if yo
Marco Beishuizen wrote:
> But the build stops with a lot of errors:
>
> ...
> In file included from mem_freebsd.c:18:
> /usr/include/vm/vm_param.h:94:2: error: unknown type name 'u_int'
> u_int xsw_version;
> ^
> /usr/include/vm/vm_param.h:95:2: error: unknown type name 'dev_t';
On Thu, 27 Aug 2015, the wise Kurt Jaeger wrote:
Hi!
There's the problem.
The tgz file does not unpack into a work/wmmemload-0.1.8/ directory,
instead it unpacks into something else.
Try to check this and fix it with some WRKSRC or similar variable.
Well, the good news is that I got somew
Hi!
> I'm trying to "revive" the wmmemload port because I'm using WindowMaker
> now as windowmanager, it looks like it's still being maintained upstream
> and, of course, I would like to use it.
>
> First difficult thing for me is writing the makefile. Right now it's like
> this:
[...]
> ...
>
Hi,
I'm trying to "revive" the wmmemload port because I'm using WindowMaker
now as windowmanager, it looks like it's still being maintained upstream
and, of course, I would like to use it.
First difficult thing for me is writing the makefile. Right now it's like
this:
...
# $FreeBSD$
PORT
