Adam,
As per Lawrence Velázquez's email, you need to give the full path to port
(/opt/local/bin/port) until you fix your shell's login files.
To modify your tcsh shell login files, type at the command line
open ~/.cshrc
On my 10.6.8 machine, this opens the ~/.cshrc file in TextEdit. At the
"sudo port install py27-scipy" gives "sudo: port: command not found".
On 02/05/2013, Ryan Schmidt wrote:
>
> On May 1, 2013, at 23:42, Adam Neather wrote:
>
>> Running that command gives the following:
>>
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_t
Running that command gives the following:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-scipy/py-scipy/main.log
NB: Scipy was the package that failed to install; numpy and cython
apparently worked.
On 02/05/2013, Lawrence Velázq
Given that my port command is back to not working, this may be a
difficult endeavour. ;)
On 02/05/2013, Ryan Schmidt wrote:
>
> On May 1, 2013, at 22:25, Adam Neather wrote:
>
>> Is main.log meant to be under /var/log? I can't find it.
>
> No, the file is in a directory specific to each port, and
Is main.log meant to be under /var/log? I can't find it.
I'm still running tcsh. Thought I'd just stick with it, seeing as it
was (briefly!) working. For confirmation, 'echo $SHELL' still returns
/bin/tcsh.
Thanks much everyone, I hope this isn't too frustrating.
On 02/05/2013, Ryan Schmidt wro
Gotcha.
In other news, I'm back to square one. I used 'sudo port install' to
get py-numpy and py-cython, but py-scipy failed. I rebooted the Mac,
and now I get 'No manual entry for port' etc. again. Even running the
setenv command that fixed it before isn't doing anything.
This is painfully confu
Nope, completely new account. My personal Mac has bash, but this one
seems to have defaulted to tcsh for some reason.
If I switch to bash now, will I need to reset my PATH, like I did with
setenv under tcsh?
On 02/05/2013, Ryan Schmidt wrote:
>
> Maybe you transferred an older user account fro
On May 1, 2013, at 19:22, Adam Neather wrote:
> On 02/05/2013, Ryan Schmidt wrote:
>>
>> On May 1, 2013, at 19:10, Scott Webster wrote:
>>
>>> I think bash has been the default since 10.3?
>>
>> Yes. Any user account created on Mac OS X 10.3 or newer would default to
>> bash. If your user accou
Don't know what to tell you. This is a brand new iMac, only been out
of the box for a week. I haven't changed anything, and echo $SHELL
returns tcsh.
On 02/05/2013, Ryan Schmidt wrote:
>
> On May 1, 2013, at 19:10, Scott Webster wrote:
>
>> I think bash has been the default since 10.3?
>
> Yes.
On May 1, 2013, at 19:10, Scott Webster wrote:
> I think bash has been the default since 10.3?
Yes. Any user account created on Mac OS X 10.3 or newer would default to bash.
If your user account was initially created in 10.0, 10.1 or 10.2 and you've
been upgrading that same account ever since,
On May 1, 2013, at 8:08 PM, Adam Neather wrote:
> Because tcsh is the default and I can't work out how to change it to bash. ;)
The "chpass" command in my last email is how you change your default login
shell to OS X's bash.
vq
___
macports-users mai
I think bash has been the default since 10.3?
On Wed, May 1, 2013 at 5:08 PM, Adam Neather wrote:
> Because tcsh is the default and I can't work out how to change it to bash.
> ;)
>
> On 02/05/2013, Lawrence Velázquez wrote:
> > On May 1, 2013, at 7:39 PM, Adam Neather wrote:
> >
> >> I've on
Because tcsh is the default and I can't work out how to change it to bash. ;)
On 02/05/2013, Lawrence Velázquez wrote:
> On May 1, 2013, at 7:39 PM, Adam Neather wrote:
>
>> I've only got minimal command line experience and that's with bash.
>
> Well if that's the case, you could certainly switc
On May 1, 2013, at 7:39 PM, Adam Neather wrote:
> I've only got minimal command line experience and that's with bash.
Well if that's the case, you could certainly switch your default shell to bash.
% /usr/bin/chpass -s /bin/bash
vq
___
macports-u
... why are you using tcsh then? (sorry if missed the explanation somewhere)
On Wed, May 1, 2013 at 4:39 PM, Adam Neather wrote:
> Ah ha, running that setenv command has fixed the problem.
>
> Cheers very much to everyone that helped! I never would have figured
> out the tcsh setenv command on
Ah ha, running that setenv command has fixed the problem.
Cheers very much to everyone that helped! I never would have figured
out the tcsh setenv command on my own, I've only got minimal command
line experience and that's with bash.
On 02/05/2013, Brandon Allbery wrote:
> On Wed, May 1, 2013 at
On Wed, May 1, 2013 at 12:14 AM, Adam Neather wrote:
> This is where we start to reach the limits of my Terminal Fu! To
> change my tsch start up files as suggested, would I run
>
> export PATH=/opt/local/bin:opt/local/sbin:$PATH
>
Add to the end of ~/.login:
set path=(/opt/local/bin /opt/local
On Apr 30, 2013, at 23:14, Adam Neather wrote:
> This is where we start to reach the limits of my Terminal Fu! To
> change my tsch start up files as suggested, would I run
>
> export PATH=/opt/local/bin:opt/local/sbin:$PATH
That's bash syntax, not tcsh syntax.
_
18 matches
Mail list logo
