025 15:11
> To: Robert Dubner ; Andreas Schwab
> Cc: gcc-patches@gcc.gnu.org; Rainer Orth
> Subject: RE: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.
>
> Excerpts from Robert Dubner's message of Juli 9, 2025 4:32 pm:
> > With respect, this is another example of "I have been
On Tue, 8 Jul 2025 16:59:36 -0500 (CDT)
Robert Dubner wrote:
> > Does that not suffice?
>
> I don't think it does.
>
> I am forced, for roughly the fourth time, to establish my
> requirements:
>
> 1) I want, for development, to be able to establish flags for the
> COBOL front end -- independen
Excerpts from Robert Dubner's message of Juli 9, 2025 4:32 pm:
> With respect, this is another example of "I have been unable to make it
> work."
>
> The gcc/Makefile.in has this line in it:
>
> $(foreach file,$(ALL_HOST_FRONTEND_OBJS),$(eval CFLAGS-$(file) +=
> -DIN_GCC_FRONTEND))
>
> At the po
On Jul 09 2025, Robert Dubner wrote:
> An attempt to override that with
>
> make CFLAGS-cobol/genapi.o=-DHARMLESS
>
> has no effect on the value of the CFLAGS-cobol/genapi.o
If you are doing this from the toplevel then it's because only known
variables are passed to subdirs.
--
Andreas Sc
hes@gcc.gnu.org
> Subject: Re: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.
>
> On Jul 08 2025, Robert Dubner wrote:
>
> > Are you suggesting that I can somehow apply a specific set of flags
when
> > compiling, for example,
> >
> > gcc/cobol/genapi.cc
> &
On Jul 08 2025, Robert Dubner wrote:
> Are you suggesting that I can somehow apply a specific set of flags when
> compiling, for example,
>
> gcc/cobol/genapi.cc
>
> If so, how could I do that?
There are some examples in gcc/Makefile.in.
CFLAGS-cobol/genapi.o = ...
--
Andreas Schwab, SUS
> -Original Message-
> From: James K. Lowden
> Sent: Tuesday, July 8, 2025 17:11
> To: Robert Dubner
> Cc: Richard Biener ; Rainer Orth
> ; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.
>
> On Tue, 8 Jul 2025 14:11:19
On Tue, 8 Jul 2025 14:11:19 -0500 (CDT)
Robert Dubner wrote:
> But I have other requirements. I apologize if I keep repeating
> myself, but I am being forced to.
>
> I want to be able to, for example,
>
> CXXFLAGS='-ggdb -O0'
> CXXFLAGS_FOR_COBOL="-Wsomething_or_other" ../configure
> -Original Message-
> From: Andreas Schwab
> Sent: Tuesday, July 8, 2025 10:01
> To: Robert Dubner
> Cc: Rainer Orth ; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.
>
> There is already $(CFLAGS-$@) to add extra flags f
> -Original Message-
> From: Richard Biener
> Sent: Tuesday, July 8, 2025 14:22
> To: Robert Dubner
> Cc: Rainer Orth ; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.
>
> On Tue, Jul 8, 2025 at 12:46
On Tue, Jul 8, 2025 at 12:46 AM Robert Dubner wrote:
>
>
>
> > -Original Message-
> > From: Rainer Orth
> > Sent: Monday, July 7, 2025 18:08
> > To: Robert Dubner
> > Cc: gcc-patches@gcc.gnu.org
> > Subject: Re: [PATCH] cobol: Implement CXXFL
> -Original Message-
> From: Richard Biener
> Sent: Tuesday, July 8, 2025 09:54
> To: Robert Dubner
> Cc: Andreas Schwab ; Rainer Orth bielefeld.de>; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.
>
> On Tue, Jul 8, 20
There is already $(CFLAGS-$@) to add extra flags for a particular
target. This could easily be extended by adding $(CFLAGS-$(@D)) to add
flags for all targets in a directory.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"An
On Tue, Jul 8, 2025 at 3:45 PM Robert Dubner wrote:
>
> > -Original Message-
> > From: Andreas Schwab
> > Sent: Tuesday, July 8, 2025 03:16
> > To: Robert Dubner
> > Cc: Rainer Orth ; gcc-patches@gcc.gnu.org
> > Subject: Re: [PATCH] cobol: Implemen
> -Original Message-
> From: Andreas Schwab
> Sent: Tuesday, July 8, 2025 03:16
> To: Robert Dubner
> Cc: Rainer Orth ; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.
>
> On Jul 07 2025, Robert Dubner wrote:
>
> >
On Jul 07 2025, Robert Dubner wrote:
> Furthermore, even if this method did work, I need the CXXFLAGS_FOR_COBOL
> options to appear at the end of the list, not the beginning, since they
> may need to override what came before.
Why can't you use CXXFLAGS?
--
Andreas Schwab, SUSE Labs, sch...@sus
> -Original Message-
> From: Rainer Orth
> Sent: Monday, July 7, 2025 18:08
> To: Robert Dubner
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.
>
> Hi Robert,
>
> > I have elsewhere described my frustrat
Hi Robert,
> I have elsewhere described my frustration in trying, during development,
> to set more stringent error-finding and warning-generating compilation
> options. But they seem to require the use of CXXFLAGS, which in at least
> the case of trying to set -std=c++14, causes libcody's compil
this okay for trunk?
Thanks.
Bob Dubner
>From ff295ac4ba9728fdd8d97fa73754cd17a21d0f18 Mon Sep 17 00:00:00 2001
From: Robert Dubner
Date: Mon, 7 Jul 2025 16:34:09 -0400
Subject: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.
It's useful during development to be able to specify compilation
19 matches
Mail list logo
