Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0NI6Gl42379 for ; Wed, 23 Jan 2002 13:06:17 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g0NI5Rf03762; Wed, 23 Jan 2002 13:05:27 -0500 (EST) To: Peter Eisentraut cc: Brent Verner , Vsevolod Lobko , Murray Prior Hobbs , Lamar Owen , pgsql-hackers@postgresql.org Subject: Re: pltcl build problem on FreeBSD (was: Re: pltlc and pltlcu problems) In-reply-to: References: Comments: In-reply-to Peter Eisentraut message dated "Wed, 23 Jan 2002 12:59:00 -0500" Date: Wed, 23 Jan 2002 13:05:27 -0500 Message-ID: <3759.1011809127@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200201/1066 X-Sequence-Number: 18048 Peter Eisentraut writes: > Tom Lane writes: >> [ scratches head ... ] Where is the expansion happening, then? Seems >> weird. > The $@ is expanded as a make variable. Make does care whether you're > executing a $(shell) thing around it. However, it seems that $@ should > expand to nothing in that assignment, so where's the problem? I think the complaint is that we need it to still look like $@ when TCL_SHLIB_LD is used in the shlib-building rule. If Make recursively expands the variable before executing the $shell construct then we got trouble. Ugly as it is, the check on portname may be the best solution available. I'm gonna think a little more, but I haven't got a better idea now. regards, tom lane