• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Kahakai 0.5.1 is out!

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Originally posted by: n0cmonkey

I haven't. But I can definitely tell that this project is very linux oriented.

-1 Troll 😛

There are a few issues with assuming gnu sed and grep and stuff like that (which pisses me off a lot - they were all done by one person, who apparently ignores non-gnu utils for the most part), but people seem to be getting by alright on bsd with no big complaints.

I think the rest of your issues are due to kahakai being bleeding edge, and bsds tend not to be 😉
 
Originally posted by: BingBongWongFooey
Originally posted by: n0cmonkey

I haven't. But I can definitely tell that this project is very linux oriented.

-1 Troll 😛

Bull. As illustrated by the second part of your post.

There are a few issues with assuming gnu sed and grep and stuff like that (which pisses me off a lot - they were all done by one person, who apparently ignores non-gnu utils for the most part), but people seem to be getting by alright on bsd with no big complaints.

Assuming gnu tools sounds pretty linux oriented to me. I've had trouble getting this thing installed at EVERY step so far. Maybe it's for programmers only though.

I think the rest of your issues are due to kahakai being bleeding edge, and bsds tend not to be 😉

If you say so. Some of the new features in some of the BSDs seem pretty "bleeding edge" to me.
 
Originally posted by: n0cmonkey
Originally posted by: FelixDeKat
Just stick with whole hawg UNIX.

Want to explain what that document has to do with this?

Well you stated that " Getting it to work under OpenBSD is a PITA. And probably not worth the trouble, since I don't know python. "

Therefore I stated the above. Next ?
 
Originally posted by: FelixDeKat
Originally posted by: n0cmonkey
Originally posted by: FelixDeKat
Just stick with whole hawg UNIX.

Want to explain what that document has to do with this?

Well you stated that " Getting it to work under OpenBSD is a PITA. And probably not worth the trouble, since I don't know python. "

Therefore I stated the above. Next ?

Maybe I'm dumb, but I still don't understand the correlation. Maybe I need to reread that file...
 
Originally posted by: n0cmonkey
Originally posted by: BingBongWongFooey
Originally posted by: n0cmonkey

I haven't. But I can definitely tell that this project is very linux oriented.

-1 Troll 😛

Bull. As illustrated by the second part of your post.

Lighten up. 🙂 I think I just have a very negative impression of "linux oriented". I prefer to avoid it.

There are a few issues with assuming gnu sed and grep and stuff like that (which pisses me off a lot - they were all done by one person, who apparently ignores non-gnu utils for the most part), but people seem to be getting by alright on bsd with no big complaints.

Assuming gnu tools sounds pretty linux oriented to me. I've had trouble getting this thing installed at EVERY step so far. Maybe it's for programmers only though.
But that's really the only thing. You could say that the build system is a little linux-oriented, but even that's stretching it, since 99% of it isn't. Those few things do need to be cleared up, though (I actually just fixed one, need to figure out what the deal is with another).

I think the rest of your issues are due to kahakai being bleeding edge, and bsds tend not to be 😉

If you say so. Some of the new features in some of the BSDs seem pretty "bleeding edge" to me.

In the context of a window manager, not in any other areas or even the OS in general.
 
Originally posted by: BingBongWongFooey
Originally posted by: n0cmonkey
Originally posted by: BingBongWongFooey
Originally posted by: n0cmonkey

I haven't. But I can definitely tell that this project is very linux oriented.

-1 Troll 😛

Bull. As illustrated by the second part of your post.

Lighten up. 🙂 I think I just have a very negative impression of "linux oriented". I prefer to avoid it.

There are a few issues with assuming gnu sed and grep and stuff like that (which pisses me off a lot - they were all done by one person, who apparently ignores non-gnu utils for the most part), but people seem to be getting by alright on bsd with no big complaints.

Assuming gnu tools sounds pretty linux oriented to me. I've had trouble getting this thing installed at EVERY step so far. Maybe it's for programmers only though.
But that's really the only thing. You could say that the build system is a little linux-oriented, but even that's stretching it, since 99% of it isn't. Those few things do need to be cleared up, though (I actually just fixed one, need to figure out what the deal is with another).

Well something is wrong here since the ./configure told me to run make and make tells me that:
./src/wrapper.i:48: Unable to find 'list'
../src/wrapper.i:49: Unable to find 'map'
../src/wrapper.i:50: Unable to find 'set'
 
Originally posted by: n0cmonkey

Well something is wrong here since the ./configure told me to run make and make tells me that:
./src/wrapper.i:48: Unable to find 'list'
../src/wrapper.i:49: Unable to find 'map'
../src/wrapper.i:50: Unable to find 'set'

What version of swig? I can't imagine your c++ compiler really doesn't have those..

That causes the build to die? Lots of warnings in the swig generated files is normal.
 
Originally posted by: BingBongWongFooey
Originally posted by: n0cmonkey

Well something is wrong here since the ./configure told me to run make and make tells me that:
./src/wrapper.i:48: Unable to find 'list'
../src/wrapper.i:49: Unable to find 'map'
../src/wrapper.i:50: Unable to find 'set'

What version of swig? I can't imagine your c++ compiler really doesn't have those..

That causes the build to die? Lots of warnings in the swig generated files is normal.

swig-1.3.17. I had read that 1.3.17 and 1.3.16 were ok, but bleeding edge copies were not.

Here is the end of the "gmake" I type in:
`eg++ -v .dummy.cpp 2>&1 | perl -e 'undef$/;$_=<>;s/^.*?#include <\.\.\.>[^:]*🙁(?:\n [^\n]*)*)\n.*$/$1/s;s/\n / -I/gs;print'` \
-o swig_wrapper_python.cc ../src/wrapper.i
../src/wrapper.i:48: Unable to find 'list'
../src/wrapper.i:49: Unable to find 'map'
../src/wrapper.i:50: Unable to find 'set'
gmake[2]: *** [swig_wrapper_python.cc] Error 1
gmake[2]: Leaving directory `/home/n0c/kahakai-0.5.1/src'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/home/n0c/kahakai-0.5.1/src'
gmake: *** [all-recursive] Error 1


I am guessing that is the error that kills this.

EDIT: stupid package problem. Not everything gets installed in the egcs package.
 
Back
Top