On 5/8/05, Kamaraju Kusumanchi <[EMAIL PROTECTED]> wrote:
> Michael Marsh wrote:
> > In general, though, it's better to set everything that you need in the
> > makefile, since relying on your aliases makes your makefile highly
> > non-portable. I usually do something like (using your example):
> >
On Sun, May 08, 2005 at 10:17:11PM -0400, Michael Marsh wrote:
> On 5/8/05, Kamaraju Kusumanchi <[EMAIL PROTECTED]> wrote:
> > Hi
> > Using Debian sid. I have an alias in my .bashrc say something like
> >
> > alias x="y"
> >
> > This command is executing fine on a bash shell (ie I can use x).
Michael Marsh wrote:
On 5/8/05, Kamaraju Kusumanchi <[EMAIL PROTECTED]> wrote:
Hi
Using Debian sid. I have an alias in my .bashrc say something like
alias x="y"
This command is executing fine on a bash shell (ie I can use x). But
when I use x in a makefile, it is not getting expanded to y. Is th
On 5/8/05, Kamaraju Kusumanchi <[EMAIL PROTECTED]> wrote:
> Hi
> Using Debian sid. I have an alias in my .bashrc say something like
>
> alias x="y"
>
> This command is executing fine on a bash shell (ie I can use x). But
> when I use x in a makefile, it is not getting expanded to y. Is this a
Hi
Using Debian sid. I have an alias in my .bashrc say something like
alias x="y"
This command is executing fine on a bash shell (ie I can use x). But
when I use x in a makefile, it is not getting expanded to y. Is this a
future? How can I overcome this limitation?
thanks for any pointers
raj
5 matches
Mail list logo