SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hey guys,
Ok so I just figured out how to compile the source code in the konsole.
I cd to my directory under root
i did ./ configure
then when i said make it returned-
collect2: ld returned 1 exit status
make[1]: *** [httpd] Error 1
make[1]: Leaving directory `/root/Desktop/httpd-2.2.11'
make: *** [all-recursive] Error 1
what does this mean? Because when I do make install it also brings up the same error..
There should be some other message preceeding the ones you posted which would tell you what exactly it didn't like.
But it looks like you are compiling a newer apache if I am seeing it correctly. Are you simply trying to get the latest or is there some reason for not using a slackbuild script?
If you use a slackbuild script from http://slackbuilds.org/ it will solve many problems for you and keep your system consistent - which it will not be if you build directly as you are doing.
If you just want apache and not necessarily the absolute latest, then you will already have it with whatever version of Slackware you are running (which is...?), just in case you are not aware of it.
the last few compile lines would help .Just that there is an error is is of no help to us .It could be ANYTHING
was gcc linking???
was it building a *.o ???
we just do not have enough data too help .
and what "astrogeek" why are you not using the apache that is with Slackware ?
i am pulling out a crystal ball " konsole" and seeing KDE ,you might want to add this to your profile /sig.
The console printout says it contains too many images but if you want it go ahead and e-mail me at compgeek@frontiernet.net and I can e-mail it to you. I am thinking that I am going to try and use a different version just to see because I installed another program and it worked great... Kinda. The system did as it was supposed to but I am still learning and don't know how to quite make the change over from windows and mac to linux. Thanks
here is an example of what i mean .This is from a copy of celestia i broke
[???~]$ make
Code:
g++ -DHAVE_CONFIG_H -I. -I../.. -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -W -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -DNDEBUG -DNO_DEBUG -O2 -fno-exceptions -fno-check-new -O2 -Wall -ffast-math -fexpensive-optimizations -fomit-frame-pointer -DORBIT2=1 -pthread -I/usr/include/libgnomeui-2.0 -I/usr/include/libgnome-2.0 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0 -I/usr/include/orbit-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libart-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gconf/2 -I/usr/include/gtkglext-1.0 -I/usr/lib/gtkglext-1.0/include -I/usr/include/cairo -DLUA_VER=0x050100 -DCELX -MT formatnum.o -MD -MP -MF .deps/formatnum.Tpo -c -o formatnum.o formatnum.cpp
cc1plus: warning: command line option "-Wmissing-prototypes" is valid for Ada/C/ObjC but not for C++
cc1plus: warning: command line option "-Wmissing-prototypes" is valid for Ada/C/ObjC but not for C++
formatnum.cpp: In function ‘std::ostream& operator<<(std::ostream&, const FormattedNumber&)’:
formatnum.cpp:67: error: ‘memset’ was not declared in this scope
formatnum.cpp:92: error: ‘strstr’ was not declared in this scope
formatnum.cpp:94: error: ‘strlen’ was not declared in this scope
formatnum.cpp:101: error: ‘memcpy’ was not declared in this scope
formatnum.cpp:112: error: ‘CHAR_MAX’ was not declared in this scope
make[3]: *** [formatnum.o] Error 1
make[3]: Leaving directory `/home/Download/celestia-1.5.1/src/celutil'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/Download/celestia-1.5.1/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/Download/celestia-1.5.1'
make: *** [all] Error 2
the error gives the file and line there error is in
Code:
formatnum.cpp:67: error: ‘memset’ was not declared in this scope
I am thinking that I am going to try and use a different version just to see because I installed another program and it worked great... Kinda. The system did as it was supposed to but I am still learning and don't know how to quite make the change over from windows and mac to linux. Thanks
It is good that you want to learn how to compile from source, but there is much more to it than...
Code:
./configure
./make
./make install
That will mostly lead you to frustration and disappointment. To use the example at hand, if you do that with apache on a working Slackware system you will likely end up breaking your system and still not have a working apache server - even if you satisfy all the compile errors. Then you may end up asking why Slackware is so screwed up? Kind of like putting high octane gas in your new Mercedes, then asking why it doesn't run!
On any system you need to learn how the basic system works, including it's package system, locations of common files and libraries... how things are done on THAT system. Then if you compile and install within that system's requirements, and philosophy you will reach Nirvana - particularly on Slackware!
Making the change from some lesser operating system invloves learning the how and the why.
A good place to start is of course the Slackware web site and explore the various text docs on your installation media. Also be sure to read Slackbook.
In particular - read all you can about the Slackware package tools and pay particular attention to the why of it all as you do - not just the how! Then visit Slackbuilds.org and have a look at how some of the build scripts work. In no time you will be compiling everything from source - but in a good way!
When I go to install a SlackBuild file, using chmod -x or not, then ./xxxxxxxxx.SlackBuild I get a Cannot Install, Permission Denied. I am logged in a Root, why would this be?
Even if you are using a SlackBuild script, looking at the output of "./configure --help" yields A LOT of helpful options to pass prior to "making" the program.
Code:
$ ./configure --help | less
The "make" is probably failing because you are trying to compile a portion of the program that requires a library you do not have.
You will also need to know the available options for "configure" if you're making a SlackBuild script.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.