Compatibility of SlackBuilds..

Alexvader · 10-22-2009, 09:48 AM

Hi Forum,

I Tried to compile BRL-CAD, latest version under Slackware 64 13.0.

Had to enable some stuff, seems like the autoconf could not find the development files for Tcl, Tk, and some more stuff...

#1 ) Do they exist in Slackware 13? ( assuming that I made a complete install, 4.8 gb... Do they live in a Standard prefix, like /usr/local/lib... /usr/include ...?

Anyway, i enabled ( Since The sources of BRL-Cad have its own versions of Tcl and Tk included ) --with-tcl --with-tk --enable-optimize --with-X11 --with-ogl in the configure, it created my makefle, and compiled and installed without any problem ;

The default prefix is /usr/brlcad/...

So, when I type /usr/brlcad/bin/mged ( this is a 3D geometry editor/solid Modeler ) I get these two Tcl windows, one holding a text interface for CLI, and the other holding the output of the framebuffer which contains my 3d models...

My two issues are :

If I drag another window over the framebuffer window, it gets corrupted, and wiped out, but when I use some commant over the framebuffer window it gets restored again... It is not persistent...

What can I do to avoid this... ?

Does not seem like any issue with the graphics driver, since, using an ATI Radeon X3200, it supports the full resolution of my monitor... 1280x800, glxgears is ok, KDE4 behaves normally...

What can this be... ?

I Have found a previous release of this package as a SlackBuild...
http://www.slacky.itwww.slackbuilds....office/brlcad/

It is fo Slackware 12, can it be installed for Slackware 64 13... ?

Thanks in advance

BRGDS

Alex

slackd · 10-22-2009, 09:55 AM

Quote:

Originally Posted by Alexvader

It is fo Slackware 12, can it be installed for Slackware 64 13... ?

Thanks in advance

BRGDS

Alex

i had a look at the slackbuild..should work on slack13 x64..just need to change the ARCH.

shadowsnipes · 10-22-2009, 11:37 AM

Also, you might find http://slackbuilds.org/howto/versions/ of some use. It does not talk about using the SlackBuilds on newer SW versions, but it still gives some helpful details of the differences.

#1) Do they exist?
tcl

Code:

$> ls /var/log/packages/tcl*
 16K /var/log/packages/tcl-8.5.5-i486-1  4.0K /var/log/packages/tclx-8.4-i486-2

If you do not have a good idea of what package name a file is from you can do something like

Code:

$> grep tclsh /var/log/{packages,scripts}/*
/var/log/packages/tcl-8.5.5-i486-1:usr/man/man1/tclsh.1.gz
/var/log/packages/tcl-8.5.5-i486-1:usr/bin/tclsh8.5
/var/log/scripts/tcl-8.5.5-i486-1:( cd usr/bin ; rm -rf tclsh )
/var/log/scripts/tcl-8.5.5-i486-1:( cd usr/bin ; ln -sf tclsh8.5 tclsh )

What's in the package(s)?

Code:

less /var/log/packages/tcl*

Files that are symlinks are usually created by doinst.sh file instead upon package installation. A record of this is under /var/log/scripts.
So, you might want to also do

Code:

less /var/log/scripts/tcl*

tk

Code:

$> cat /var/log/{packages,scripts}/tk*

What about for SW versions you don't have installed?
Slackware Package Browser - Note: the browser is currently down.

Some useful scripts for package information

Oh, and unfortunately, ATI drivers on Linux can be hit or miss. I've had better experiences with Nvidia. You might want to try disabling Composite extensions and/or turning off XLIB_SKIP_ARGB_VISUALS.

Here's how to do the latter.

Code:

$> cat /etc/profile.d/x-fix.sh 
#!/bin/sh
# mentioned in CHANGES_AND_HINTS.TXT
export XLIB_SKIP_ARGB_VISUALS=1

(file is executable and won't take effect until the next logon.)