You are not logged in.

SuSe paths are messed up!

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Franklin DeMatto

Unregistered

1

Monday, July 14th 2003, 4:31am

SuSe paths are messed up!

Hi. I'm checking out SuSE now. From the desktop, it seems great. Very sharp KDE. But the second I fire up a good ol' console (konsole?), as far as I can tell, everything is messed up.

SuSE says in its docs that it generally is File System Hierarchy compliant (http://www.pathname.com/fhs/). I found the opposite to be true: files are tucked away in directories like /usr/lib/qt3/etc/ and /usr/lib/qt3/bin/ (for a whole bunch of things, not just Qt). This makes console use next to impossible - the most basic tools are outside the path, etc.

Even trying to do simple things like compile prewritten software gave errors. I had to fiddle around to get things to compile properly, finding the libs and includes. (I couldn't cajole the Perl OpenGL module to find the GL libraries.)

Why is it like this? More importantly, is there any solution? As it stands now, SuSE is a great distro if you don't want to to take your fingers off the mouse, but if you want to do some ol' time Linux hacking (things as simple as basic compilation), you're in for a lot of frustration.

Can anyone help me out?

Rinse

Professional

Posts: 797

  • Send private message

2

Tuesday, July 29th 2003, 8:57am

Your problem is kinda odd.
on my system, all directories are located in SuSE's PATH, so software compiles without any problems.

Did you check the library paths on SuSE to see if anything is wrong?

Kind regards, Rinse
Help mee om KDE 3.5.5 in het Nederlands te vertalen