Re: pltcl build problem on FreeBSD (was: Re: pltlc and pltlcu problems) - Mailing list pgsql-hackers

From Brent Verner
Subject Re: pltcl build problem on FreeBSD (was: Re: pltlc and pltlcu problems)
Date
Msg-id 20020123122950.A14509@rcfile.org
Whole thread Raw
In response to Re: pltcl build problem on FreeBSD (was: Re: pltlc and pltlcu problems)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pltcl build problem on FreeBSD (was: Re: pltlc and pltlcu problems)  (Brent Verner <brent@rcfile.org>)
List pgsql-hackers
[2002-01-23 12:06] Tom Lane said:
| Brent Verner <brent@rcfile.org> writes:
| > | Will it not work to do
| > | 
| > | $(shell echo '$(TCL_SHLIB_LD)' | sed ...
| 
| > No.  I just tested this, and the $@ still got expanded too early.
| 
| [ scratches head ... ]  Where is the expansion happening, then?  Seems
| weird.

apparently the $(shell ...) construct expands any shell-like
vars.

from make's info file:
    The `shell' function performs the same function that backquotes (``') perform in most shells: it does "command
expansion".

| > We'll need to use the suggested ifeq($(PORTNAME),linux) test.
| 
| I don't much like that since it makes an inappropriate assumption,
| viz that if you're on Linux you must have a TCL_SHLIB_LD value that
| hasn't got any $variables in it.  I'd prefer to figure out *why* we
| are getting a premature evaluation.

maybe check for a '$' in the TCL_SHLIB_LD ?  I've been trying
$(findstring ...) but have not gotten that to work right yet.
 brent

-- 
"Develop your talent, man, and leave the world something. Records are 
really gifts from people. To think that an artist would love you enough
to share his music with anyone is a beautiful thing."  -- Duane Allman


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pltcl build problem on FreeBSD (was: Re: pltlc and pltlcu
Next
From: Peter Eisentraut
Date:
Subject: Re: pltcl build problem on FreeBSD (was: Re: pltlc and