Python 2.7 it is!! Yes, you are right . It was the problem (compatibility) with version 3.3 I added 2.7 to config.nmake and installed it and I could succsfully build and run wireshark !!
Thanks for all the help Guys. On Tue, Nov 12, 2013 at 12:52 AM, Pascal Quantin <[email protected]>wrote: > Hi, > > html2text.py is most probably not compatible with Python 3.3 yet. > I recommend to install Python 2.7 instead, that's what I use to build > Wireshark myself. > > Regards, > Pascal. > > Le 11 nov. 2013 à 20:07, Sreejith M M <[email protected]> a écrit : > > Thanks Graham > > I tried Visual Studio command prompt and it worked. > After encountering a few errors and googling around it, I am now stuck at > the below error. Looks like a syntax error in html2text.py. Have anyone > seen it? > > > > > > > > > > > > > > > > > > > > > > > > > > > *Microsoft (R) Program Maintenance Utility Version 10.00.30319.01Copyright > (C) Microsoft Corporation. All rights reserved. > "C:\Python33\python.exe" faq.py | "C:\Python33\python.exe" ..\tools\html > 2text.py --width=72 --no-links > faq.txt File "..\tools\html2text.py", > line 332 self.o("][" + `a['count']` + "]") > ^SyntaxError: invalid syntax Traceback (most recent call last): File > "faq.py", line 2101, in <module> sys.exit(main()) File "faq.py", line > 265, in main create_output(header, footer) File "faq.py", line 236, in > create_output create_index() File "faq.py", line 226, in > create_index sec.print_index() File "faq.py", line 71, in > print_index print(('<a class="faq_qnum" href=#q%s>%s %s</a>\n' % (id, > id, question))) BrokenPipeError: [Errno 32] Broken pipeNMAKE : fatal error > U1077: '"C:\Python33\python.exe"' : return code '0x1'Stop.NMAKE : fatal > error U1077: '"C:\Program Files\Microsoft Visual Studio 10.0\VC\BI > N\nmake.exe"' : return code '0x2'Stop.* > > > On Mon, Nov 11, 2013 at 3:21 PM, Graham Bloice < > [email protected]> wrote: > >> On 11 November 2013 09:16, Sreejith M M <[email protected]> wrote: >> >>> Even the below files does not exist in my PC. >>> >>> For the sake of future users, I believe the wireshark developer doc must >>> be editied >>> >>> >>> >> Maybe you could use the Explorer search facility to find the files? >> Doing so on my XP /2010 Express build environment found: >> >> C:\Program Files\Microsoft Visual Studio\VC\bin\vcvars32.bat >> C:\Program Files\Microsoft Visual Studio\VC\vcvarsall.bat >> C:\Program Files\Microsoft Visual Studio\Common7\Tools\vsvars32.bat >> >> vcvars32 and vsvars32 are identical, vsvarsall is a wrapper to setup the >> environment for cross compiling (e.g. amd64 on x86) by passing in extra >> parsm >> >> There is another simpler way however, in the Start Menu, under the Visual >> Studio Express item there should be an entry for "Visual Studio Command >> Prompt (2010)". Use that and the environment is set for you. >> >> I believe there are some issues around Visual Studio 2010 SP1 and the 7.1 >> SDK, generally around breaking the compilers. Google will lead you to some >> info. >> >> >> ___________________________________________________________________________ >> Sent via: Wireshark-dev mailing list <[email protected]> >> Archives: http://www.wireshark.org/lists/wireshark-dev >> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >> mailto:[email protected] >> ?subject=unsubscribe >> > > > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <[email protected]> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > > mailto:[email protected]?subject=unsubscribe<[email protected]?subject=unsubscribe> > > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <[email protected]> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:[email protected] > ?subject=unsubscribe >
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
