Adam Joseph 86a0e46ed4 gcc: fix implication order in assertion ... In 6812dd98c4 I mistakenly had the implication order reversed. This commit corrects that mistake. The original assertion (which is correct) was the following, which asserts that if you enable the GDB plugin, you must enable plugins generally (there is shared infrastructure): ``` assert enableGdbPlugin -> enablePlugin; ``` When the option name was changed to `disableGdbPlugin`, I incorrectly wrote: ``` assert disableGdbPlugin -> enablePlugin; ``` And then again incorrectly wrote: ``` assert disableGdbPlugin -> !enablePlugin; ``` This commit uses the correct equivalent for the first statement, which is the contrapositive: ``` assert !enablePlugin -> disableGdbPlugin; ```		2023-02-23 22:54:49 -08:00
..
configure-flags.nix	gcc: fix implication order in assertion	2023-02-23 22:54:49 -08:00
dependencies.nix	gcc: add callFile to make it more convenient to call files	2023-02-11 21:17:30 +02:00
extra-target-flags.nix	cross/mingw: make threading library configureable	2022-11-14 12:50:04 +01:00
meta.nix	gcc: add common/meta.nix	2023-02-12 05:44:34 +02:00
platform-flags.nix
pre-configure.nix	gnat12: Add support for x86_64-darwin	2023-01-07 18:32:12 +11:00
strip-attributes.nix	libgccjit: don't try to enter into non-existent $lib output	2022-08-20 12:51:36 +01:00