Dominik Vogt writes:
> Currently:
>
> $ touch configure.in
> $ make CFLAGS="-Wall -Werror"
> => make reruns configure
> => some configure test programs fail because of the warnings in
> some header files
> => features are detected/missed incorrectly (e.g. AC_C_CONST
> detects a non-
Dominik Vogt writes:
> On Wed, Sep 18, 2002 at 08:35:22AM -0400, Dan Espen wrote:
> > Dominik Vogt writes:
> > > On Wed, Sep 18, 2002 at 10:30:52AM +0200, fvwm-workers wrote:
> Does it compile if you remove the "conts" bits?
Yes.
I changed 1 line like this:
main(int i, int * p)
Solaris:
fork
On Wed, Sep 18, 2002 at 08:35:22AM -0400, Dan Espen wrote:
> Dominik Vogt writes:
> > On Wed, Sep 18, 2002 at 10:30:52AM +0200, fvwm-workers wrote:
> > [snip]
> > > How about this: write a small test program that issues lots of
> > > warnings with -Wall and AC_TRY_COMPILE it. When that fails,
>
On Wed, Sep 18, 2002 at 08:33:32AM -0500, Eric Gillespie wrote:
> Dominik Vogt writes:
[snip]
> > How about this: write a small test program that issues lots of
> > warnings with -Wall and AC_TRY_COMPILE it. When that fails,
> > configure bugs out with an error message.
>
> I guess you meant -We
Dominik Vogt writes:
> Okay, but what about CFLAGS? I don't care much about the
You're probably OK resetting CFLAGS; anything someone will need
to add to build it would be a define, include path, or library
path, i should think. You never know though, and there's still
the principle of least s
Dominik Vogt writes:
> On Wed, Sep 18, 2002 at 10:30:52AM +0200, fvwm-workers wrote:
> [snip]
> > How about this: write a small test program that issues lots of
> > warnings with -Wall and AC_TRY_COMPILE it. When that fails,
> > configure bugs out with an error message.
>
> This is the test cod
On Wed, Sep 18, 2002 at 01:27:09PM +0200, Ulrich Fahrenberg wrote:
> On Wed, 18 Sep 2002, Dominik Vogt wrote:
>
> > --- warn.c ---
> > #include
> > main(const i, const int * const p)
> > {
> > char *c;
> >
> > switch (*p = p = *c)
> > {
> >
On Wed, 18 Sep 2002, Dominik Vogt wrote:
> --- warn.c ---
> #include
> main(const i, const int * const p)
> {
> char *c;
>
> switch (*p = p = *c)
> {
> case 0:
> printf("%p", c, p);
> }
> *c = &i;
> c = p;
> while (1
On Wed, Sep 18, 2002 at 10:30:52AM +0200, fvwm-workers wrote:
[snip]
> How about this: write a small test program that issues lots of
> warnings with -Wall and AC_TRY_COMPILE it. When that fails,
> configure bugs out with an error message.
This is the test code I came up with. To the best of my
On Tue, Sep 17, 2002 at 02:00:27PM -0500, Eric Gillespie wrote:
> Dominik Vogt writes:
>
> > Yes, there is a very good reason: configure chokes on the
> > -Werror flag and produces more or less random test results.
> > This can be hell to debug. Maybe I can find a way to enable
> > the original
Dominik Vogt writes:
> Yes, there is a very good reason: configure chokes on the
> -Werror flag and produces more or less random test results.
> This can be hell to debug. Maybe I can find a way to enable
> the original CFLAGS again before they are placed in the
> Makefiles.
That is not general
On Tue, Sep 17, 2002 at 12:44:03PM +0200, Ulrich Fahrenberg wrote:
> On Tue, 17 Sep 2002, Dominik Vogt wrote:
>
> > On Tue, Sep 17, 2002 at 01:54:56AM -0400, Suzanne Skinner wrote:
> >
> > > Also, CFLAGS aren't working at all?
> >
> > They should be working as usual. I have disabled them in
> > c
On Tue, 17 Sep 2002, Dominik Vogt wrote:
> On Tue, Sep 17, 2002 at 01:54:56AM -0400, Suzanne Skinner wrote:
>
> > Also, CFLAGS aren't working at all?
>
> They should be working as usual. I have disabled them in
> configure because they often cause some tests to fail. How did
> you specify the fl
On Tue, Sep 17, 2002 at 01:54:56AM -0400, Suzanne Skinner wrote:
> Fvwm does not compile if Gnome hints and/or EWMH hints are disabled. The
> attached patch fixes this.
>
> Also, CFLAGS aren't working at all?
They should be working as usual. I have disabled them in
configure because they often c
14 matches
Mail list logo
