[m-dev.] turning on --halt-at-warn-if-possible

[Zoltan Somogyi]

I have a diff that add this new option to the .mgnuc_opts file in each
directory. I have just committed a diff that fixes the last thing
that causes gcc warnings during a hlc.gc bootcheck, so it is good to go,
but I want to wait until (a) everyone has installed a compiler with the
9d46463 change I committed yesterday, and (b) there is an rotd
with that change. I would like to add this option to .mgnuc_opts files
on thursday. If this is too early for you, please speak up.

Zoltan.

[Julien Fischer]

Post by Zoltan Somogyi
I have a diff that add this new option to the .mgnuc_opts file in each
directory. I have just committed a diff that fixes the last thing
that causes gcc warnings during a hlc.gc bootcheck, so it is good to go,
but I want to wait until (a) everyone has installed a compiler with the
9d46463 change I committed yesterday,

FYI, rotd-2018-07-31 (which was just uploaded) contains that commit.

Julien.

[Peter Wang]

Post by Julien Fischer

Post by Zoltan Somogyi
I have a diff that add this new option to the .mgnuc_opts file in each
directory. I have just committed a diff that fixes the last thing
that causes gcc warnings during a hlc.gc bootcheck, so it is good to go,
but I want to wait until (a) everyone has installed a compiler with the
9d46463 change I committed yesterday,

FYI, rotd-2018-07-31 (which was just uploaded) contains that commit.

Can we provide the exact git commit hash for each ROTD on the download
page, or in the archive?

Peter

[Julien Fischer]

Post by Peter Wang

Post by Julien Fischer

Post by Zoltan Somogyi
I have a diff that add this new option to the .mgnuc_opts file in each
directory. I have just committed a diff that fixes the last thing
that causes gcc warnings during a hlc.gc bootcheck, so it is good to go,
but I want to wait until (a) everyone has installed a compiler with the
9d46463 change I committed yesterday,

FYI, rotd-2018-07-31 (which was just uploaded) contains that commit.

Can we provide the exact git commit hash for each ROTD on the download
page, or in the archive?

Sure; I both would be preferable -- have the hash next to the link on
the download page and put it in a file (e.g. COMMIT_ID) within the
tarball.

Julien.