Here is my train of thought on the building. My setup: python2 AND python (which is python 3.2), located in /usr/bin/ Builds are done by way of "PKGBUILDs" which contain functions called "build" that do the compiling.
For brevities sake i DLed the source from the repo just once. The first "vanilla" attempt is using just the autogen.sh and configure commands http://paste.pocoo.org/raw/356159/ It fails, as the python binary is python 3. Adding the quick sed hack to use python2 binary in the PKGBUILD yields some results: http://paste.pocoo.org/raw/356165/ Yet still fails at: File "../../tools/ncp2222.py", line 207 if highest_var > global_highest_var: ^ TabError: inconsistent use of tabs and spaces in indentation. I remove the python2 package, and with only python 3 installed repeat the process. http://paste.pocoo.org/raw/356168/ Fails with that same error in autogen that was fixed by switching over to the python2 binary. -ptchinster On Wed, Mar 16, 2011 at 12:30 PM, ptchinster <[email protected]> wrote: > Greetings, > > I am the maintainer for the svn version of wireshark in the Arch Linux > User Repo (AUR). Arch has both python version 2 and 3 in its main > repos (package 'python' is v3 and package 'python2' is v2, as many > packages still require version 2). > > When a system only has python2 installed i can easily build wireshark. > However, if python (v3) is also installed, the build will fail as it > attempts to use the /usr/bin/python interpreter, which is of course v3 > of python. > > Is there a way to *force* the location of python to be > /usr/bin/python2 ? I've tried several different ways with configure's > --with-python flag but have been unsuccessful so far. > > -ptchinster > > -- > "Somewhere, something incredible is waiting to be known." --Carl Sagan > "Keep on rockin' in the free world." -- Neil Young > -- "Somewhere, something incredible is waiting to be known." --Carl Sagan "Keep on rockin' in the free world." -- Neil Young ___________________________________________________________________________ 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
