Compiling Python 2.6 on Arch

I am getting the following gcc error when compiling Python 2.6 from source:
gcc -pthread -c -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE -DSVNVERSION=\"`LC_ALL=C svnversion .`\" -o Modules/getbuildinfo.o ./Modules/getbuildinfo.c
gcc: error: directory": No such file or directory
make: *** [Modules/getbuildinfo.o] Error 1
Can anyone reproduce this issue? How do you fix this?

karol wrote:Are you using https://aur.archlinux.org/packages.php?ID=41809 ?
I tried installing from AUR, but I am getting the same error.

Similar Messages

Compiling Python with Alchemy

Hi there,
I'm trying to compile the latest Python 3.1rc2 on intel Mac OSX 10.5.7 using Alchemy 0.5a. During ./configure adl is throwing a couple of errors but the process doesn't die and pressing continue in the popup dialog allow it to complete the configure process.
When I then run 'make' it eventually dies with the following error:
./Modules/python.c:137: error: ‘FP_X_OFL’ undeclared (first use in this function)
gcc -Wl,--export-dynamic -o python.exe \
Modules/python.o \
libpython3.1.a -lsocket -lnsl -ldld -ldl -lpthread -lmpc -lm
llvm-ld: error: Cannot find linker input 'Modules/python.o'
/bin/sh: ./python.exe: No such file or directory
make: *** [sharedmods] Error 127
So for some reason it's referencing a .exe file which is obviously not present on the OSX platform. Anyone ran into this issue before?
Any suggestions or pointers are greatly appreciated.
Cheers,
Thijs

karol wrote:Are you using https://aur.archlinux.org/packages.php?ID=41809 ?
I tried installing from AUR, but I am getting the same error.

Python Dev setup for Arch + KDE ?

Hello.
First excuse my awfull English
I'm new to Arch and KDE, I've been using some GNOME distros before, like Fedora, but now that almost all the distros switched to GNOME3, I moved to Arch Linux and KDE,
In Gnome I used Gedit for almost all my development work (Just a hobby, I'm a teen who is learning, nothing serious), Gedit has some great AddOns and themes, like code Snippets, Embbed terminals, and so.
But now... I don't know if install Gedit in my KDE setup or use a native KDE tool like Kate.
I'm not a big fan of KDE software, but I'm trying to use GTK Apps the less.
Also I thougt in VIM and Emacs, but that's too much for me to learn at the moment, I want to center in programming for now.
Any recomendations ? I also program in C++ some times, but I want to learn Python well before do the jump to C++.
So... what tool should I use ? Which one do you use ?
Thanks.

@dysoco: You will have to work with the tool, and thus only you can know what's the best tool for you. No one can choose an editor for you. Just use whatever you like most and do not care for the toolkit of your editor.
Kate is much alike to GEdit. It has all the standard editor features, good syntax highlighting, automatic indentation, and a bunch of extensions for programmers, including code snippets, symbol browser and more. It certainly isn't a bad tool for Python programming, and nothing stands against using it.
Aside of these, there are also cream, geany, scite and much more, all suitable for programming. There are even fully fledged IDEs like Eclipse with Pydev or Eric. All of them are actively used, through Emacs and VIM are by far the most popular editors amongst Python programmers on Linux (probably even on all OS).
Btw, if you dislike KDE and its applications, why are you using it?! Not meaning to start a flame war, just being curious
Last edited by lunar (2011-10-11 10:47:56)

Trouble compiling python-scipy-svn

Can somebody point me in the right direction?? here is the copy and paste from right before it errors out.
customize UnixCCompiler
customize UnixCCompiler using build_ext
customize Gnu95FCompiler
customize Gnu95FCompiler using build_ext
building 'scipy.sparse._sparsetools' extension
compiling C++ sources
C compiler: g++ -pthread -DNDEBUG -g -O3 -Wall -march=i686 -mtune=generic -O2 -pipe -fPIC
compile options: '-ILib/sparse/sparsetools -I/usr/lib/python2.5/site-packages/numpy/core/include -I/usr/include/python2.5 -c'
g++: Lib/sparse/sparsetools/sparsetools_wrap.cxx
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'int SWIG_Python_ConvertPtr(PyObject*, void**, swig_type_info*, int)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1221: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1231: error: invalid conversion from 'const char*' to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* SWIG_Python_NewPointerObj(void*, swig_type_info*, int)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1329: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'char* pytype_string(PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1492: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1493: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1494: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1495: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1496: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1497: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1498: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1499: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1500: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1501: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1502: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1504: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx: At global scope:
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* _wrap_sort_csr_indices__SWIG_1(PyObject*, PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:18786: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* _wrap_sort_csc_indices__SWIG_1(PyObject*, PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:19295: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx:19297: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* _wrap_sort_csc_indices__SWIG_2(PyObject*, PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:19347: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* _wrap_sort_csc_indices__SWIG_3(PyObject*, PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:19402: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* _wrap_sort_csc_indices__SWIG_4(PyObject*, PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:19457: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* _wrap_sort_csc_indices__SWIG_5(PyObject*, PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:19512: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* _wrap_sort_csc_indices__SWIG_6(PyObject*, PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:19567: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'void SWIG_Python_FixMethods(PyMethodDef*, swig_const_info*, swig_type_info**, swig_type_info**)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:20206: error: invalid conversion from 'const char*' to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'int SWIG_Python_ConvertPtr(PyObject*, void**, swig_type_info*, int)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1221: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1231: error: invalid conversion from 'const char*' to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* SWIG_Python_NewPointerObj(void*, swig_type_info*, int)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1329: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'char* pytype_string(PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1492: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1493: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1494: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1495: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1496: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1497: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1498: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1499: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1500: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1501: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1502: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1504: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx: At global scope:
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx:1512: warning: deprecated conversion from string constant to 'char*'
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* _wrap_sort_csr_indices__SWIG_1(PyObject*, PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:18786: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* _wrap_sort_csc_indices__SWIG_1(PyObject*, PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:19295: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx:19297: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* _wrap_sort_csc_indices__SWIG_2(PyObject*, PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:19347: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* _wrap_sort_csc_indices__SWIG_3(PyObject*, PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:19402: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* _wrap_sort_csc_indices__SWIG_4(PyObject*, PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:19457: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* _wrap_sort_csc_indices__SWIG_5(PyObject*, PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:19512: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'PyObject* _wrap_sort_csc_indices__SWIG_6(PyObject*, PyObject*)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:19567: warning: dereferencing type-punned pointer will break strict-aliasing rules
Lib/sparse/sparsetools/sparsetools_wrap.cxx: In function 'void SWIG_Python_FixMethods(PyMethodDef*, swig_const_info*, swig_type_info**, swig_type_info**)':
Lib/sparse/sparsetools/sparsetools_wrap.cxx:20206: error: invalid conversion from 'const char*' to 'char*'
error: Command "g++ -pthread -DNDEBUG -g -O3 -Wall -march=i686 -mtune=generic -O2 -pipe -fPIC -ILib/sparse/sparsetools -I/usr/lib/python2.5/site-packages/numpy/core/include -I/usr/include/python2.5 -c Lib/sparse/sparsetools/sparsetools_wrap.cxx -o build/temp.linux-i686-2.5/Lib/sparse/sparsetools/sparsetools_wrap.o" failed with exit status 1
==> ERROR: Build Failed. Aborting...

Well, for one, perl is not a compiled language. You can if you want to, but it gains you few benefits. Google for "perl compiler" if you really must.
As for the second, do you know how the shebang line works in unix, and do you know what the -w option does for perl? The answer should reveal itself to you.
Make sure you "use strict;", it will catch many errors.

Python 2.5.1 in Arch

Recently I tried to compile ardour from the PKGBUILD in abs, but the build always failed for me. Very strange, I didn't modify anything in that PKGBUILD. Later I suspected that it might be caused by default build of python 2.5.1 in Arch, but I can't make sure of whether it is the root cause or not. So I post the steps I managed to compile ardour below:
1. I had the default build of python-2.5.1-1 and scons-0.96.95-2 installed and tried to makepkg ardour-2.0.2-1 from my /var/abs. makepkg always failed, with following error message:
patching file libs/libsndfile/configure
patching file libs/libsndfile/src/flac.c
scons: Reading SConscript files ...
scons: *** No tool named 'midl': not a Zip file
File "/root/src/extra/multimedia/ardour/src/ardour-2.0.2/SConstruct", line 16, in <module>
scons: Reading SConscript files ...
scons: *** No tool named 'midl': not a Zip file
File "/root/src/extra/multimedia/ardour/src/ardour-2.0.2/SConstruct", line 16, in <module>
(there is a small bug in ardour's PKGBUILD; it doesn't do the error check for the building process. Whether the build is ok or not, you always get a .tar.gz package for it)
2. First I tried to browse scons's source code and even installed the latest one from their official site(using makepkg & pacman -U). Still the same error.
3. I guessed the problem should be related to python. Fired up python shell and was surprised to find out that there is an entry for python 2.4 site-packages in sys.path. Upon my pure guess, I used pacman to remove all the packages under my /usr/lib/python2.4/site-packages/. Now even the directory /usr/lib/python2.4 didn't exist anymore(actually I was already using my scons mentioned in step 5 in this stage), but I still got the same error when makepkg ardour.
4. I checked the PKGBUILD and Makefile for python-2.5.1-1 and found out that the SITEPATH in Makefile would affect other python path settings(though I didn't know what these settings would do to the build process). I commented out the following line in the PKGBUILD for python and makepkg
sed -i 's#SITEPATH=#SITEPATH=:../python2.4/site-packages#' Makefile
5. Installed the newly compiled Python, but, unfortunately, scons-0.96.95-2 was installed to /usr/lib/python2.4/site-packages/. So I makepkged scons from source and installed my scons. (this time they were all installed to /usr/lib/python2.5/site-packages/)
6. Now ardour compiled!
Doesn't "sed -i 's#SITEPATH=#SITEPATH=:../python2.4/site-packages#' Makefile" just a hack for python version transition and should be removed when the transition is done? I found there are some binary package compiled for python 2.4, while some are compiled for python 2.5. Anyone has suggestion on this?
Is there any other method to compile ardour from source without recompile python and scons??(or it's just me who got this problem??)
Thanks in advance.

no issues at all. been using ardourvst since the old ardour. never had an issue with python.
I've been running ardour with vst support for 2 years now.
ardour2.0.2 builds and runs with no issue. I edit the PKGBUILD from extra, interupt the build, add the vst zip package to ../libs/fst and re-run makepkg.
never ever an issue with python or scons. I'm running the latest of all the the mentioned software with no issues.
from the ardour website:
This section applies only to people building Ardour 2.0 (not 0.99.X) and only for Linux/x86 platforms. At this time, you cannot run VST plugins in Ardour on OS X or Linux x86_64 platforms. Note that if you use your x86_64 system in 32 bit mode, that counts as x86, and things will work as expected.
Please note that it is illegal to build Ardour 2.0 with VST support and then distribute the binary to anyone else. This is because Steinberg continues to refuse to allow redistribution of the otherwise freely available VST SDK. It is therefore not possible for you to comply with the terms of the GPL (i.e. you cannot provide the person you distribute the binary to with all the source code required to build the binary). We hope that one day Steinberg/Yamaha will change the licensing to allow redistribution of the SDK, and then this silly restriction will go away.
Building Ardour 2.0 with VST support involves a few extra steps before the usual scons-based build.
1. Download the VST 2.3 SDK from Steinberg. At this time, we cannot provide you with any advice on where to get this from. Steinberg seems to regularly change the URL required to get the SDK. We recommend that you use google to search for it. Do not download the 2.4 or upcoming 3.0 SDK packages, since Ardour cannot currently use them.
2. put the VST SDK zip archive into libs/fst
3. make sure you have the Wine "development" package installed (typically called "wine-devel")
4. run scons VST=1
After a successful build, run scons install.
Running it
The command name for this version of Ardour is ardourvst, not ardour2 which is the non-VST supporting version. In all other ways, it should behave identically.
Where to install VST plugins
Ardour looks for VST plugins in the location(s) indicated by your environment variable
Last edited by funkmuscle (2007-05-24 13:10:46)

[solved] Problem compialing boost python example on Arch.

I have bean trying to compile the basic boost.python example program on arch, but g++ is spitting out errors stating that it cannot find Python.h and so on.
#include <boost/python.hpp>
char const* greet()
return "hello, world";
BOOST_PYTHON_MODULE(hello_ext)
using namespace boost::python;
def("greet", greet);
g++ boost_python_test.cpp
In file included from /usr/include/boost/python/detail/prefix.hpp:13,
from /usr/include/boost/python/args.hpp:8,
from /usr/include/boost/python.hpp:11,
from boost_python_test.cpp:1:
/usr/include/boost/python/detail/wrap_python.hpp:50:23: error: pyconfig.h: No such file or directory
/usr/include/boost/python/detail/wrap_python.hpp:75:24: error: patchlevel.h: No such file or directory
/usr/include/boost/python/detail/wrap_python.hpp:78:2: error: #error Python 2.2 or higher is required for this version of Boost.Python.
/usr/include/boost/python/detail/wrap_python.hpp:142:21: error: Python.h: No such file or directory
^C
tonnes of errors.
Last edited by Hessiess (2009-04-30 21:25:26)

JK3mp wrote:Don't forget to put SOLVED in the title on your solved issue's please.
Done

Is there a python-dev package?

I can't compile python-sexy from aur because python headers not found:
checking for headers required to compile python extensions... not found
configure: error: could not find Python headers
is there python-dev package in arch?
What can i do?
Last edited by gaara (2007-11-15 05:48:58)

I have base-devel and the problem continue, I found my python headers with python-config --cflags, but i don't know what does python-sexy not found those libraries
Last edited by gaara (2007-11-15 16:25:02)

64 bit python on Mac?

Hi folks, I was wondering if anyone has successfully installed a 64-bit version of python on Leopard. I'm pretty sure both python and MacOS are capable, but google failed me miserably on this count - every search I did ended up with some comment about libraries rather than instructions on compiling. My attempt to compile python from source with the following configuration options:
./configure --with-framework-name=Python64 --with-universal-archs='64-bit'
failed because of some missing libraries. So, is there a compiled version of 64 bit python anywhere?
Thanks,
Adam

Outside of Windows 64-bit drivers, and the level of support now in the latest BootCamp, I had Vista 64-bit for a few months. Some software is not yet 64-bit so I am holding back for now (Symantec, drivers, even Microsoft OneCare).
You shouldn't have any trouble as far as accessing RAM with XP Pro 64-bit.

Python without tk

Would it be possible to split the python package into one that does not require tk (and therefore X) to be installed? I'm a big fan of python and use it for server scripts and don't like running X on servers.
I believe all it would require is a "--without-tk" to the configure script in the PKGBUILD to produce a tk-less python package. At least that's what I do via abs.
Thanks in advance,
farphel

Xentac wrote:The difference between perl/perltk and python/pythontk is that perltk is actually a seperate module, pythontk is distributed with the base python tarball.
You're right about perl/perltk. However, I think the python/pythontk is a bit of a grey area. Python ships with Tk support (a module called Tkinter), but the only way it is built is if the host system already has Tcl/Tk installed. If Tk is not installed and you compile python from source, you do not get Tkinter (or IDLE). If python is built without Tkinter, it does not in any way affect python, its performance, or its usability. That's why I feel that having the python package require Tk is a mistake.
Xentac wrote:One of the package design decisions that's been around since before I started is that no packages would be artificially split. That is, nothing the upstream developers meant should be together should be split into seperate pieces. If the upstream developers split it, then we'd have two packages, otherwise we leave it as one.
Thanks for the clarification, Xentac. This sheds some insight onto why python requires Tk.
Xentac wrote:Splitting packages also makes for a maintenance nightmare.
Well, your point is valid for packages with many compile options, or possible dependencies on other software. In this case, I don't think it would be that bad to have to monitor upstream python release and rebuild an additional pythontk package. However, your point is well taken. Afterall, the reason why I'd rather see the python package split up is so that I (as an end-user) do not have to deal with it but would rather have an Arch package maintainer deal with it. I know that sounds lazy, but oneof the reasons I love Arch so much is that the package maintainers do such an excellent job keeping up with new versions and providing solid packages. I'd like to continue relying on them!
Xentac wrote:Arch's design goals is to be simple and cut out all the crap.
That's one of my peeves with this too. I consider Tk extra "crap". If I were to write a GUI using python, I would rather use pyGTK or pyQT (both of which are also platform independent). Of course this is a personal opinion.
Xentac wrote:I'm not voting either way here. I'm just clearing what I see as some misconceptions up. Please continue the arguing.
I'm guessing it will be difficult to rely on community opinion to drive this decision. How many professional python programmers are using Arch? Do they write GUIs using Tkinter? Would all of those people care to weigh in on the discussion? And yes, I basically program in python exclusively for my day job. I'm not saying that that entitles me to a better opinion. It's just that when it comes time to deploy my python applications on a sserver, I want my server to be as lean as possible. If I have to install X just to use a scripting language, then I feel that there is something wrong with the way it is being packaged. I don't like installing extra software cruft on my servers - it's just more software to monitor for local/remote exploits.
Anyway, I've stated my case and what I think is a good solution. There are workarounds for me such as the -d flag for pacman or rebuilding my package via abs (which I'm currently doing). I just feel that my point is valid and would love to see it adopted.
Cheers,
farphel

The Official Unofficial 'Arch is Best' Thread

(Arch is the best distro ever...)
...at least for me. i know that one should not make claims that this or that distro is the best os. my past 2,5 years have been a constant distro hopping. i've tried tons of distros, the only one that comes close to arch is gentoo, but my thinkpad is not that powerful (866mhz/256 mb ram) to wait for software to compile.
if there wasn't arch, i'd probably buy a mac. this is my third time with arch, but i don't think i'm going anywhere.
so please keep up the good work, i wish that the archlinux project goes on as long as possible (forever? )
probably irrelevant, just wanted to get this off my heart. thanks for reading[/b]

Arch needs a little more polishing(pacman errors on upgrading) and stop its "let's put things in thousands of different repos(AUR unsupported/community, TURs, current, extra, testing, unstable and never integrate OFFICIALLY things waited for months". (Yes I'm exaggerating)
For example, azureus is waiting to be in the official repos, at least in community...
What I also do not understand, is why devs have not yet built a structure so that devs can massively join the distro...
Apart from that, sure it is one of the most impressive distro I've seen so far, next only to Ubuntu.
I'm now trying(and really like) Sarge and I'm waiting for a Arch 1.0 release !!!

PKGBUILD parser in Python.

I've wrote PKGBUILD parser in Python and thought someone else might also want to use it. Here's a little example of how it works
# python
Python 2.5.2 (r252:60911, Jul 8 2008, 21:21:10)
[GCC 4.3.1 20080626 (prerelease)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pkgbuild
>>> p = pkgbuild.PKGBUILD('/home/piotrek/aurshell/xfburn-svn/PKGBUILD')
>>> p.parse_pkgname()
['xfburn-svn']
>>> p.parse_makedepends()
['gcc', 'xfce4-dev-tools', 'pkgconfig', 'subversion']
>>> p.parseall()
{'replaces': [], 'pkgname': ['xfburn-svn'], 'maintrainer': [], 'license': ['GPL'], 'source': [], 'makedepends': ['gcc', 'xfce4-dev-tools', 'pkgconfig', 'subversion'], 'provides': ['xfburn'], 'contributor': [" Jakub 'Icar' Jar\xc3\xb3\xc5\xbcek <[email protected]>"], 'depends': ['libburn', 'libisofs', 'libxfcegui4', 'thunar', 'gcc', 'xfce4-dev-tools', 'pkgconfig', 'subversion'], 'md5sums': [], 'flags': ['--prefix=/usr', '--sysconfdir=/etc'], 'build': ['build() {\n\ncd $startdir/src\n msg "Connecting to svn.xfce.org svn server...."\n svn co $_svntrunk $_svnmod\n\n msg "SVN checkout done or server timeout"\n msg "Starting make..."\n\n cp -R $startdir/src/$_svnmod $startdir/src/$_svnmod-build\n cd $startdir/src/$_svnmod-build\n\n ./autogen.sh --prefix=/usr --sysconfdir=/etc\n make\n make DESTDIR=$startdir/pkg install\n\n}'], 'install': ['xfburn.install'], 'conflicts': ['xfburn'], 'pkgver': ['5141'], 'arch': ['i686', 'x86_64'], 'pkgdesc': ['Xfburn is a simple CD/DVD burning tool based on libburnia libraries. It can blank CD-RWs, burn and create iso images, as well as burn personal compositions of data to either CD or DVD.'], 'pkgrel': ['1']}
>>> from pprint import pprint
>>> pprint(p.parseall())
{'arch': ['i686', 'x86_64'],
'build': ['build() {\n\ncd $startdir/src\n msg "Connecting to svn.xfce.org svn server...."\n svn co $_svntrunk $_svnmod\n\n msg "SVN checkout done or server timeout"\n msg "Starting make..."\n\n cp -R $startdir/src/$_svnmod $startdir/src/$_svnmod-build\n cd $startdir/src/$_svnmod-build\n\n ./autogen.sh --prefix=/usr --sysconfdir=/etc\n make\n make DESTDIR=$startdir/pkg install\n\n}'],
'conflicts': ['xfburn'],
'contributor': [" Jakub 'Icar' Jar\xc3\xb3\xc5\xbcek <[email protected]>"],
'depends': ['libburn',
'libisofs',
'libxfcegui4',
'thunar',
'gcc',
'xfce4-dev-tools',
'pkgconfig',
'subversion'],
'flags': ['--prefix=/usr', '--sysconfdir=/etc'],
'install': ['xfburn.install'],
'license': ['GPL'],
'maintrainer': [],
'makedepends': ['gcc', 'xfce4-dev-tools', 'pkgconfig', 'subversion'],
'md5sums': [],
'pkgdesc': ['Xfburn is a simple CD/DVD burning tool based on libburnia libraries. It can blank CD-RWs, burn and create iso images, as well as burn personal compositions of data to either CD or DVD.'],
'pkgname': ['xfburn-svn'],
'pkgrel': ['1'],
'pkgver': ['5141'],
'provides': ['xfburn'],
'replaces': [],
'source': []}

Basic support for simple bash variables usage isn't that hard to add. But it's working only for $<word> syntax:
macbook # python pkgbuild.py /home/piotrek/aurshell/python-markdown/PKGBUILD
{'arch': ['x86_64', 'i686'],
'build': ['build() {\n cd ${startdir}/src/markdown-$_pkgver\n python setup.py install --root=$startdir/pkg\n}'],
'conflicts': [],
'contributor': ' Lauri J\xc3\xa4ntti <[email protected]>',
'depends': ['python'],
'flags': [],
'install': [],
'license': [],
'maintrainer': [],
'makedepends': [],
'md5sums': ['99b1721d723e8c64381fc023d23b202a'],
'pkgdesc': 'A Python implementation of John Gruber',
'pkgname': 'python-markdown',
'pkgrel': '1',
'pkgver': '1.7',
'provides': [],
'replaces': [],
'source': ['http://dfn.dl.sourceforge.net/sourceforge/python-markdown/markdown-1.7.zip']}
macbook # cat /home/piotrek/aurshell/python-markdown/PKGBUILD
# Contributor: Lauri Jäntti <[email protected]>
pkgname=python-markdown
pkgver=1.7
_pkgver=1.7
pkgrel=1
pkgdesc="A Python implementation of John Gruber's Markdown. current version implements all Markdown syntax features and fully passes Markdown Test Suite 1.0."
url="http://www.freewisdom.org/projects/python-markdown/"
license="custom"
arch=(x86_64 i686)
depends=('python')
source=(http://dfn.dl.sourceforge.net/sourceforge/python-markdown/markdown-$pkgver.zip)
md5sums=('99b1721d723e8c64381fc023d23b202a')
build() {
cd ${startdir}/src/markdown-$_pkgver
python setup.py install --root=$startdir/pkg

Qpspmanager compile issue

anyone here have a psp, or use qpspmanager? i wasn't sure exactly where the best place to post this was. but i've had the source for qpspmanager 2.0.2 for a while now. it compiled fine on 2 machines running 32bit arch. but it won't compile on my 64 bit arch install on my main rig, which is where i would be able to use it. i figured which all this qt jabber going on, and qpsp 2 being qt4 based, i would try to compile it again. and it gives me the same trouble. i tried renaming the makefile and running qmake to build a new one, but still won't compile
just wondering if anyone here who uses it, or would be interested in using it may be able to lend a hand since i really don't know what im doing

this help?
sh-3.2$ cd /home/urmom/Desktop/qpspmanager-2.0.2
sh-3.2$ make
make: *** No rule to make target `/opt/qt4/mkspecs/linux-g++/qmake.conf', needed by `Makefile'. Stop.
sh-3.2$ qmake
sh-3.2$ make
g++ -c -pipe -march=x86-64 -mtune=generic -O2 -pipe -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt/mkspecs/linux-g++ -I. -I/usr/include/QtCore -I/usr/include/QtCore -I/usr/include/QtGui -I/usr/include/QtGui -I/usr/include -I. -Isrc -Iobj -Iui -o obj/moc_backupswidget.o obj/moc_backupswidget.cpp
g++ -c -pipe -march=x86-64 -mtune=generic -O2 -pipe -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt/mkspecs/linux-g++ -I. -I/usr/include/QtCore -I/usr/include/QtCore -I/usr/include/QtGui -I/usr/include/QtGui -I/usr/include -I. -Isrc -Iobj -Iui -o obj/moc_addisodialog.o obj/moc_addisodialog.cpp
/usr/bin/rcc -name qpspmanager src/qpspmanager.qrc -o resources/qrc_qpspmanager.cpp
g++ -c -pipe -march=x86-64 -mtune=generic -O2 -pipe -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt/mkspecs/linux-g++ -I. -I/usr/include/QtCore -I/usr/include/QtCore -I/usr/include/QtGui -I/usr/include/QtGui -I/usr/include -I. -Isrc -Iobj -Iui -o obj/qrc_qpspmanager.o resources/qrc_qpspmanager.cpp
g++ -Wl,-rpath,/usr/lib -o bin/QPSPManager obj/main.o obj/mainwindow.o obj/optionsmanager.o obj/applicationsmanager.o obj/optionswidget.o obj/qpspmanager.o obj/videosmanager.o obj/videoswidget.o obj/applicationswidget.o obj/backupswidget.o obj/isoswidget.o obj/backupsmanager.o obj/pspapplication.o obj/filemanager.o obj/isosmanager.o obj/qpspmanagerexception.o obj/qpspmanagerpbpexception.o obj/video.o obj/encodevideodialog.o obj/isocompressor.o obj/psxconverter.o obj/addisodialog.o obj/videojob.o obj/pspendian.o obj/videojobmanager.o obj/savegame.o obj/helpwidget.o obj/whichunix.o obj/fsusageunix.o obj/moc_mainwindow.o obj/moc_optionsmanager.o obj/moc_applicationsmanager.o obj/moc_optionswidget.o obj/moc_qpspmanager.o obj/moc_videosmanager.o obj/moc_videoswidget.o obj/moc_applicationswidget.o obj/moc_backupsmanager.o obj/moc_backupswidget.o obj/moc_isoswidget.o obj/moc_encodevideodialog.o obj/moc_addisodialog.o obj/moc_videojob.o obj/moc_videojobmanager.o obj/moc_isosmanager.o obj/moc_helpwidget.o obj/qrc_qpspmanager.o -L/usr/lib -lQtGui -L/usr/lib -L/usr/X11R6/lib -lpng -lSM -lICE -pthread -pthread -lXi -lXrender -lXrandr -lXfixes -lXcursor -lXinerama -lfreetype -lfontconfig -lXext -lX11 -lQtCore -lz -lm -pthread -lgthread-2.0 -lrt -lglib-2.0 -ldl -lpthread
collect2: ld terminated with signal 11 [Segmentation fault]
/usr/bin/ld: i386 architecture of input file `obj/main.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/mainwindow.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/optionsmanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/applicationsmanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/optionswidget.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/qpspmanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/videosmanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/videoswidget.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/applicationswidget.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/backupswidget.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/isoswidget.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/backupsmanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/pspapplication.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/filemanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/isosmanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/qpspmanagerexception.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/qpspmanagerpbpexception.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/video.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/encodevideodialog.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/isocompressor.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/psxconverter.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/addisodialog.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/videojob.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/pspendian.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/videojobmanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/savegame.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/helpwidget.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/whichunix.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/fsusageunix.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_mainwindow.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_optionsmanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_applicationsmanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_optionswidget.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_qpspmanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_videosmanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_videoswidget.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_applicationswidget.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_backupsmanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_isoswidget.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_encodevideodialog.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_videojob.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_videojobmanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_isosmanager.o' is incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file `obj/moc_helpwidget.o' is incompatible with i386:x86-64 output
obj/mainwindow.o: In function `Ui_MainWindow::retranslateUi(QMainWindow*)':
mainwindow.cpp:(.text._ZN13Ui_MainWindow13retranslateUiEP11QMainWindow[Ui_MainWindow::retranslateUi(QMainWindow*)]+0x70): undefined reference to `operator new(unsigned int)'
mainwindow.cpp:(.text._ZN13Ui_MainWindow13retranslateUiEP11QMainWindow[Ui_MainWindow::retranslateUi(QMainWindow*)]+0x180): undefined reference to `operator new(unsigned int)'
mainwindow.cpp:(.text._ZN13Ui_MainWindow13retranslateUiEP11QMainWindow[Ui_MainWindow::retranslateUi(QMainWindow*)]+0x293): undefined reference to `operator new(unsigned int)'
mainwindow.cpp:(.text._ZN13Ui_MainWindow13retranslateUiEP11QMainWindow[Ui_MainWindow::retranslateUi(QMainWindow*)]+0x3a9): undefined reference to `operator new(unsigned int)'
mainwindow.cpp:(.text._ZN13Ui_MainWindow13retranslateUiEP11QMainWindow[Ui_MainWindow::retranslateUi(QMainWindow*)]+0x4bf): undefined reference to `operator new(unsigned int)'
obj/mainwindow.o:mainwindow.cpp:(.text._ZN13Ui_MainWindow13retranslateUiEP11QMainWindow[Ui_MainWindow::retranslateUi(QMainWindow*)]+0x5d5): more undefined references to `operator new(unsigned int)' follow
obj/filemanager.o: In function `FileManager::copyFile(QString, QString, bool)':
filemanager.cpp:(.text+0x1a50): undefined reference to `__divdi3'
obj/filemanager.o: In function `FileManager::copyFolder(QDir, QDir, bool)':
filemanager.cpp:(.text+0x2bb2): undefined reference to `operator new(unsigned int)'
obj/isosmanager.o: In function `ISOsManager::initComputerDir()':
isosmanager.cpp:(.text+0xaef): undefined reference to `operator new(unsigned int)'
obj/isosmanager.o: In function `ISOsManager::initPSPDir()':
isosmanager.cpp:(.text+0x111f): undefined reference to `operator new(unsigned int)'
obj/isosmanager.o: In function `ISOsManager::scanDir(QString, QList<QString>&)':
isosmanager.cpp:(.text+0x1541): undefined reference to `operator new(unsigned int)'
obj/isosmanager.o: In function `QList<QPair<QString, long long> >::append(QPair<QString, long long> const&)':
isosmanager.cpp:(.text._ZN5QListI5QPairI7QStringxEE6appendERKS2_[QList<QPair<QString, long long> >::append(QPair<QString, long long> const&)]+0x35): undefined reference to `operator new(unsigned int)'
obj/encodevideodialog.o:encodevideodialog.cpp:(.text._ZN20Ui_EncodeVideoDialog7setupUiEP7QDialog[Ui_EncodeVideoDialog::setupUi(QDialog*)]+0xc5): more undefined references to `operator new(unsigned int)' follow
obj/isocompressor.o: In function `ISOCompressor::check_file_size(_IO_FILE*, int&, ISOCompressor::ciso_header&)':
isocompressor.cpp:(.text+0x112): undefined reference to `__divdi3'
obj/isocompressor.o: In function `ISOCompressor::expandISO(QString, QString)':
isocompressor.cpp:(.text+0x331): undefined reference to `__udivdi3'
obj/addisodialog.o: In function `Ui_AddISODialog::setupUi(QDialog*)':
addisodialog.cpp:(.text._ZN15Ui_AddISODialog7setupUiEP7QDialog[Ui_AddISODialog::setupUi(QDialog*)]+0xbc): undefined reference to `operator new(unsigned int)'
addisodialog.cpp:(.text._ZN15Ui_AddISODialog7setupUiEP7QDialog[Ui_AddISODialog::setupUi(QDialog*)]+0x115): undefined reference to `operator new(unsigned int)'
addisodialog.cpp:(.text._ZN15Ui_AddISODialog7setupUiEP7QDialog[Ui_AddISODialog::setupUi(QDialog*)]+0x173): undefined reference to `operator new(unsigned int)'
addisodialog.cpp:(.text._ZN15Ui_AddISODialog7setupUiEP7QDialog[Ui_AddISODialog::setupUi(QDialog*)]+0x1fd): undefined reference to `operator new(unsigned int)'
addisodialog.cpp:(.text._ZN15Ui_AddISODialog7setupUiEP7QDialog[Ui_AddISODialog::setupUi(QDialog*)]+0x293): undefined reference to `operator new(unsigned int)'
obj/addisodialog.o:addisodialog.cpp:(.text._ZN15Ui_AddISODialog7setupUiEP7QDialog[Ui_AddISODialog::setupUi(QDialog*)]+0x32f): more undefined references to `operator new(unsigned int)' follow
obj/moc_backupswidget.o:(.rodata._ZTV13BackupsWidget[vtable for BackupsWidget]+0x1d0): undefined reference to `non-virtual thunk to BackupsWidget::~BackupsWidget()'
obj/moc_backupswidget.o:(.rodata._ZTV13BackupsWidget[vtable for BackupsWidget]+0x1d8): undefined reference to `non-virtual thunk to BackupsWidget::~BackupsWidget()'
obj/moc_mainwindow.o:(.rodata._ZTV10MainWindow[vtable for MainWindow]+0xf4): undefined reference to `non-virtual thunk to QWidget::devType() const'
obj/moc_mainwindow.o:(.rodata._ZTV10MainWindow[vtable for MainWindow]+0xf8): undefined reference to `non-virtual thunk to QWidget::paintEngine() const'
obj/moc_mainwindow.o:(.rodata._ZTV10MainWindow[vtable for MainWindow]+0xfc): undefined reference to `non-virtual thunk to QWidget::metric(QPaintDevice::PaintDeviceMetric) const'
obj/moc_optionswidget.o:(.rodata._ZTV13OptionsWidget[vtable for OptionsWidget]+0xf0): undefined reference to `non-virtual thunk to QWidget::devType() const'
obj/moc_optionswidget.o:(.rodata._ZTV13OptionsWidget[vtable for OptionsWidget]+0xf4): undefined reference to `non-virtual thunk to QWidget::paintEngine() const'
obj/moc_optionswidget.o:(.rodata._ZTV13OptionsWidget[vtable for OptionsWidget]+0xf8): undefined reference to `non-virtual thunk to QWidget::metric(QPaintDevice::PaintDeviceMetric) const'
obj/moc_videoswidget.o:(.rodata._ZTV12VideosWidget[vtable for VideosWidget]+0xf0): undefined reference to `non-virtual thunk to QWidget::devType() const'
obj/moc_videoswidget.o:(.rodata._ZTV12VideosWidget[vtable for VideosWidget]+0xf4): undefined reference to `non-virtual thunk to QWidget::paintEngine() const'
obj/moc_videoswidget.o:(.rodata._ZTV12VideosWidget[vtable for VideosWidget]+0xf8): undefined reference to `non-virtual thunk to QWidget::metric(QPaintDevice::PaintDeviceMetric) const'
obj/moc_applicationswidget.o:(.rodata._ZTV18ApplicationsWidget[vtable for ApplicationsWidget]+0xf0): undefined reference to `non-virtual thunk to QWidget::devType() const'
obj/moc_applicationswidget.o:(.rodata._ZTV18ApplicationsWidget[vtable for ApplicationsWidget]+0xf4): undefined reference to `non-virtual thunk to QWidget::paintEngine() const'
obj/moc_applicationswidget.o:(.rodata._ZTV18ApplicationsWidget[vtable for ApplicationsWidget]+0xf8): undefined reference to `non-virtual thunk to QWidget::metric(QPaintDevice::PaintDeviceMetric) const'
obj/moc_isoswidget.o:(.rodata._ZTV10ISOsWidget[vtable for ISOsWidget]+0xf0): undefined reference to `non-virtual thunk to QWidget::devType() const'
obj/moc_isoswidget.o:(.rodata._ZTV10ISOsWidget[vtable for ISOsWidget]+0xf4): undefined reference to `non-virtual thunk to QWidget::paintEngine() const'
obj/moc_isoswidget.o:(.rodata._ZTV10ISOsWidget[vtable for ISOsWidget]+0xf8): undefined reference to `non-virtual thunk to QWidget::metric(QPaintDevice::PaintDeviceMetric) const'
obj/moc_encodevideodialog.o:(.rodata._ZTV17EncodeVideoDialog[vtable for EncodeVideoDialog]+0xfc): undefined reference to `non-virtual thunk to QWidget::devType() const'
obj/moc_encodevideodialog.o:(.rodata._ZTV17EncodeVideoDialog[vtable for EncodeVideoDialog]+0x100): undefined reference to `non-virtual thunk to QWidget::paintEngine() const'
obj/moc_encodevideodialog.o:(.rodata._ZTV17EncodeVideoDialog[vtable for EncodeVideoDialog]+0x104): undefined reference to `non-virtual thunk to QWidget::metric(QPaintDevice::PaintDeviceMetric) const'
obj/moc_helpwidget.o:(.rodata._ZTV10HelpWidget[vtable for HelpWidget]+0xf0): undefined reference to `non-virtual thunk to QWidget::devType() const'
obj/moc_helpwidget.o:(.rodata._ZTV10HelpWidget[vtable for HelpWidget]+0xf4): undefined reference to `non-virtual thunk to QWidget::paintEngine() const'
obj/moc_helpwidget.o:(.rodata._ZTV10HelpWidget[vtable for HelpWidget]+0xf8): undefined reference to `non-virtual thunk to QWidget::metric(QPaintDevice::PaintDeviceMetric) const'
make: *** [bin/QPSPManager] Error 1

Slackware TGZ to Arch Linux Package Converter

I have two programs that interest me (LilyPond and Battle for Wesnoth) that don't have Arch Linux packages and compiling them would involve hunting everywhere for obscure dependencies (LilyPond in particular) so I just downloaded the Slackware packages, inspected them and found that by unzipping them onto the root folder (as superuser) and running the install script (if there is one) I can get them to run with minimal fuss.
Has the idea of making a Slackware to Arch package converter been brought up before? Is there any problems with this? (Slackware is i386-optimised if I remember correctly, but I think it's still worth it since there is more Slackware packages than Arch Linux ones out there.)

i3839 wrote:Flames?? Where? You sure you didn't misread something?
Probably.
Here's what I read, admitting that it doesn't seem quite as bad the second time around...:
Oh? All I was hearing is that Arch already has enough packages, and that the devs are overloaded and almost down.
"you don't know which way is up, you contradict yourself while continuing to ignore the problems and aren't fixing anything".
Also getting custom packages into Arch's official repository seems a bit hard currently, not to mention that it's totally unclear how to do that (drop it in incomming and wait a year? Lotto?).
"The system isn't working and you haven't done anything to try to fix it. I haven't read or noticed any of the threads illustrating that this topic has been argued to death and isn't going unnoticed"
Maintaining packages is the most work, and every distro maintains the same packages over and over again. Tell me why to not use good, working packages from another sane distro?
"The other distros are better."
(Personally, I don't care if anybody likes another distro better, but if so, use it instead, don't talk about it)
Changing GCC often gives the same problem as updating to new major libraries. Simply leave the old GCC libs or make a seperate package for them. Currently it's rather impossible in Arch to install new packages with an outdated system, if that's solved then it's also easy to use Slackware packages.
"The Arch philosophy of keeping packages stable but up to date is just plain wrong. I don't bother to pacman -Syu before I mention problems."
Of course if would be best if there was a nice, good binary package standard that works on all distros, so that the application makers can make and maintain the packages themselves, but that's utopia (paths are too often hardcoded for instance).
"hey, I do have some good ideas".
It isn't a matter of being able to do something or not, it's a matter of convenience. All programs should be relative easy to compile from source, but that doesn't mean that everyone should compile all programs themselves.
"There aren't enough Arch binaries to go around"
OR:
"ABS sucks"
OR:
"Hold my hand, I can't compile."
OR:
"I use Arch cause I don't like Gentoo". :-D
Yeah, some of that is a little (or quite, or even very) harsh, you can blame it on me rather than taking it to heart.
As for the slackware packages issue, I'm personally not writing a script to convert them; I've never used slackware in my life. The idea has merit, but I get tired of people discussing pros and cons and not doing anything. I think that's because I'm about as bad as anyone on that front, possibly worse.
Dusty

Question about kernel compilation from wiki

Hello,
I compile kernel in line with arch wiki (http://wiki.archlinux.org/index.php/Ker … rom_Source). In paragraph '2. With makepkg and pacman (Recommended)' are lines:
mv [kernel location]/* src/
cp -r [kernel location]/* src/
Does it make sense? First I move [kernel location] to src/ (I think it should be '/src/') and then I copy nonexistent [kernel location] to the same path.
Thanks
#edit:
I looked through word 'either' So now I'm not sure with this:
(my build directory is ~/kernelbuild)
1. in ~/kernelbuild create 'src' directory
2. copy ~/kernelbuild/linux-2.6.30.5/* src/
Am I right?
Last edited by cinan (2009-08-22 12:16:34)

Commands are correct, but as I said I was little confused about names/terms (eg kernel location-kernel source, making directory usr). I hope the wiki page will be more clear for users who never compiled custom kernel.

Good instructions for making a GCC cross compiler?

Hi
I think this might be the best place to ask this since people probably have been making cross compilers. I am interested in trying to make a cross compiler of GCC targetting Plan9/i386. There is an old 3.0 version of GCC (http://cm.bell-labs.com/sources/extra/gcc/) ported to Plan9.
The thing that confuses me a bit about cross compilers is the use of binutils for the target architecture. How does that actually work? The host OS/architecture would not be able to execute those binaries. It feels a bit like a chicken-and-egg issure and I am not really sure how to get started. I have been trying to read up a bit on the PKGBUILDs for cross-arm but the whole theoretical issue of how to actually get the thing working in the first place is still a bit unclear to me.
Some good instructions/links/help would be appreciated
I could post my temporary PKGBUILD here if people want to help out with the actual build...

A small update to my attempts:
This is my binutils package, it has failed at multiple levels during my attempts. The binutils ported to Plan9 are relatively old so some stuff needs to be patched up to build. Now it fails on not being able to recognize arlex.o . This seems a bit odd I think.
# Adapted from cross-arm-elf, cross-i686-pc-gnu and cross-i686-pc-mingw32
pkgname=cross-i386-plan9-binutils
pkgver=2.11.2
pkgrel=1
pkgdesc="The GNU Compiler Collection - Cross compiler for Plan9 i386 target"
arch=('i686' 'x86_64')
license=('GPL')
url="http://plan9.bell-labs.com/wiki/plan9/porting_alien_software_to_plan_9/index.html"
depends=('glibc' 'zlib')
options=('!libtool' '!distcc' '!ccache')
source=('http://plan9.bell-labs.com/sources/extra/gcc/gnusrc.tgz' \
'bucommh.patch')
md5sums=('39d23b7223b68de4cf333205257112ce' \
'2945c4e40dbcd966217ed1349195e312')
_target=i386-lucent-plan9
_sysroot=/usr/lib/cross-${_target}
build() {
rm -rf ${srcdir}/build
mkdir ${srcdir}/build #starting fresh
msg "building and packaging binutils"
cp -ar ${srcdir}/binutils-2.11.2/* ${srcdir}/build/
cd ${srcdir}/build
msg "cheating broken references to Plan9-ported GNU binutils"
ln -s /usr/bin/ar "${_target}-ar"
ln -s /usr/bin/as "${_target}-as"
ln -s /usr/bin/ld "${_target}-ld"
ln -s /usr/bin/ranlib "${_target}-ranlib"
PATH=${srcdir}/build:$PATH
CFLAGS='-O2 -static'
msg "patching up stuff"
cd ${srcdir}/build/binutils
patch bucomm.h -i $srcdir/bucommh.patch
msg "going back to build directory and start configure"
cd ${srcdir}/build
./configure --prefix=${_sysroot} --bindir=/usr/bin \
--with-sysroot=${_sysroot} \
--build=$CHOST --host=$CHOST --target=${_target} \
--with-gcc --with-gnu-as --with-gnu-ld \
--enable-shared --without-included-gettext \
--disable-nls --disable-debug
msg "fixing some corrupt libraries"
cp /usr/lib/libiberty.a ${srcdir}/build/libiberty/
msg "finally making the actual binutils"
cd ${srcdir}/build
make
make DESTDIR=$pkgdir/ install
# clean-up cross compiler root
rm -r ${pkgdir}/${_sysroot}/share/{info,man}
# needed for gcc build
install -dm755 ${pkgdir}/${_sysroot}/include
this is the bucommh.patch:
81c81
< extern char *sbrk ();
> extern void *sbrk ();
Last edited by W.F.Cody (2011-09-13 18:57:17)

Compiling Python 2.6 on Arch

Similar Messages

Maybe you are looking for