automake generates delete targets twice

Hello, regarding to https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2749 I'm wondering whether at UNIX systems automake could be improved to delete a target only once. -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 signature.asc Descri

How to pinpoint aclocal failure

Hello! Since I'm not sure if this is actually an automake or autoconf issue, and sure you can also help I'm also posting this here as well as on the autoconf mailin-list. Excuse me if this bothers someone. Last addition of some macros to the cURL (libcurl) project have triggered an aclocal failur

Re: automake generates delete targets twice

Hello Toralf, * Toralf Förster wrote on Wed, Jul 30, 2008 at 09:26:10AM CEST: > > regarding to https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2749 I'm > wondering whether at UNIX systems automake could be improved to delete a > target > only once. Why? (This is an honest question.) AFAIC

Re: How to pinpoint aclocal failure

Hello, * Yang Tse wrote on Wed, Jul 30, 2008 at 08:17:54PM CEST: > > Since I'm not sure if this is actually an automake or autoconf issue, It's not clear from the bug report. aclocal endless loops are a pain to debug. If you can go back to a known-good version (of configure.ac and *.m4 files),

My rule doesn't seem to work

I have figured out how to compile qt-3.x programs using autotools with one exception. qmake makes a file called image_collection which takes .png files and combines them into one cpp file. It uses the command: uic -embed appname image1.png image2.png -o image_collection I tried writing the rule

Re: How to pinpoint aclocal failure

2008/7/30, Ralf Wildenhues wrote: > aclocal endless loops are a pain to debug. If you can go back to a > known-good version (of configure.ac and *.m4 files), you may be able to > bisect. One of the many things that have already been tried is to comment out the new macro invocations leaving in pl