[M3devel] install issues (stripping, permissions)

[Jay K]

$ORIGIN is "in case" we restructure Unix install to look like Windows install -- moving lib on top of bin.
I realize you'd like just the minimum required, not hypothetical values for the future.

Regarding gcc/ld -- isn't it desirable to have either/both work?
Are there command lines that work with both and provide the same meaning?

Does our stuff not work with older gcc/ld?
Do ports in general avoid system gcc/ld?

Does clang work?
I intend to try.

 - Jay



 
> Date: Sat, 6 Jun 2015 07:57:50 +0200
> From: adacore at marino.st
> To: jay.krell at cornell.edu
> CC: m3devel at elegosoft.com
> Subject: Re: [M3devel] install issues (stripping, permissions)
> 
> On 6/6/2015 00:59, Jay 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.
> 
> I'm not really a fan of just adding every possible rpath.  In this case,
> it's either $ORIGIN/../lib or $ORIGIN/../../../lib, but together is
> never correct (as the other mail indicates, $ORIGIN by itself also seems
> to be always wrong)
> 
> > 
> > Isn't it desirable to be buildable w/ system cc/ld and latest?
> 
> On DragonFly - yes
> On FreeBSD - no.
> 
> FreeBSD is stuck with either ancient gcc (4.2.1), ancient binutils
> (2.17) or clang.  In every case, it needs to use newer GCC and binutils
> from ports to build M3. (and every newer GCC)
> 
> John
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20150606/929078c3/attachment-0002.html>