https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97183
Jim Wilson changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97183
--- Comment #7 from Jim Wilson ---
Fixed on mainline and the gcc-10 branch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97183
--- Comment #6 from CVS Commits ---
The releases/gcc-10 branch has been updated by Jim Wilson :
https://gcc.gnu.org/g:9d85b9880e1772ead961c7b5a2bd8caab57815bf
commit r10-8831-g9d85b9880e1772ead961c7b5a2bd8caab57815bf
Author: Jim Wilson
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97183
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jim Wilson :
https://gcc.gnu.org/g:6649df18f98d5baf89b56a09b816b5eeb5f67bcb
commit r11-3536-g6649df18f98d5baf89b56a09b816b5eeb5f67bcb
Author: Jim Wilson
Date: Mon Sep
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97183
--- Comment #4 from Martin Liška ---
> Or we can check for the 1.3.0 version which seems simpler.
> I do know that version 1.3.3 of zstd works as this is what Ubuntu 18.04 has.
> I haven't tried the versions 1.3.[012].
Yes, I would recommend ch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97183
--- Comment #3 from Jim Wilson ---
I installed Ubuntu 16.04 on an old laptop so I can directly reproduce the build
failure.
Checking for the zstd version looks like the easier patch.
Checking for specific macros and functions might be better, b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97183
Martin Liška changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
Last reconfir
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97183
--- Comment #1 from Richard Biener ---
I think amending the configure test for the specific macro / API uses is better
than a version check.
