Very Computer

tks

harveyneon.doesntexist.com

--
**********************************************************************
Desmond Coughlan     Network Engineer    Forum des Images     Paris  *

**********************************************************************

Quote:> and why doesn't it work?
> (no such file or directory)

Nick

I presume if you're running ./configure that you're wanting to
compile some source you found somewhere outside of the ports
collection. Even if you're not, you're certainly going to do so
one day so the advice won't come amiss. Let's imagine you have
with a file called "really_cool_application-2.3.tar.gz".

$ su (because you know enough not to log on as root)

Put the .tar.gz file in /usr/local/src, which is the "official
location" for this sort of thing. Then cd to /usr/local/src and

$ tar -zxvf really_cool_application-2.3.tar.gz

This should make a directory called  really_cool_application-2.3
(though some tars like Mozilla give you a completely different
name from the original)

$ cd really_cool_application-2.3
$ ./configure

./configure will now work because you're calling it from the
right place. It will spit out a load of information about how
well your system supports the compilation and than either stop
at the end of the list or tell you sorry, pal, you don't have
what it takes. Assuming the first happy outcome, you can then
type "make" and if this works with no errors, "make install"  
will put all the binaries in the right directories.
Afterwards, if you don't want to keep the compiled object files,
type make clean. If it was a pig to get to compile, you probably
won't be in a hurry to ditch the source.
Lastly, because you used su at the start, use control-D to get
out of superuser mode.

Bye, Dave.

P.S. just to be picky, configure is not the autoconf program, it
is a perfectly standard script. Autoconf is the program that
generates the configure script, which has usually already been
done by the time you get the source. (I don't even have autoconf
on my machine).

--

OK, I've installed the free software. Now where's the free beer?

To mail me swing an axe between underscore and dave.

                        Hope this helps,
                              Don

--
**********************      You a bounty hunter?
* Rev. Don McDonald  *      Man's gotta earn a living.
* Baltimore, MD      *      Dying ain't much of a living, boy.
**********************             "Outlaw Josey Wales"
http://members.home.net/oldno7

                        Yours in Christ,
                              Don

--
**********************      You a bounty hunter?
* Rev. Don McDonald  *      Man's gotta earn a living.
* Baltimore, MD      *      Dying ain't much of a living, boy.
**********************             "Outlaw Josey Wales"
http://members.home.net/oldno7

Quote:

>> and why doesn't it work?
>> (no such file or directory)

>Uh, that sounds bad.  Have you tried running it by typing "sh -x configure" to
>see where the error is?  (You didn't remove /bin/sh, by any chance?)

thanks for your help, but didn't really help. i see i got lots of
other replies though, so i'll try them. thanks nick.

Harveyneon.doesntexist.com

Quote:

>Nick

Nick

cheers, g.

harveyneon.doesntexist.com

ps. i log in as root ALL THE TIME

# cd /usr/ports/net/samba
# make install clean

and let the FreeBSD ports system take care of everything - inlcuding
calling ./configure?

HTH,
Patrick
--
--- WEB ISS GmbH - Scheffelstr. 17a - 76135 Karlsruhe - 0721/9109-0 ---

"Contrary to popular belief, penguins are not the salvation of modern
 technology.  Neither do they throw parties for the urban proletariat."

can i geta witness?

but seriously, i had to dl the tar.gz and start from scratch cuz it
was so fAckEd up. (i fixed it myself!)

( i deleted the skeleton. )

yours truly,

harveyneon.doesntexist.com

Quote:>this was for samba 2.0.7 and the makefiles and all that junk
>are in the /source directory, not the main directory of the
>port. samba is a pain in the ass for me, i would like to
>completely uninstall it.. but i don't know how to go about
>that. i think that'll be my next research subject.

>cheers, g.

--

OK, I've installed the free software. Now where's the free beer?

To mail me swing an axe between underscore and dave.

flame on, by all means.

besides, it's obvious which one of us has a problem socially
interacting with other human beings so severe that he cannot even do
so properly using his trusty computer.

i say this because you basically invited me to not participate in this
newsgroup on the grounds that i am too green and have not RTFM. and
then you said something about wasting time or something, which i just
plain don't understand. are you wasting people's time by posting your
flame bunk, or am i wasting my time in attempting to configure samba
without reading the whole fbsd manual?

in any event, suckmyballs, and i'll be getting right on to that
freebsd manual, oh great master of the universe with your advanced
skills and knowledge which make me obsolete in today's world.

hope this wasted some of your time, Dave.

        Fag,

        While I in no way agree with Dave's flame of someone trying to
learn, I must admit you do project the "i NEed sUm WAreZ duuUUUde"
attitude with the way you post.  Learn to hold down the "Shift" key
when typing "I".  It might stop people from dismissing your postings
as those of an adolescent.

        To get back to the question, if you are continually getting "file
not found" when you try to run "configure", that means that you are
not in the right directory, "configure" isn't in your PATH or you
are leaving off the "./".  What you need to do is to unTAR your
package and then "cd" into the subdirectory it creates.  Then do
"./configure".  Unless it was a typo, you posted that you did
"/configure".  They are two very different commands.  Under UNIX
(and presumably pseudo UNIX) systems "." means the current
directory.  What "./" means is run the command right here in this
*ing directory!  Some newbie nimrods include "." in their PATH
mostly because they are idiots.  If "." is in your PATH, you won't
need the "./" but "." should never be in your PATH.  There are
volumes that have been written on why.  Take the following as an
example of compiling the package "pseudo-unix-1.0".

        Step 1: Download "pseudo-unix-1.0.tar.Z" from the appropriate
anonymous FTP site.

        Step 2: Uncompress "pseudo-unix-1.0.tar.Z" with "uncompress
pseudo-unix-1.0.tar.Z"  
        (The ".Z" means it is a compressed file.  If it was compressed with
"gzip", it
        would have a ".gz" "extension".  In that case you would do
        "gunzip pseudo-unix-1.0.tar.Z")

        Step 3: Do "tar tvf pseudo-unix-1.0.tar.Z"
        (This is because you're being careful instead of clueless.  Some
TAR files
        do not unTAR neatly into subdirectories.  They put all their files
in the
        current directory which can be a mess.  The "t" option in "tar tvf"
is for
        "table of contents" and you should see that all the filenames are
proceeded
        by some directory name and a slash (e.g.
"pseudo-unix-1.0/file1.c").  If not
        then do "mkdir temp; cd temp").

        Step 4: UnTAR the file.  That would be "tar xvf
pseudo-unix-1.0.tar.Z"
        (or "tar xvf ../pseudo-unix-1.0.tar.Z" if you had to make the
"temp"
        subdirectory).

        Step 5: Do "./configure".  That's "./configure"!!!  Don't leave any
characters
        out!

        Step 6: Do "make".

        Step 7: Do "make install".

        Step 8: If you're old enough, sit back with a beer and relax
because you just installed your application.

                        Hope this helps,
                              Don

--
**********************      You a bounty hunter?
* Rev. Don McDonald  *      Man's gotta earn a living.
* Baltimore, MD      *      Dying ain't much of a living, boy.
**********************             "Outlaw Josey Wales"
http://www.veryComputer.com/