Ronaldo Mercado wrote:
>One way I have seen this solved is to have a #define, say '#define MAIN'
>
>On the header file "header.h" you would have a declaration and a definition
>only if MAIN is defined, e.g.
>
>extern int y; /* declaration */
>#ifdef MAIN
>int y; /* definition */
>#endif
On Mon, Feb 17, 2020 at 2:59 PM Bruno Wolff III wrote:
> For greyhounds, I didn't make an exception in the include file, but rather
> added definitions to the main unit to reserve the space (and changed the
> include file to add extern to the definitions). This didn't result in a
> conflict, so I'
On Mon, Feb 17, 2020 at 21:32:30 +,
Ronaldo Mercado wrote:
I would like to see an example package where you experience this problem.
In my case, greyhounds was the normal case. raidem was the enum should have
been a typedef case.
For greyhounds, I didn't make an exception in the inclu
Hello,
> The most common fix I used was, using "extern" in all but one place.
> Well I guess what I was looking for was for us non-C/C++ programmers. :)
> I can grep the source and arbitrarily choose which one not to use extern
> with, but is there a right way?
I would like to see an example pac
On Mon, Feb 17, 2020 at 12:20 PM Bruno Wolff III wrote:
> On Sun, Feb 16, 2020 at 07:24:10 -0600,
> Richard Shaw wrote:
> >So I have several FTBFS bugs most likely from the new gcc being more
> >pedantic. I understand the bug at a high level but I think it would be
> nice
> >if someone who rea
On Sun, Feb 16, 2020 at 07:24:10 -0600,
Richard Shaw wrote:
So I have several FTBFS bugs most likely from the new gcc being more
pedantic. I understand the bug at a high level but I think it would be nice
if someone who really understood it could perhaps document strategies for
figuring out how
For now I'm settling for packages which I know I don't want to be retired
to add:
# https://gcc.gnu.org/gcc-10/porting_to.html#common
%define _legacy_common_support 1
To the top of the spec with a link to an upstream issue if filed...
Thanks,
Richard
>
___
So I have several FTBFS bugs most likely from the new gcc being more
pedantic. I understand the bug at a high level but I think it would be nice
if someone who really understood it could perhaps document strategies for
figuring out how to find the right file that needs to be updated and how.
Perha
