| Re: Compilation Prob
Apr 6 2006 on content Kwlan |
Same here - slack 10.2. .configure works fine, but make bombs out with -
make[1]: Entering directory `/home/slight/downloads/kwlan-0.3.0'
configure.in:39: error: possibly undefined macro: AM_INIT_AUTOMAKE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.in:44: error: possibly undefined macro: AM_CONFIG_HEADER
configure.in:47: error: possibly undefined macro: AC_CHECK_COMPILERS
configure.in:48: error: possibly undefined macro: AC_ENABLE_SHARED
configure.in:49: error: possibly undefined macro: AC_ENABLE_STATIC
configure.in:54: error: possibly undefined macro: AM_KDE_WITH_NLS
configure.in:57: error: possibly undefined macro: AC_PATH_KDE
configure.in:62: error: possibly undefined macro: AC_CHECK_KDEMAXPATHLEN
make[1]: *** [configure] Error 1
make[1]: Leaving directory `/home/slight/downloads/kwlan-0.3.0'
make: *** [configure] Error 2
odd.... |
|  | | Re: with checkinstal
Oct 15 2005 on content Kompile |
I've taken a look at the source and it may be possible to incorporate checkinstall - the problem is the sheer number of options available with checkinstall. At the very least you would need to have a flag to determine which package you wish to create (RPM DEB or Slack), unless this can be determined logically at runtime. From looking at the TODO it looks like the author is planning on incorporating some ability to specify configure options, but I don't know where this stands. I may hack on this a bit (I agree that it is a wonderful idea and unfortunately one that is a long time coming) to see if I can add any functionality. After all, you have to love open source.
Another thought? How about exporting of Compiler flags prior to running configure? Can you imagine a few radio buttons where you can click what type of processor you have and if you want level 3 optimizations turned on? Or (*drools*) better yet distcc access where you can specify other machines to take part in the compile!!!!! |
| | | Fix for nvidia sys
Oct 9 2005 on content Crystal-GL |
For those of you running on Nvidia systems, your user needs to be part of the 'video' group in order for this to work correctly. All of the Nvidia device files (/dev/nvidia*) are permissioned to root and the group called video. This window decoration apparently needs access to these device files. I was getting the same error that everyone else is complaining about, Kcontrol crashes immediately with a segfault when trying to select this window deco. Just do this as root:
usermod -G video 'yourusername'
and you should be fine. A restart (of KDE at least) may be necessary, I can't remember. |
| | | Re: Tooo bad
Aug 30 2005 on content Crystal-GL |
As always, dig hard enough and you'll find the problem, and the answer. Turns out my user needed to be part of the 'video' group in-order for certain permissions related things to work.
I must say, CrystalGL rocks. Eye Candy galore! And despite the warnings to the contrary, it seems suprisingly stable.
Slight |
| | | Tooo bad
Aug 27 2005 on content Crystal-GL |
It bombs out on my Slack 10.1 install. Nvidia FX5700 Ultra. I've tried different versions of the Nvidia driver, back to 6229, and none work. Traceback always shows glcore as the culprit, but I'm at a loss as to what the issue may be. Oh well.
slight |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
