<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>$ORIGIN is "in case" we restructure Unix install to look like Windows install -- moving lib on top of bin.<BR>I realize you'd like just the minimum required, not hypothetical values for the future.<BR><br>Regarding gcc/ld -- isn't it desirable to have either/both work?<br>Are there command lines that work with both and provide the same meaning?<BR><br>Does our stuff not work with older gcc/ld?<br>Do ports in general avoid system gcc/ld?<BR><br>Does clang work?<br>I intend to try.<BR><br> - Jay<br><br><br><br> <BR><div>> Date: Sat, 6 Jun 2015 07:57:50 +0200<br>> From: adacore@marino.st<br>> To: jay.krell@cornell.edu<br>> CC: m3devel@elegosoft.com<br>> Subject: Re: [M3devel] install issues (stripping, permissions)<br>> <br>> On 6/6/2015 00:59, Jay wrote:<br>> > We could use origin, origin/../lib, origin/../../lib etc? But<br>> > eventually a security problem to reach all around? Plain origin is in<br>> > case the files are all together in one directory like on windows.<br>> <br>> I'm not really a fan of just adding every possible rpath. In this case,<br>> it's either $ORIGIN/../lib or $ORIGIN/../../../lib, but together is<br>> never correct (as the other mail indicates, $ORIGIN by itself also seems<br>> to be always wrong)<br>> <br>> > <br>> > Isn't it desirable to be buildable w/ system cc/ld and latest?<br>> <br>> On DragonFly - yes<br>> On FreeBSD - no.<br>> <br>> FreeBSD is stuck with either ancient gcc (4.2.1), ancient binutils<br>> (2.17) or clang. In every case, it needs to use newer GCC and binutils<br>> from ports to build M3. (and every newer GCC)<br>> <br>> John<br></div> </div></body>
</html>