If you are using 0.99.1+ (maybe) or SVN version you may have this
problem!

This problem crept in several months ago when the python input file for
.\dissectors was renamed (maake-dissector-reg.py) and moved to a
sub-directory.  This change was also made in the .\plugins\profinet &
sbus directories.  On Win32 platform, this problem can be corrected by
either of two solution:

change
        @$(PYTHON) ../../tools/make-dissector-reg.py . dissectors
$(DISSECTOR_SRC)

to
        @$(PYTHON) "../../tools/make-dissector-reg.py" . dissectors
$(DISSECTOR_SRC)

or
        @$(PYTHON) ..\..\tools\make-dissector-reg.py . dissectors
$(DISSECTOR_SRC)

This still needs to be corrected in SVN & releases.

-Tim



> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Ulf Lamping
> Sent: Monday, September 18, 2006 6:39 AM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] newbie build problem with python
> 
> 
> > 
> > Try to use Cygwins Python.
> > 
> >  
> 
> I'm using cygwin's python and sometimes also get this error. 
> This seems to be a Makefile problem (a dependency? still 
> don't know a real solution to it). Try to build some of the 
> subtargets first, e.g.:
> 
> nnmake -f Makefile.nmake doc
> 
> usually helps me around.
> 
> Regards, ULFL
> 
> _____________________________________________________________________
> Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
> http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
> 
> _______________________________________________
> Wireshark-dev mailing list
> [email protected]
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
> 
> ______________________________________________________________
> _______________
> Scanned by IBM Email Security Management Services powered by 
> MessageLabs. For more information please visit 
> http://www.ers.ibm.com 
> ______________________________________________________________
> _______________
> 
_______________________________________________
Wireshark-dev mailing list
[email protected]
http://www.wireshark.org/mailman/listinfo/wireshark-dev

Reply via email to