./configure is actually telling the computer to run a shell script that is contained in the current directory (which you just set by using cd ). If the terminal cannot find the command, perhaps you had better check to make sure it's there. Type the following at the prompt:
# cd wlassistant-0.3.9
# ls
Look at the output printed. There should be a file listed there named "configure". If the files don't seem remotely like the source code (no INSTALL, README files), then perhaps you're in the wrong directory.
If you're using a terminal app to enter your commands, usually the easiest way to solve the problem mentioned is to drag the wlassistant onto the terminal app, which will automatically paste the folder's location; add "cd" in front of it, and then hit return. Then try the configure script again.
Hope this helps
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
That means that the shell can find the configure script, but cannot get past a certain line. This could be due to a number of things, but the easiest way to find out what's wrong is to try this command instead:
sh ./configure
Post any error messages you get.
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
You may want to try downloading and installing SCons first to see if that fixes anything.
My other suspicion is that python is not in the PATH variable. Try running echo $PATH at the shell. You'll get a list of paths seperated by colons. If /usr/bin isn't listed, then you'll need to enter the following:
# PATH=$PATH:/usr/bin
And then try running the configure script again.
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
Hehe, looks like you're going to have to install another package from source. :D
http://prdownloads.sourceforge.net/scons/scons-src-0.96.94.tar.gz
That's what is annoying about compiling from source - all too often packages have other dependancies which have dependancies of their own, causing you to go on a wild goosechase trying to install all these other packages to get the original to compile.
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
Ah. Unarchiving tar.gz is nearly identical to unarchiving tar.bz2. Just enter something like this at the shell:
# tar xfz scons-source-...
A directory containing the source code will then be created. cd to this, and then proceed with regular compilation steps.
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
Would this have anything to do with the fact that i am running it live on CD? Would it work better if i actually had it installed?
No kidding...
I assumed that you had actually installed MEPIS from the LiveCD. No wonder. Yes, if you're interested in Linux, you should really try installing it. LiveCDs are a fun way to try out Linux, but the real fun comes once you've got a working install. Then you can actually install and compile stuff properly.
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
SCons installed fine, (oh, why did i install that anyways? What does it do?)
You need it because Wireless Assistant was built with it, and so you need it to reconstruct the program when compiling.
But that wlassistant STILL doesn't want to install!
It keeps saying "bad interpreter: Permission Denied"!!!!!!!!!!!
The real question is to try the configure command again with the sh to find out what's actually going on. Make sure that this line here changes:
Checking for SCons : [B]not found, will use mini distribution.[/B]
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
You don't need wlassistant to connect to the internet. iwconfig is a command-line utility (related it iwlist) that allows you to connect to access points, and is installed by default in nearly every Linux distro. First of all, run iwconfig to find out your wireless adapter:
# iwconfig
It will spit out various network adapters. The one that has wireless extensions is the one you want to take note of. Then use this for your connection like this:
# iwconfig ath0 essid "accesspoint"
Of course, you have to know the name of the access point to be able to connect to it. Then run iwconfig again to make sure it connected:
# iwconfig ath0
If the information printed out looks correct, proceed by getting your IP address either by static or DHCP
(for dhcp) dhcpcd ath0
(for static) ifconfig ath0 192.168.0.1
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
There's quite a number of things which can be causing this. For one thing, this error occurs everytime if your hard drive is mounted with the noexec option. To fix this, you'd need to go into your /etc/fstab file, edit it, and make sure that when it lists your hard drive, no "noexec" line is present. If there is, remove it.
Secondly, it could be due to the configure script being in the wrong encoding format. Any script using DOS end-of-line symbols will totally mess up the script interpreter for Linux. Try editing the file and make sure there's no whitespace between #/bin/sh and the top of the file. Resave it.
Thirdly, try running the script again with sh. That is,
sh ./configure
And post the error results.
edit:
And yes you are right, you could assign your computer a static IP address, because it's from your router to your computer; the dynamic IP address is from your ISP to your router. To assign, simply use ifconfig, but be warned: many routers don't like static IPs either and prefer to assign them to you.
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7