On Mar 3, 2018, at 15:14, Jan Stary wrote:
> On Feb 28 08:03:31, Ken Cunningham wrote:
>> The basic principle is that a build of a port on any darwin_N system
>> anywhere will be identical to every other build on that darwin version
>> on all other machines.
>
> Does that mean that MP will set
On 2018-03-03, at 1:14 PM, Jan Stary wrote:
>
> What of I have two of those, with different Xcode on each?
That is undesirable for reproducible builds.
Most users have the default Xcode version for a give system, as Apple flushes
all the updates that way.
If users report broken builds and
> > > mandoc's ./configure sets CC to whatever make(1) thinks CC is:
> > > CC=`printf "all:\\n\\t@echo \\\$(CC)\\n" | env -i make -sf -`
> > > Why exactly is it "not the right compiler"?
> >
> > As env -i clears the environment,
> > how is this supposed to work at all?
> > This does not respect
On Feb 28 08:03:31, ken.cunningham.web...@gmail.com wrote:
> The basic principle is that a build of a port on any darwin_N system
> anywhere will be identical to every other build on that darwin version
> on all other machines.
Does that mean that MP will set the same configure.cc for mandoc
on
On 2018-02-28 08:52, Jan Stary wrote:
> The ticket is closed, so I will continue here.
>
>> Actually it's not specific to the universal variant. Rather, the problem
>> is that the port is not UsingTheRightCompiler.
>
> mandoc's ./configure sets CC to whatever make(1) thinks CC is:
> CC=`printf
On Feb 28, 2018, at 01:52, Jan Stary wrote:
>> I had my MacPorts configured to error out if `cc` is used
>> using the method described at UsingTheRightCompiler#testing.
>
> Why would you do that?
To detect ports that do not use a specific compiler. MacPorts policy is that
all ports shall use
