[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <94D52C65148543D0B234A271903199F9@D9VGLK61>
Date: Tue, 7 Jun 2011 19:20:11 -0500
From: "JimF" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: Re: Makefile LN = ln -sf
I can not comment on the -sf to -s -f. For the sparc, no it was not there.
I build both 64 and 32 bit, and was having issues prior to the RM
However, the -sf to -s -f was done, and then I started having problems.
That may go away if the -sf works as you mention below.
Jim.
----- Original Message -----
From: "Solar Designer" <solar@...nwall.com>
Sent: Tuesday, June 07, 2011 6:35 PM
> Jim, magnum -
>
> In -jumbo-5, there are these changes (which were not in -jumbo-1):
>
> -LN = ln -sf
> +LN = ln -f -s
>
> solaris-sparc64-cc:
> + $(RM) arch.h
> $(LN) sparc64.h arch.h
>
> and similar for other Solaris targets.
>
> Why? Didn't the original Makefile work fine on Solaris?
>
> Then, why make both changes at once? Are they unrelated or are they
> both an attempt to fix the same issue?
>
> Normally, the "-f" option to "ln -s" tells it to remove existing
> destination files before creating the symlink, so the $(RM) shouldn't be
> needed. Also, normally "ln -sf" is the same as "ln -f -s".
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
