[SOLVED] problem with "./configure --prefix=usr/local/apache --enable-module=so"
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
problem with "./configure --prefix=usr/local/apache --enable-module=so"
Using Ubuntu 9.04 on a partitioned hard drive installation.
I'm trying to set up Apache as part of a LAMP setup. My book told me to use that command as part of compilation process, right before "make", but when I run that command, I get this:
Warning: Your 'echo' command is slightly broken.
It interprets escape sequences per default. We already
tried 'echo -E' but had no real success. If errors occur
please set the SEO variable in 'configure' manually to
the required 'echo' options, i.e. those which force your
'echo' to not interpret escape sequences per default.
using installation path layout: Apache (config.layout)
Obviously, I'm a Linux newbie. I have not a clue what all that means, so any advice will be greatly appreciated.
Warning: Your 'echo' command is slightly broken.
It interprets escape sequences per default. We already
tried 'echo -E' but had no real success. If errors occur
please set the SEO variable in 'configure' manually to
the required 'echo' options, i.e. those which force your
'echo' to not interpret escape sequences per default.
using installation path layout: Apache (config.layout)
Escape-Sequence: basically, you can give certain commands "special characters" if you want to do things like display color, or in some cases call variables. In this case the "echo" command (which just outputs whatever you give it to STDOUT) that is available on your system doesn't act the way that the ./configure script would like.
Normally this isn't a big deal, as most project's ./configure scripts are rather robust (heck, Apache will compile on almost anything).
Quote:
P.S.- Is my Apache corrupted?
No, as long as you downloaded the file from Apache, and verified either the MD5 or the SHA-1 sum, you should be good.
(To do that, run md5sum -b filename.of.the.tar.gz.you.downloaded and verify the alphanumeric string it gives you with the MD5 listed on the website for the download).
Either way, you can typically disregard little things like the "echo" error and continue along with your build process. It's typically not a show-stopper.
Try following
root#rm -f /bin/sh
root#ln -s /bin/bash /bin/sh
I would strongly advise against doing that. The problem the Original Poster is having is not related to a shell call, in most Linux flavors, "echo" is a binary living in /usr/bin or /bin.
If you're unable to continue your Apache build, you may want to check both /bin/sh and /bin/bash. You might find out that "sh" is just a symbolic link to "bash".
You can find out for sure if they're separate files by running the following command;
"ls -l /bin/bash /bin/sh"
(Note: that's the "ls" command, not the "ln" command used to create links)
-r-xr-xr-x 1 root bin 735572 Jan 22 2005 /bin/bash
-r-xr-xr-x 1 root root 95468 May 9 2008 /bin/sh
If you see something like this, then they're separate files, and you should rename "/bin/sh" (with the "mv" command) before creating the link (but don't just outright delete the "/bin/sh" binary, you can't undo that, and it might cause problems down the road.)
If instead you see something like this, then "/bin/sh" is already a link to "/bin/bash";
-r-xr-xr-x 1 root bin 732556 May 2 2007 /bin/bash
lrwxrwxrwx 1 root root 13 Nov 24 2008 /bin/sh -> /bin/bash
P.S: Exercise extreme caution when using the "rm" command. I understand that you're new to Linux, so take heed and read the man page for that command. There's no Recycle Bin on the command-line!
i saw your post after I had done the other. No worries though, it definitely fixed the problem. I don't appear to have any problems yet, but I'm not exactly an expert. I did look up those commands in the manual, not that I understood them too well, but hey, it's all a learning curve. The good news is, if all else fails, this is a throwaway system anyhow, rescued from the trash heap. So if I irrevocably screw it up, no huge loss. Of course, if I can avoid that, so much the better. Anyhow, thanks to both of you. Problem solved, for now at least.
Not just that apache but there more than 20000 packages available. You can find most of the popular packages there, may be more than what you will ever use in your life. Instead of compiling from the source use the Synaptic. It will download and install not only the package you want but all the dependencies as well. That will save a lot of time for you and put more time in productive work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.