| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Comments:
<0> (change my QTDIR path etc?)
<1> up to you
<0> benJIman|tov: isn't any call for qt3 gonna want that 64-bit directory?
<1> only when running the configure scripts
<0> benJIman|tov: does suse use QTDIR for many other things?
<0> actually nevermind; I don't mind typing that on each compile, really
<1> I just alias it to qtconfigure
<0> benJIman|tov: would that be complex?
<0> why oh why doesn't yast show the download rate? :P That does get annoying :D
<2> i havent had to do that
<2> i compile lots of qt apps on my 64bit box, not as many as ben...
<3> and prolly not as many as me ;)
<1> francis_:the package manage is being improved
<3> brb
<1> it has been mainly used for installing from dvd / local network sources
<0> benJIman|tov: cool stuff! Look forward to it. I'm coming from debian, so it's more a case of things being different rather than inferior/superior, I'd say, on the whole.
<1> times have changed
<0> indeed
<1> francis_: you might find smart nice
<0> benJIman|tov: another package manager?
<0> I've been playing around with suse's apt lately
<1> I wouldn't use suse's apt
<1> smart isn't bad though
<0> it's very good in some ways (build-dep seems to generally work, on the whole, which is very nice)
<0> cool, I'll check it out now
<1> http://labix.org/smart, it's in the yaloki's yast repo
<0> (well, as soon as the current install stuff finishes :) )
<0> benJIman|tov: is his the guru one?
<1> francis_: ues
<0> cool. Very nice of him to do all that packaging :)
<1> and there's y2pmsh of course
<0> yup, tried that; not too bad. CLI is nice for speediness.
<0> yast -i works well though too
<1> y2pmsh is handy with the 10.1 betas as it's pretty much the only working package manager
<4> benJIman|tov: pff :)
<0> heh. Quite happy I didn't dive straight into 10.1 now =). Nice to see it in stability
<4> benJIman|tov: I am the package manager :) rpm rulez :)
<1> [daemon]: I was stuck with rpm -Uhv and wget and a bash script as my package manager for a while :)
<4> :)
<4> benJIman|tov: don't forget xargs :)
<0> hehe
<4> benJIman|tov: go and ask the desktop team
<1> [daemon]: where?
<1> one of the lists?
<4> benJIman|tov: http://freedesktop.org/wiki/
<4> hey Suit
<5> lo [daemon]
<5> [daemon]: how is life?
<6> benJIman|tov: Outrule linux? *dives*
<1> FauxFaux: wow you're attatched to your screen
<1> has opera broken again?
<6> Lies, Opera is perfect!
<7> hola
<7> necesito ayuda soy novato
<7> en linux
<7> #suse-es
<8> Has anyone ever used mocp?
<9> who ever said updating all sources would take forever was right....about 4 hrs to go..out of 5
<8> lol
<10> hehehe
<9> at least im not on a dialup connection...that would take forever
<11> Hey
<0> what packages do I need for the kde headers (trying to install a windeco for KDE)??
<0> I already have kdelibs3/base3-devel
<12> questoin: what RPMs do I need (packman or whatever) to enable support for mp3 in rhythmbox?
<13> moin.
<0> benJIman|tov: any idea? :) What packs would I need for the KDE includes?
<0> I already have the base/libs respective devel files
<1> kde devel
<1> what can't it find?
<1> you have the --prefix=/opt/kde3 ?
<0> kde-devel doesn't seem to exist
<0> "in the prefix, you've chosen, are no KDE libraries installed. This will fail."
<1> you have kdebase3-devel installed?
<0> yup
<1> and kdelibs I ***ume
<0> 'course
<1> and kdelibs3-devel?
<0> benJIman|tov: ah, I see that only 3.4.2 -devel files are available in the repositories I have
<0> (while I'm running 3.5 -- do you think that could be the problem?)
<1> yes
<0> SuSEhelp: updatekde
<14> http://susewiki.apanela.com/tutorials:updatekde
<0> indeed it isn't
<0> I'll use that, cool.
<0> actually, that's no good. I'm not on i386
<0> ia64 repo there I see anyhow, excellent
<15> hey, kkathman
<16> hi there hussam!!
<17> does anyone have an idea on this - i shutdown a machine with shutdown -r now, and left it for a bit, now i can sttill ping it, but ssh requests are refused
<17> put the machine has been pingable the whole time, as though it never shut down at all
<18> possibly
<17> can i force a shutdown?
<17> from outside the machine :)
<0> benJIman|tov: hm, it fails again even though I have current versions of both
<1> what are you building?
<0> benJIman|tov: a kde windeco
<1> link?
<0> benJIman|tov: http://www.kde-look.org/content/show.php?content=32099
<1> builds here
<1> compiled
<0> benJIman|tov: amd64 too?
<1> you must be missing [the correct version of] a devel package
<1> yes
<17> any ideas anybody?
<1> francis_: you're using ./configure --prefix=/opt/kde3 --with-qt-dir=/usr/lib64/qt3 --with-qt-libraries=/usr/lib64/qt3/lib64 --enable-libsuffix=64
<0> benJIman|tov: but what other dev files would it require? I have both the respective base and libs ones
<1> ?
<0> benJIman|tov: no libsuffix, no. WIll try that.
<1> that should do if they're the appropriate versions
<1> ah libsuffix is important
<18> libwtf?
<1> --enable-libsuffix=64, very useful for 64bit , too bad most gtk apps ignore it :(
<0> apologies; I wasn't aware of it.
<18> if everything goes well, they should not need any libsuffix parameter at all, but be well with --libdir
<0> benJIman|tov: worked like a charm now :). Thanks again.
<0> so many extra options required for suse building!
<1> jengelh: libsuffix makes it look in all the lib64 dirs rather than just lib
<1> gtk stuff always just fails to build unless you edit the build scripts usually
<0> that really ****s; damn gtk.
<1> well the big apps like gaim and such work fine
<1> but too many need manually editing build scripts for 64bit still
<8> anyone have any idea where to start looking for the reason portmap fails to start?
<19> Wampyre: start it from konsole
<19> Wampyre: or what ever console you use :_p
<8> Fri13, I'm running at runlevel 3.
<8> At startup, it says failed, if I try /etc/init.d/portmap start, it fails
<8> if I do portmap -d, nothing happens, it just sits there doing nothing
<19> Wampyre: have you checked /var/log ?
<8> messages shows nothing
<19> Wampyre: then you should ask someone else who would know better....
<8> k
<20> is there any way to create a bootable thumbdrive image to install suse from a network source without having to burn a cd/dvd ?
<1> in theory
<1> you could also netboot it
<20> how do I do that? I can't burn anything onto a CD or dvd as my drive is messed up
<1> to netboot you'd need to set up a pxe boot server
<1> you might be able te to set up a flash drive bootable thing with dd, not usre
<1> or you could use the floppy images if you like old technology
<20> that requires another computer running linux to do? (the pxe boot server)
<1> or you could pick up a boxed set which has pre-burned cds
<1> yes
<20> can I use an older suse install cd to launch the new install?
<1> not a good idea
Return to
#suse
or
Go to some related
logs:
gentoo rev-rebuild
mount cifs non root ubuntu
www.goobar.com
gumby netstorm
#perl
#math
#math
iptables: Unknown error 4294967295 connlimit fedora
fc3 kernel-module-qc-usb
gnomepeercast
|
|