Re: AM_MAINTAINER_MODE

2013-02-09 Thread Ineiev
On 02/08/2013 08:30 PM, Russ Allbery wrote: Another place where the default behavior frequently breaks is if one is applying a patch to both the generated file and the source file, usually because one explicitly *doesn't* want to re-run Automake (often because there's some incompatibility with th

Re: Solved: Need Code to Run Before Targets Are Processed?

2008-08-04 Thread Ineiev
Sorry for delay. On 8/4/08, Bobby Dill <[EMAIL PROTECTED]> wrote: > Just wanted to let everyone know I figured out what Ineiev solution was. Just wanted to explain in more detail for those who did not. Makefile.am.m4 is a template written in m4 without Autoconf redefinitions and macros

Fwd: Solved: Need Code to Run Before Targets Are Processed?

2008-08-04 Thread Ineiev
Awfully sorry, sent it from a wrong address. -- Forwarded message -- From: Ineiev <[EMAIL PROTECTED]> Date: Aug 4, 2008 11:00 AM Subject: Re: Solved: Need Code to Run Before Targets Are Processed? To: Bobby Dill <[EMAIL PROTECTED]> Cc: Automake Sorry for delay. On 8

Re: Need Code to Run Before Targets Are Processed?

2008-07-31 Thread Ineiev
ke info, section FAQ->wildcards. The summary of their considerations is that you should know your sources to keep them neat and that it is technically hard to provide this feature portably. Regards, Ineiev -- Navigare necesse est. Vivere non est necesse.

Re: dist_bin_SCRIPTS and implicit rules

2008-07-28 Thread Ineiev
Hello Ralf, On 7/28/08, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > #When src/foo.c is newer than src/foo, > > #GNU make applies it's implicit rule, like this: > > # gcc -g -O2../ns/src/foo.c -o src/foo > > Yep. Kinda ugly. You should be able to work around it by adding > an empty rule:

Re: Dependencies: non-standard path to system headers

2008-07-03 Thread Ineiev
taddrinfo: hostname nor servname provided, or not known > tar: c\:/tmp/foo.tar: Cannot open: Input/Output error > tar: Error is not recoverable: exiting now --force-local? Again, I think your idea is generally correct; and I am not going to work on Cygwin at all (I wish my eyes didn't look at them!), I just checked whether my package can build there. Regards, Ineiev

Re: Dependencies: non-standard path to system headers

2008-07-02 Thread ineiev
st need to be recompiled. In my real life I need an access to RS-232 UARTs. I use W5s API, because termios won't do it on Cygwin. >This is far from the only example where you will encounter this clash if >you continue to mix native apps with Cygwin tools. The life is hard. Best regards, Ineiev

Re: Dependencies: non-standard path to system headers

2008-07-02 Thread ineiev
.in Thank you. This would be really better. Regards, Ineiev

Dependencies: non-standard path to system headers

2008-06-30 Thread Ineiev
Some time ago I tested build process of my project on cygwin. Some parts of the project are AVR-hosted, so I checked if WinAVR were capable to build them. WinAVR gcc produces dependencies that shall confuse `make', like these: sampler.o: ../../../stribog/sw/auxilia/coil/sampler.c \ c:/winavr-20