On Fri, Aug 11 2017, Jeremie Courreges-Anglas <j...@wxcvbn.org> wrote:
> On Fri, Aug 11 2017, Christian Weisgerber <na...@mips.inka.de> wrote:
>> On 2017-08-10, Jeremie Courreges-Anglas <j...@wxcvbn.org> wrote:
>>> +# XXX base gcc
>>> +CC=                        /usr/bin/gcc
> Thanks for the test reports, which confirm that I'm the only one unable
> to run memtest86+ on my machines...
>> That isn't a solution.
> It is a solution, just not a long-term one. ;)
> So here's a diff I just cooked up (I don't know where I've put the
> previous version...).  While here, respect CC.  Note that as(1) is still
> used once, which could be a problem on a clang-only box.
> Tests welcome.

So with this diff memtest86+ doesn't work any more on naddy's x230
(it did with /usr/bin/gcc).  Using gcc from ports doesn't help.

We have several options:
- mark it broken
- force the use of /usr/bin/gcc, which obviously work work any more when
  we unlink gcc on i386/amd64.
- build a binary snapshot with /usr/bin/gcc and then just use that
  binary snapshot as a distfile.  After all, these are standalone

Marking it BROKEN would be a shame, memtest86+ is a useful tool.  As
discussed with naddy I don't know yet which solution we'll choose in the
end, opinions welcome.

jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE

Reply via email to