Can't compile as user

Boyer · 11-26-2004, 03:42 AM

Hey! I just downloaded Konstruct (the KDE auto downloader, extractor, builder and installer) and tried to run it from my home dir. Everything extracted fine, but then I just get a Make Error 2 everytime it tries to compile, then it moves on to the next piece, and fails that etc until the end.

Then, I tried editing gar.conf.mk to my home dir, but running "make install" as root. Everything is working fine now. My user is in the root group (so user:root).

Any ideas why I can't compile as a user? This is annoying, because I'm going to have to do a "chown" when it's finished which will take forever...

coolpyrofreak · 11-26-2004, 03:49 AM

generally, you always have to install as root. that way, the program can be install system-wide for all users. try compiling and then installing as root, then run the program normally

Boyer · 11-26-2004, 04:01 AM

Well I do usually compile my stuff as root, and system wide, but in this case, I've had bad luck with getting new KDE version to work (I've botched my install twice in the last year trying to upgrade) so I want it just in my home to try it out, so it doesn't effect my system globaly forcing me to reinstall.

In the README of konstruct, it states that it will compile and install to you hom dir by default, and says nothing about being root. I son't understand why I can't run it as a user since it's not trying to write to any protected directories...

daihard · 11-26-2004, 05:09 AM

Quote:

Originally posted by Boyer
In the README of konstruct, it states that it will compile and install to you hom dir by default, and says nothing about being root. I son't understand why I can't run it as a user since it's not trying to write to any protected directories...

Yes, you should be able to build and install KDE as normal user using Konstruct. I just did that a few days ago, installing KDE 3.3.1 on my $HOME/kde3.3.1 directory (as defaulted in gar.conf.mk).

What kind of error messages do you get when you run Konstruct as yourself? Also, what does your gar.conf.mk say about your build directory? It should say:

Code:

prefix ?= $(HOME)/kde3.3.1

I added the following line to make sure the source code will be backed up within my home directory as well:

Code:

GARCHIVEDIR = $(HOME)/source/kde3.3.1

Boyer · 11-27-2004, 04:02 PM

Thanks for replying!

Yes, my PREFIX and GARCHIVEDIR are both the same as yours.

Here is an example error message:

==> Trying file//files/kdelibs-3.3.1.tar.bz2
make[3]: Entering directory `/home/boyer/Downloads/konstruct/kde/kdelibs'
make[3]: *** [file//files/kdelibs-3.3.1.tar.bz2] Error 1
make[3]: Leaving directory `/home/boyer/Downloads/konstruct/kde/kdelibs'

I have no idea what's going on here.

Further more, after I did do an install as root, I chmod'd it to my user, and copied it to my home dir. Then, I set the vars it says to set in the README. Then, when I restart X, and login as my user, the screen flashes, then X restarts. When I look at the console to find out what went wrong, it tells me it couldn't find libidin.so.11, even thouh it is in kde3.3.1/lib and that dir is in my LD_LIBRARY_PATH.

daihard · 11-27-2004, 05:31 PM

Quote:

Originally posted by Boyer
Yes, my PREFIX and GARCHIVEDIR are both the same as yours.

Here is an example error message:

==> Trying file//files/kdelibs-3.3.1.tar.bz2
make[3]: Entering directory `/home/boyer/Downloads/konstruct/kde/kdelibs'
make[3]: *** [file//files/kdelibs-3.3.1.tar.bz2] Error 1
make[3]: Leaving directory `/home/boyer/Downloads/konstruct/kde/kdelibs'

I have no idea what's going on here.

The first error is actually nothing special. It simply says that the source file for kdelibs is not found on your local system. What's strange is, konstruct should then go to your GARCHIVE directory to look for the source and, if that's unsuccessful too, then go out on the Internet and connect to an available mirror to download the source. Your errors seem to indicate that it just quits there. You do have an Internet connection, right?

Boyer · 11-30-2004, 04:32 AM

Yes, I do have a connection. Konstruct worked fine once run as root...

Either way, any idea why it won't work? The install I did as root I mean?

daihard · 11-30-2004, 05:12 AM

Quote:

Originally posted by Boyer
Yes, I do have a connection. Konstruct worked fine once run as root...

Either way, any idea why it won't work? The install I did as root I mean?

That's strange... I don't have libidin.so anywhere on my system, let alone my KDE/Qt library directories. Anyway... if I were you, I would make sure your "startkde" script is not overwriting your own KDE path setups. I am saying this because the "startkde" script that comes with my distro wipes out any user-defined KDEDIR and QTDIR and replaces them with the system default.

Does your KDE setup look like this?

Code:

export QTDIR=$HOME/kde3.3.1
export KDEDIR=$HOME/kde3.3.1
export KDEDIRS=$HOME/kde3.3.1
export PATH=$KDEDIR/bin:$PATH
export LD_LIBRARY_PATH=$HOME/kde3.3.1/lib:$LD_LIBRARY_PATH

Boyer · 11-30-2004, 06:05 AM

Yup, basicly like that, except $HOME is actually ~/ but same difference. Just uncase, I tried ut as $HOME, same results...

daihard · 11-30-2004, 08:21 PM

Quote:

Originally posted by Boyer
Yup, basicly like that, except $HOME is actually ~/ but same difference. Just uncase, I tried ut as $HOME, same results...

Actually, this just occurred to me. Did you say you were trying to run the new KDE as root, or as yourself? If you are running it as root, ~/ and $HOME will translate into /root/, not /home/username/.

Other than that, I am running out of ideas. Your konstruct directory (and all the subdirectories) belong to you and have the appropriate permissions to read/write/execute, correct?

Boyer · 12-01-2004, 02:49 PM

That's correct. After sucessful compilation as root, I did a recursive chmod on the entire kde3.3.1 dir, then copied it to /home/user. Then, set the variables. When I try to login as the user with the correct permissions, X just restarts itself, and presents me with the mdkkdm screen...

When I check the colsole for errors, it tells me that it can't find a lib (I think it's libidin.so.11), even though it's in my kde.3.3.1/lib, and that's in my LD_LIBRARY_PATH

I'm totally lost here.

Maybe it would help if I added the new KDE to my mdkkdm screen. What file do I edit to add another desktop?

daihard · 12-01-2004, 08:47 PM

Aah, hold on, looks like I do have libidn.so.11 in my kde3.3.1/lib directory.

Code:

[daihard:/home/daihard/kde3.3.1/lib]$ ls -l libidn*
-rw-r--r--    1 daihard  daihard    209312 Nov 22 20:17 libidn.a
-rwxr-xr-x    1 daihard  daihard       859 Nov 22 20:17 libidn.la*
lrwxrwxrwx    1 daihard  daihard        16 Nov 22 23:55 libidn.so -> libidn.so.11.5.3*
lrwxrwxrwx    1 daihard  daihard        16 Nov 22 23:55 libidn.so.11 -> libidn.so.11.5.3*
-rwxr-xr-x    1 daihard  daihard    202671 Nov 22 20:17 libidn.so.11.5.3*

Where and how exactly did you set your LD_LIBRARY_PATH?

Boyer · 12-02-2004, 01:51 AM

I've set my path as typing " LD_LIBRARY_PATH=/home/user/kde3.3.1/lib:$LD_LIBRARY_PATH" and also, added this to my .bashrc: "LD_LIBRARY_PATH=/home/user/kde3.3.1/lib:$LD_LIBRARY_PATH".

The lib is infact there, I checked, but it still says it isn't... It's really weird.

daihard · 12-02-2004, 03:19 AM

Quote:

Originally posted by Boyer
I've set my path as typing " LD_LIBRARY_PATH=/home/user/kde3.3.1/lib:$LD_LIBRARY_PATH" and also, added this to my .bashrc: "LD_LIBRARY_PATH=/home/user/kde3.3.1/lib:$LD_LIBRARY_PATH".

The lib is infact there, I checked, but it still says it isn't... It's really weird.

Assuming that your ~/.bashrc is included in your ~/.bash_profile, I *think* the problem is that you set the LD_LIBRARY_PATH variable without "exporting" it. I'd suggest that you try the following in your ~/.bashrc:

Code:

export LD_LIBRARY_PATH=/home/user/kde3.3.1/lib:$LD_LIBRARY_PATH

The keyword here is "export," which means you let the variable take effect outside the shell. I have a feeling that this will fix your problem. If not, hey, we can take it from there.

Boyer · 12-02-2004, 03:55 AM

Opps, my fault. The line from my .bashrc was supposed to be "export LD_LIBRARY_PATH=$HOME/kde3.3.1/lib:$LD_LIBRARY_PATH".

Here is the whole chunk of my .bashrc, whish is included in .bash_profile:

Code:

export QTDIR=$HOME/kde3.3.1
export KDEDIR=$HOME/kde3.3.1
export KDEDIRS=$HOME/kde3.3.1
export PATH=$KDEDIR/bin:$PATH
export LD_LIBRARY_PATH=$HOME/kde3.3.1/lib:$LD_LIBRARY_PATH

Weird, no?