[M3devel] ROOT

Tony Hosking hosking at cs.purdue.edu
Thu Jul 2 19:47:44 CEST 2009


On 2 Jul 2009, at 12:55, Jay wrote:

> As long as there is a need to work with older m3core, there will be  
> hacks..

But why would you compile a new cm3 with an old m3core?

> This stuff provides a significant value.
> Before, the runpaths recorded would be a directory per dependent  
> shared object -- the directory in the package store. And the  
> runpaths were not machine portable -- if you install to a different  
> location, which is debatable, maybe everyone should be stuck with / 
> usr/local/cm3. OR everyone had to set LD_LIBRARY_PATH.

I thought the use of -rpath overcomes the need for LD_LIBRARY_PATH?

> With the hard links, people don't have to set LD_LIBRARY_PATH and  
> everyone can pick their own install location.

Is LD_LIBRARY_PATH so bad if you insist on moving the libraries  
someplace other than the rpath used in their linkage?

> As well the temporary staging location for a distribution is not  
> recorded in the binaries -- e.g. it wouldn't be /usr/local/cm3, but / 
> tmp/something.

I'd really like to hear opinions on this from others.

>
>
> - Jay
>
>
>
> ________________________________
>> CC: m3devel at elegosoft.com
>> From: hosking at cs.purdue.edu
>> To: jay.krell at cornell.edu
>> Subject: Re: [M3devel] ROOT
>> Date: Thu, 2 Jul 2009 12:40:18 -0400
>>
>> I'm not talking about m3overrides. That is a arguably a special- 
>> purpose hack. We shouldn't layer a hack into the *normal* build  
>> process.
>>
>>
>> Antony Hosking | Associate Professor | Computer Science | Purdue  
>> University
>> 305 N. University Street | West Lafayette | IN 47907 | USA
>> Office +1 765 494 6001 | Mobile +1 765 427 5484
>>
>>
>>
>>
>> On 2 Jul 2009, at 12:19, Jay wrote:
>>
>>
>> Seems broken to me to depend on
>> the source directory structure
>>
>> Like m3overrides? But yes, I agree.
>> m3overrides seems broken too.
>>
>> - Jay
>>
>>
>>
>>
>>
>>
>>
>>
>> ----------------------------------------
>> From: hosking at cs.purdue.edu
>> To: m3devel at elegosoft.com
>> Date: Thu, 2 Jul 2009 11:49:34 -0400
>> Subject: [M3devel] ROOT
>>
>> Where did variable ROOT come from? Do I really need to define it?
>> Seems broken to me to depend on the source directory structure as it
>> sets that structure in stone.
>>
>>
>>




More information about the M3devel mailing list