• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How long it take KDE3 to compile for you?

Poontos

Platinum Member
My PIII866 laptop started at 4PM EST, now it is 10:47PM EST, still going...

Did I do something wrong? 🙂

cd /usr/ports/x11/kde3
make install clean



 
Originally posted by: BingBongWongFooey
I've never compiled it, though I installed it once 😛
Correct me if I am wrong, but when the "make" command is executed, there is some kind of compiling going on?

How did you go about installing it, and on what OS?
 
Originally posted by: Poontos
Originally posted by: Nothinman
I wouldn't know, I have people that do that sort of tedious thing for me =)
Thanks for replying to my thread, but one has to assume this was just a post-count-increase reply? :brokenheart:

Who cares about post count? This isn't ATOT 🙂

Correct me if I am wrong, but when the "make" command is executed, there is some kind of compiling going on?

How did you go about installing it, and on what OS?

"make" looks in the file "Makefile" in the current directory for instructions about what to do, theoretically you could use it for almost anything. Most of the time, yes, it's used to compile stuff. The way to tell that stuff is being compiled is when you get stuff like:

gmake[2]: Entering directory `/usr/Pkgsrc/sysutils/fam/work/fam-2.6.9/libfam'
/bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\"/usr/pkg/etc/fam.conf\" -I/usr/pkg/include -O2 -I/usr/pkg/include -c Client.c++
mkdir .libs
c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\"/usr/pkg/etc/fam.conf\" -I/usr/Pkgsrc/sysutils/fam/work/.buildlink/include -O2 -I/usr/Pkgsrc/sysutils/fam/work/.buildlink/include -c Client.c++ -fPIC -DPIC -o .libs/Client.o
c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\"/usr/pkg/etc/fam.conf\" -I/usr/Pkgsrc/sysutils/fam/work/.buildlink/include -O2 -I/usr/Pkgsrc/sysutils/fam/work/.buildlink/include -c Client.c++ -o Client.o >/dev/null 2>&1
/bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\"/usr/pkg/etc/fam.conf\" -I/usr/pkg/include -O2 -I/usr/pkg/include -c fam.c++
c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\"/usr/pkg/etc/fam.conf\" -I/usr/Pkgsrc/sysutils/fam/work/.buildlink/include -O2 -I/usr/Pkgsrc/sysutils/fam/work/.buildlink/include -c fam.c++ -fPIC -DPIC -o .libs/fam.o
c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\"/usr/pkg/etc/fam.conf\" -I/usr/Pkgsrc/sysutils/fam/work/.buildlink/include -O2 -I/usr/Pkgsrc/sysutils/fam/work/.buildlink/include -c fam.c++ -o fam.o >/dev/null 2>&1
/bin/sh ../libtool --mode=link c++ -O2 -I/usr/pkg/include -Wl,-R/usr/pkg/lib -L/usr/pkg/lib -o libfam.la -rpath /usr/pkg/lib -export-symbols fam.sym Client.lo fam.lo -lstdc++
c++ -shared -nostdlib /usr/lib/crtbeginS.o .libs/Client.o .libs/fam.o -L/usr/Pkgsrc/sysutils/fam/work/.buildlink/lib -lstdc++ -lm -lgcc_pic /usr/lib/crtendS.o -Wl,-R/usr/pkg/lib -Wl,-soname -Wl,libfam.so.0 -Wl,-retain-symbols-file -Wl,fam.sym -o .libs/libfam.so.0.0
(cd .libs && rm -f libfam.so.0 && ln -s libfam.so.0.0 libfam.so.0)
(cd .libs && rm -f lib

etc etc.

And I installed it once on debian, just with binary packages.
 
Back
Top