Wireshark-dev: Re: [Wireshark-dev] plugin Linux Makefile failure
From: "Bob Pultorak" <pultorak@xxxxxxxxx>
Date: Fri, 4 Apr 2008 13:50:52 -0500
I was using a symbolic link to my plugins, I copied those directories into the project and it now compiles.  anyone have any experience with this and why symbolic links don't work?

On Thu, Apr 3, 2008 at 12:55 PM, Bob Pultorak <pultorak@xxxxxxxxx> wrote:
Thanks,
I fixed that now I get

make[3]: *** No rule to make target `../../aclocal-fallback/glib.m4', needed by `Makefile.in'.  Stop.


On Thu, Apr 3, 2008 at 11:55 AM, Jaap Keuter <jaap.keuter@xxxxxxxxx> wrote:
Hi,
 
Looks like that somewhere in the process an ASCII editor is used which has the option "Replace tabs by spaces" enabled.
Look very carefully at the settings of your editors.
 
Thanx,
Jaap


From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Bob Pultorak
Sent: 2008-Apr-03 16:45
To: wireshark-dev@xxxxxxxxxxxxx
Subject: [Wireshark-dev] plugin Linux Makefile failure

I have added a few custom plugins to the new release (1.0.0).  I was able to successfully compile the code before adding anything.
I followed the DEVELOPER.plugins file for instruction how to add a new plugin correctly.  I updated all the necessary files, ran autogen.sh and configure.  When compiling my plugins I get the following error:

Makefile:763: *** missing separator (did you mean TAB instead of 8 spaces?).  Stop.

If I go into the makefile it corresponds to this line:
        @if test -n "$(PYTHON)"; then \

if I change the spaces to a tab, it just changes the error to another line, it takes over 20 replacements like this to successfully compile.  I have done a diff between my makefile and agentx's makefile and the only difference is the name of my plugin.  I would like to fix the root of the problem rather then hand editing the Makefile any time I run the configure script.

Thanks,
Bob

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev