Alex

I do not have a visible file called pathsetup at all on my OS partition. As
you can see, certainly not in my /sw/bin folder...

T




On 23/3/04 4:15 pm, "Alexander K. Hansen" <[EMAIL PROTECTED]> wrote:

> This may be out of date:  do you have /sw/bin/pathsetup.sh on your
> system?
> 
> On Mar 23, 2004, at 10:43 AM, Timothy Carpenter wrote:
> 
>> Hi
>> 
>> According to the FAQ, I run the sw/bin/pathsetup
>> 
>> Alas, I do not have such a file in this directory nor anywhere on my
>> boot
>> volume. BTW I aim to get Fink Commander running - 0.5.2 is now loaded
>> but is
>> empty - I guess for the PATH reasons.
>> 
>> My Fink Commander PATH is:
>> /sw/bin:/sw/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/
>> bin:/sbi
>> n
>> 
>> 
>> /sw/bin contains the following:
>> 
>> [Tim-Carpenters-Computer:/sw/bin] timcarpe% ls
>> 822-date                dpkg-name               init.sh
>> aclocal                 dpkg-parsechangelog     m4
>> aclocal-1.6             dpkg-scanpackages       md5sum
>> apt-cache               dpkg-scansources        mktemp
>> apt-cdrom               dpkg-shlibdeps          msgcmp
>> apt-config              dpkg-source             msgcomm
>> apt-extracttemplates    dpkg-split              msgfmt
>> apt-get                 dselect                 msgmerge
>> apt-sortpkgs            editor                  msgunfmt
>> autoconf                fink                    ngettext
>> autoheader              gawk                    onsgmls
>> autom4te                gawk-3.1.0              openjade
>> automake                gettext                 osgmlnorm
>> automake-1.6            gettextize              ospam
>> autoreconf              glib-genmarshal         ospent
>> autoscan                glib-gettextize         osx
>> autoupdate              glib-mkenums            pager
>> awk                     gm4                     pgawk
>> bunzip2                 gnutar                  pkg-config
>> bzcat                   gobject-query           readlink
>> bzcmp                   gtar                    reset
>> bzdiff                  gtkdoc-fixxref          tack
>> bzegrep                 gtkdoc-mkdb             tar
>> bzfgrep                 gtkdoc-mkhtml           tempfile
>> bzgrep                  gtkdoc-mkman            tic
>> bzip2                   gtkdoc-mktmpl           toe
>> bzip2recover            gtkdoc-scan             tput
>> bzless                  gtkdoc-scangobj         tset
>> bzmore                  gtkdoc-scanobj          xgettext
>> captoinfo               gunzip                  xmlwf
>> clear                   gzcat                   zcat
>> dpkg                    gzexe                   zcmp
>> dpkg-architecture       gzip                    zdiff
>> dpkg-buildpackage       iconv                   zforce
>> dpkg-checkbuilddeps     ifnames                 zgrep
>> dpkg-deb                igawk                   zless
>> dpkg-distaddfile        infocmp                 zmore
>> dpkg-genchanges         infotocap               znew
>> dpkg-gencontrol         init.csh
>> 
>> Thanks
>> 'Chef'
>> 
>> On 23/3/04 2:29 pm, "Alexander K. Hansen" <[EMAIL PROTECTED]>
>> wrote:
>> 
>>> 
>>> On Mar 23, 2004, at 8:06 AM, Joshua S. Freeman wrote:
>>> 
>>>> Tim,
>>>> 
>>>> first, I believe you have to be 'root' to run fink... have you
>>>> enabled
>>>> 'root' on your machine?  or, better yet, have you added yourself to
>>>> the
>>>> sudoers list on your machine?  if you don't know what I'm talking
>>>> about
>>>> email me off-list.
>>>> 
>>>> 
>>> 
>>> You don't need to be root to run the "fink" command (it doesn't hurt
>>> anything if you are, though).
>>> 
>>> You do need to be root to install/remove packages with "apt-get" or
>>> "dselect"
>>> 
>>>> Anyway..
>>>> 
>>>>  when you're in /sw/bin
>>>> 
>>>> you need to type:  ./fink selfupdate
>>>> 
>>>> that dot slash is very important when running commands that are not
>>>> in
>>>> your path.
>>>> 
>>> 
>>> This is not what you want to do.  You need the correct working
>>> environment, as per what I sent in my other message.
>>> 
>>> A problem with just specifying the path to the "fink" executable is
>>> that if you run "fink selfupdate" and something does need to be
>>> installed, then "fink" will want to run other programs after building
>>> the package, but won't be able to find them.
>>> 
>>>> Cheers,
>>>> 
>>>> J.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> <snip>
>>> 
>>>> --
>>> Alexander Hansen
>>> Fink Documentarian
>>> [Day Job] Levitated Dipole Experiment
>>> http://www.psfc.mit.edu/LDX
>>> 
>>> 
>>> 
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by: IBM Linux Tutorials
>>> Free Linux tutorial presented by Daniel Robbins, President and CEO of
>>> GenToo technologies. Learn everything from fundamentals to system
>>> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>>> _______________________________________________
>>> Fink-beginners mailing list
>>> [EMAIL PROTECTED]
>>> https://lists.sourceforge.net/lists/listinfo/fink-beginners
>> 
>> 
>> 
>> -------------------------------------------------------
>> This SF.Net email is sponsored by: IBM Linux Tutorials
>> Free Linux tutorial presented by Daniel Robbins, President and CEO of
>> GenToo technologies. Learn everything from fundamentals to system
>> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>> _______________________________________________
>> Fink-beginners mailing list
>> [EMAIL PROTECTED]
>> https://lists.sourceforge.net/lists/listinfo/fink-beginners
>> 



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Fink-beginners mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-beginners

Reply via email to