| View previous topic :: View next topic |
| Author |
Message |
statix
n00b
Joined: 27 Sep 2002
Posts: 8
Location: Tampa, FL
|
 Posted: Fri Sep 27, 2002 4:45 pm Post subject: Kde 3.1 beta build problems |
 |
|
Im trying to emerge in kde 3.1 beta. Problem is when it gets to kdelibs.
I get this output.
>>> Unpacking kdelibs-3.0.7.tar.bz2
/usr/sbin/ebuild.sh: cd: /var/tmp/portage/kdelibs-3.1_beta1/work/kdelibs-3.1_beta1: No such file or directory
/usr/sbin/ebuild.sh: cd: /var/tmp/portage/kdelibs-3.1_beta1/work/kdelibs-3.1_beta1/kio/misc/kpac: No such file or directory
>>> Source unpacked.
/usr/sbin/ebuild.sh: cd: /var/tmp/portage/kdelibs-3.1_beta1/work/kdelibs-3.1_beta1: No such file or directory
qtmt
ssl
cups
/usr/sbin/ebuild.sh: cd: /var/tmp/portage/kdelibs-3.1_beta1/work/kdelibs-3.1_beta1: No such file or directory
Its trying to build it in kdelibs-3.1_beta1 while its in kdelibs-3.0.7 instead. Ive tried making a link between the two changing the name but everytime I run emerge again it removes all my changes. I tried messing with the ebuild file but to no avail. Any help would be great. |
|
| Back to top |
|
 |
StrCrssd
n00b
Joined: 17 Apr 2002
Posts: 68
Location: McAllen, TX USA
|
| Posted: Fri Sep 27, 2002 9:54 pm Post subject: how to get kdelibs-3.1_beta1 to build... |
|
|
step
1) unmask kde 3.1 beta 1
2) emerge kdelibs, this ensures that all dep's are installed
3) go to the portage kdelibs directory and use the following command: "ebuild kdelibs-3.1_beta1 unpack"
4) go to the unpack (/var/tmp/portage) directory and key "ln -s kdelibs-3.0.7 kdelibs-3.1_beta1"
5) go back to the portage kdelibs and "ebuild kdelibs-3.1_beta1 compile && ebuild kdelibs-3.1_beta1 install"
6) emerge kde
That did it here...everything else was just fine.
_________________
StrCrssd
Give a man enough rope, he'll hang himself. Teach a man to make rope, he'll hang other people. |
|
| Back to top |
|
|
statix
n00b
Joined: 27 Sep 2002
Posts: 8
Location: Tampa, FL
|
| Posted: Fri Sep 27, 2002 10:14 pm Post subject: |
|
|
worked for me. Much thanks.
Also dont forget -
ebuild kdelibs-3.1_beta1 merge |
|
| Back to top |
|
|
Russki
Tux's lil' helper
Joined: 28 Apr 2002
Posts: 119
Location: Prague, Czech Republic
|
| Posted: Sat Sep 28, 2002 7:51 pm Post subject: Re: how to get kdelibs-3.1_beta1 to build... |
|
|
| StrCrssd wrote: | step
1) unmask kde 3.1 beta 1
2) emerge kdelibs, this ensures that all dep's are installed
3) go to the portage kdelibs directory and use the following command: "ebuild kdelibs-3.1_beta1 unpack"
4) go to the unpack (/var/tmp/portage) directory and key "ln -s kdelibs-3.0.7 kdelibs-3.1_beta1"
5) go back to the portage kdelibs and "ebuild kdelibs-3.1_beta1 compile && ebuild kdelibs-3.1_beta1 install"
6) emerge kde
That did it here...everything else was just fine. |
Hi,
when I do step 3, I get the first part of a. error message
| Code: |
>>> Unpacking kdelibs-3.0.7.tar.bz2
/usr/sbin/ebuild.sh: cd: /var/tmp/portage/kdelibs-3.1_beta1/work/kdelibs-3.1_beta1: No such file or directory
/usr/sbin/ebuild.sh: cd: /var/tmp/portage/kdelibs-3.1_beta1/work/kdelibs-3.1_beta1/kio/misc/kpac: No such file or directory
>>> Source unpacked.
|
After making simbolic link (step 4) and doing step 5, I get second part with "no configure script found" of that error message.
I tryed to rename kdelibs-3.1_beta1.ebuild to kdelibs-3.0.7.ebuild and it goes fine, but at one point I get another error about not finding
and it asks to check if I've got aRts compiled correctly.
i have no idea what else should I do.
Could someone help me out? Thanks
_________________
Facts are stupid things.
-Ronald Reagan
[img]http://www.danasoft.com/vipersig.jpg[/img] |
|
| Back to top |
|
|
Russki
Tux's lil' helper
Joined: 28 Apr 2002
Posts: 119
Location: Prague, Czech Republic
|
| Posted: Sat Sep 28, 2002 8:25 pm Post subject: |
|
|
Solved!
(Maybe I didn't understand step 4 correctly first, and It didn't work)
I did this, instead of step 4:
| Code: |
cd /var/tmp/portage/kdelibs-3.1_beta1/work/
mv kdelibs-3.0.7 kdelibs-3.1_beta1
|
After that I did step 5, with the aditional
| Code: |
&& ebuild kdelibs-3.1_beta1 merge
|
And it worked!
_________________
Facts are stupid things.
-Ronald Reagan
[img]http://www.danasoft.com/vipersig.jpg[/img] |
|
| Back to top |
|
|
justus
n00b
Joined: 16 Apr 2002
Posts: 48
|
| Posted: Sun Sep 29, 2002 10:39 am Post subject: Easier way maybe |
|
|
You can also try to edit the ebuild itself and add the following somewhere at the top (ie. after the homepage section or so):
| Code: | | S=${WORKDIR}/kdelibs-3.0.7 |
This should work to set it up to choose the correct directory to compile. This is exactly how they take care of the problem in the KDE-CVS version ebuilds.
Note: The other files should all work perfectly.
Hope that helps.
Justin T |
|
| Back to top |
|
|
justus
n00b
Joined: 16 Apr 2002
Posts: 48
|
| Posted: Sun Sep 29, 2002 11:51 am Post subject: Heya... |
|
|
Just got an email back from Dan (the kde ebuild maintainer) that stated that this is now fixed. I checked up on it and it should all work for you now after an emerge rsync.
I guess that this happened while Dan was preparing for the KDE 3.1 beta 2 series of ebuild... which I think will be coming soon.
Justin T |
|
| Back to top |
|
|
|
Desktop Environments
