Re: Force -O0 flags, inhibit the default -O2 flags

2005-09-27 Thread Ralf Corsepius
On Tue, 2005-09-27 at 12:53 +0200, Harald Dunkel wrote: > Ralf Corsepius wrote: > > > > Nope. You don't seem to have understood how things are working: > > > > AM_CFLAGS/AM_CXXFLAGS are supposed to take flags having been specified > > by a package's developer. > > > > Understood. > > > CFLAGS/

Re: Force -O0 flags, inhibit the default -O2 flags

2005-09-27 Thread Ralf Corsepius
On Tue, 2005-09-27 at 19:38 -0600, Brian wrote: > We have several files which are not able to be optimized, and when our mac > mini tries to build the project it chokes up when attempting to do so. It > seems incorrect to say that the package developer is the least qualified to > judge compiler fla

Re: Force -O0 flags, inhibit the default -O2 flags

2005-09-27 Thread Bob Friesenhahn
On Tue, 27 Sep 2005, Brian wrote: We have several files which are not able to be optimized, and when our mac mini tries to build the project it chokes up when attempting to do so. It seems incorrect to say that the package developer is the least qualified to judge compiler flags, and it also see

Re: Force -O0 flags, inhibit the default -O2 flags

2005-09-27 Thread Brian
We have several files which are not able to be optimized, and when our mac mini tries to build the project it chokes up when attempting to do so. It seems incorrect to say that the package developer is the least qualified to judge compiler flags, and it also seems to avoid the point. The package de

Re: Force -O0 flags, inhibit the default -O2 flags

2005-09-27 Thread Bob Friesenhahn
On Tue, 27 Sep 2005, Harald Dunkel wrote: So the user has to write make CFLAGS= CXXFLAGS= install to get the default flags (AM_CXXFLAGS, etc.) provided by the developer? Sorry, but this is weird. Are there any other flags the user has to reset to get the flags specified by the developer

Re: windres compilation rule

2005-09-27 Thread Stepan Kasal
Hello, On Tue, Sep 27, 2005 at 05:23:43AM -0500, John Ratliff wrote: > I tested it in Linux with automake 1.9.6 and it still doesn't work. indeed, I previously did some quick testing with rule .list-> .c, and it worked. But for rules .foo -> .o it really doesn't work. I wrote a patch which fixe

RE: windres compilation rule

2005-09-27 Thread John Ratliff
I tested it in Linux with automake 1.9.6 and it still doesn't work. I changed the rc rule to compile an rc file that was really a C file. It still doesn't interpret the directory correctly. Per your other suggestions, I have altered my Makefile.am like so: AUTOMAKE_OPTIONS = subdir-objects EXTRA

Re: Force -O0 flags, inhibit the default -O2 flags

2005-09-27 Thread Harald Dunkel
Ralf Corsepius wrote: > > Nope. You don't seem to have understood how things are working: > > AM_CFLAGS/AM_CXXFLAGS are supposed to take flags having been specified > by a package's developer. > Understood. > CFLAGS/CXXFLAGS are suppoed to take flags having been specified by a > package's inst

RE: windres compilation rule

2005-09-27 Thread John Ratliff
I tested it in Linux with automake 1.9.6 and it still doesn't work. I changed the rc rule to compile an rc file that was really a C file. It still doesn't interpret the directory correctly. Per your other suggestions, I have altered my Makefile.am like so: AUTOMAKE_OPTIONS = subdir-objects EXTRA

RE: windres compilation rule

2005-09-27 Thread John Ratliff
> Hello, > > On Tue, Sep 27, 2005 at 01:40:34AM -0500, John Ratliff wrote: > > make[2]: *** No rule to make target `windows.o', needed by `mpg.exe'. > Stop. > > this message indicates a problem in the makefile. It seems that the > variable mpg_OBJECTS contains "windows.o", while it should contai

Re: windres compilation rule

2005-09-27 Thread Stepan Kasal
Hello, On Tue, Sep 27, 2005 at 01:40:34AM -0500, John Ratliff wrote: > make[2]: *** No rule to make target `windows.o', needed by `mpg.exe'. Stop. this message indicates a problem in the makefile. It seems that the variable mpg_OBJECTS contains "windows.o", while it should contain "res/windows.