Re: Compiling Postgresql 8.0.3 on Solaris 10

Hello Tom,

I hope that you are well, thank you for your guidence, but these are indeed
defined in my .bashrc:

# .bashrc

# User specific aliases and functions

# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi

if [ "$PS1" ]; then
# your settings:
PS1="[\u(at)\h::\@::\w]\\$ "
fi

alias cls=clear
alias e\-mail=pine
alias e='emacs -nw $1'
alias rmf='/bin/rm -f'
alias rmp='/bin/rm'
alias rm='rm -i'
alias logout=exit
alias lo=exit
alias rmtmp='rm -i core *~ *.*~ .*~ .pine-debug*'
alias mproc='ps -ef | grep $USER'
alias allproc='ps -ef | less'
alias ll='colorls -l'
alias ls='colorls -al'

I don't see why colorls would do anything different, or for that matter rm -i,
shouldn't the shell scripts *not* use the user's environment and detect that
there is /bin/rm and that ls is /bin/ls etc etc. Secondly, I did login and typed
sh, which dumped me into the sh shell, in my previous e-mail I showed the alias
listings in that shell. I tried compiling in that shell and it seems that it
presents the same problems.

Cheers,

Aly.

Tom Lane wrote:
> Aly Dharshi <aly(dot)dharshi(at)telus(dot)net> writes:
>
>>alias ls='colorls -al'
>>alias rm='rm -i'
>
>
>>I don't see any aliases that are going to break the compile process.
>
>
> I beg to differ --- I think the ones quoted above match your symptoms
> pretty well. So the question is: why are they getting used in a
> noninteractive script?
>
> My bet is that you've defined these aliases in the wrong place.
> I'm not sure about Solaris, but on Linux one conventionally puts
> aliases like these in ~/.bashrc, which I think is not read by
> plain sh. If you've put them in ~/.profile they are very likely
> to break shell scripts.
>
> regards, tom lane

--
Aly Dharshi
aly(dot)dharshi(at)telus(dot)net

"A good speech is like a good dress
that's short enough to be interesting
and long enough to cover the subject"