svn commit: r402352 - head/lang/gcc

[Alexey Dokuchaev]

On Sun, Feb 19, 2017 at 05:06:45PM +0100, Gerald Pfeifer wrote:
> > Symlinks are badly created (will be broken if e.g. $prefix mounted under
> > non-/ via NFS), better (untested) approach would be:
> > 
> > .for f in gfortran g++ gcc
> > 	${LN} -sf ${f}${SUFFIX} ${STAGEDIR}${PREFIX}/bin/${f}
> > .endfor
> 
> At first I wasn't completely clear what you had in mind here (or
> rather: why exactly), and I did not get a single report from a
> user in the 15 months since then.

Probably because most people don't care exactly how symlinks point to their
targets as long as it works (and it does, most of the time).  Usually it's
better to use relative paths though, and just the filename when both source
and target are in the same directory.

> What do you think about the patch below?

I still think that it's better to use make(1)'s .for loop rather than
sh(1)'s one.  Consider attached patch which also fixes indentation of the
comment.  (You might also want to call ln(1) with `-f' switch at your
discretion.)

> Only problem is, portlint now warns
> 
>   WARN: g++: this is a symlink. Please remove it.
>   WARN: gcc: this is a symlink. Please remove it.
>   WARN: gfortran: this is a symlink. Please remove it.
> 
> which I did not do when I've been using absolute paths.

Hmm, I cannot reproduce this.  Can you report portlint version (portlint -V)
and attach the output of `portlint -Avc .' please?  These messages should
normally be emitted when checking port's directory; are there anything not
belonging to it by chance?

./danfe
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gcc.diff
Type: text/x-diff
Size: 711 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-ports-all/attachments/20170221/97d51c42/attachment.diff>