On Mon, Mar 30, 2009 at 03:15:18PM -0400, Terry Dontje wrote:
> >
<snip>
> >
> >->ls -l /bin/sh
> >lrwxrwxrwx 1 root root 4 2008-04-02 02:13 /bin/sh -> bash
> >
> I am using tcsh it may take me a while to set up bash for myself.
I too run tcsh as a login shell but the scripts are all shebanged to run in bash.
So even more curous
> >handle MCA bucket. Ungracefully hacking the offending parentheses
> >from configure causes some v.strange things to happen. I will continue
> >hacking but until this bears fruit... do you also need to include
> >'x86_64' as an argument for configure?
> I don't, and pretty sure neither does Ethan.
> >What happens when you run 'uname -X'?
> >
> >
> Interesting I get "uname: invalid option --X" but should this always
> end up turning into "unknown"?
configure line 2903:
/bin/uname -X = `(/bin/uname -X) 2>/dev/null || echo unknown`
Hmmm... v.interesting
Why do I need to provide x86_64 as an argument when nobody else seems to????
There is something v.vstrange going on with my parentheses.
k.mcmanus_at_[hidden] - http://staffweb.cms.gre.ac.uk/~k.mcmanus
--------------------------------------------------------------
Dr Kevin McManus Queen Mary 413
School of Computing & Mathematical Sciences,
University of Greenwich,
Old Royal Naval College,
Park Row, Greenwich, Tel +44 (0)208 331 8719
London, SE10 9LS Fax +44 (0)208 331 8665
--------------------------------------------------------------
University of Greenwich, a charity and company limited by
guarantee, registered in England (reg no. 986729)
Registered Office: Old Royal Naval College
|
![[Flag]](../../../../../community/mirrors/flag-us.gif){kind=small}