[M3devel] install issues (stripping, permissions)

[Jay]

Also "dist" means "distribution" means run on other machines, try not to be too specific to build machine. That is why not full paths.

 - Jay

On Jun 5, 2015, at 3:59 PM, Jay <jay.krell at cornell.edu> wrote:

> We could use origin, origin/../lib, origin/../../lib etc? But eventually a security problem to reach all around? Plain origin is in case the files are all together in one directory like on windows.
> 
> Isn't it desirable to be buildable w/ system cc/ld and latest?
> 
> Thank you for this work.
> 
> - Jay
> 
> On Jun 5, 2015, at 1:53 PM, John Marino <adacore at marino.st> wrote:
> 
>> On 6/5/2015 20:51, Jay K wrote:
>>> This is kind of on purpose as Olaf said and kind of broken as you point out.
>>> 
>>> We often build_standalone() to workaround the origin/rpath matte.
>>> 
>>> We kind of fail here, in terms of library paths.
>> 
>> well, to be blunt, it -is- broken and thus is a fail.
>> 
>>> I don't think the original system fully accounted for runpath.
>>> I think at the time, LD_LIBRARY_PATH might have been considered an
>>> acceptable solution.
>> 
>> If I wanted to go down a path like this, I'd use ldconfig, but my
>> personal feeling if is ldconfig is required, the software is doing
>> something wrong.
>> 
>> 
>>> Elsewhere, with libtool, make install relinks to reset paths. We don't
>>> have that implemented.
>>> It is somewhat a good solution.
>> 
>> I think it has to be a tweak at FreeBSD.common -- rather than use
>> $ORIGIN/../lib for rpath, it needs a conditional statement to use
>> $ORIGIN/../../../lib instead.  I just don't know what the condition is.
>> 
>> I'm also trying to figure out why rpath=$ORIGIN is needed.  are there
>> ever libraries in the same directory as cm3?
>> 
>> ohn