Re: [Tack-devel] CVS & the new build system

[tim k. <gt...@di...>]

At 6:36 PM -0400 7/24/06, David Given wrote:
>tim kelly wrote:
>[...]
>> host:Ack {114} ./pm -DPREFIX=/home/lapd/ack/bin/ configure
>> host:Ack {115} ./pm -DPREFIX=/home/lapd/ack/bin/
>
>Ah --- I suspect you're confusing the LLgen installation procedure with the
>ACK one! -DPREFIX only applies to LLgen. You have to install it so that LLgen
>is on the path. Once that's done, './pm configure && ./pm' will build the ACK
>(somewhere else).

Ok, I was thinking the PREFIX path coded some paths.

>Basically, they're two separate packages that get installed separately. If you
>can't run LLgen from the command line, the ACK won't build.

Hmmm...there's a difference between running "LLgen" and
"/home/account/ack/bin/LLgen" :-)

>[...]
>> pm: object 'LLgen', defined at pmfile:39, failed to build with return code
>> 32512
>
>This error message doesn't mean that LLgen has failed to build, despite the
>phrasing; it means that a rule of type 'LLgen' has failed --- that is,
>something is trying to *use* LLgen but hasn't worked (because LLgen isn't on
>your path).

Yes, and looking through the specific line in the pmfile that failed, it
was building util/cpp, which is the first utility in the process to require
LLgen, as far as I can tell.  Looks like util/topgen is the only other
utility that needs LLgen.  I'm still grepping through the other files.

So what flag needs to be added to the pmfiles to specify the location for
LLgen?  (And it is possible one might wish to run different versions of
LLgen, plus on some systems it is not possible without root privileges to
install into /usr/local, notably OpenBSD, which has it group and world
read-execute, but not write).

tim

Gregory T. (tim) Kelly
Owner
Dialectronics.com

P.O. Box 606
Newberry, SC 29108

"Anything war can do, peace can do better."  -- Bishop Desmond Tutu