Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As a test I compiled xcb-proto with python3 (I had to remove python2 first). Then I compiled libxcb with no problem.
So it seems something is wrong with the file /usr/lib/python3.3/site-packages/xcbgen/xtypes.py on your system.
I ran diff on the newly compiled version and a freshly untarred version of this file.
Code:
$ diff -u xtypes.py ../../xcb-proto-1.9-old/xcbgen/xtypes.py
--- xtypes.py 2013-11-07 14:14:12.000000000 +0100
+++ ../../xcb-proto-1.9-old/xcbgen/xtypes.py 2013-12-02 19:31:35.208247662 +0100
@@ -76,7 +76,7 @@
complex_type.fields.append(new_field)
def make_fd_of(self, module, complex_type, fd_name):
- '''
+ '''
Method for making a fd member of a structure.
'''
new_fd = Field(self, module.get_type_name('INT32'), fd_name, True, False, False, None, True)
As you can see there is a slight difference of the indentation. Maybe you should recompile it and see if you get the right version. So _don't_ just copy this file from the sources, because that is the faulty version.
(Sorry for changing back and forth. I'm bit confused about this...)
Or you can try to correct it. The only differens is the ''' on line 79, but python is very strict about how much indented it should be, and not mixing tabs and spaces.
Edit2: The more I think about this the more strange it seems, how the file could be changed. I can't see anything in the Makefile about changing it.
It should be 8 spaces, the faulty version has 4 spaces and one tab.
As a test I compiled xcb-proto with python3 (I had to remove python2 first). Then I compiled libxcb with no problem.
So it seems something is wrong with the file /usr/lib/python3.3/site-packages/xcbgen/xtypes.py on your system.
I ran diff on the newly compiled version and a freshly untarred version of this file.
Code:
$ diff -u xtypes.py ../../xcb-proto-1.9-old/xcbgen/xtypes.py
--- xtypes.py 2013-11-07 14:14:12.000000000 +0100
+++ ../../xcb-proto-1.9-old/xcbgen/xtypes.py 2013-12-02 19:31:35.208247662 +0100
@@ -76,7 +76,7 @@
complex_type.fields.append(new_field)
def make_fd_of(self, module, complex_type, fd_name):
- '''
+ '''
Method for making a fd member of a structure.
'''
new_fd = Field(self, module.get_type_name('INT32'), fd_name, True, False, False, None, True)
As you can see there is a slight difference of the indentation. Maybe you should recompile it and see if you get the right version. So _don't_ just copy this file from the sources, because that is the faulty version.
(Sorry for changing back and forth. I'm bit confused about this...)
Or you can try to correct it. The only differens is the ''' on line 79, but python is very strict about how much indented it should be, and not mixing tabs and spaces.
Edit2: The more I think about this the more strange it seems, how the file could be changed. I can't see anything in the Makefile about changing it.
It should be 8 spaces, the faulty version has 4 spaces and one tab.
i decided to remove python and install it again, but while configuring i've got an error:
Code:
....
Python/_warnings.c
/bin/mkdir -p Include
python3.3 ./Parser/asdl_c.py -h include ./Parser/Python.asdl
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Fatal Python error: Py_Initialize: Unable to get the locale encoding
ImportError: No module named 'encodings'
make: *** [Include/Python-ast.h] Aborted
...]#
I havn't installed optional Valgrind, berkeley, openssl, sqlite.
I ran across that error as well. I have everything built as the book states in 7.4 stable BLFS, but libxcb still refuses to budge. Very disturbing this error is.
Remove python completely. If configure finds python on your system, it'll use it. If it doesn't find it, it'll instead use the newly compiled binary.
There are some hardship with it. I removed python folders from /usr/lib and /usr/share and /usr/lib/libpython3.3m.so, /usr/lib/libpython.so. But whe i try to locate "*python*" there are folders where there r python files:
No other package has files in /usr/include/python3.3m.
The packages that has files in /usr/lib/python3.3 is:
pyalpm 0.6.2-1
python3-beautifulsoup4 4.3.2-1
python3-setuptools 1.3-1
I think the most important are the files in /usr/bin, especially /usr/bin/python3.3, so that configure doesn't find python.
No other package has files in /usr/include/python3.3m.
The packages that has files in /usr/lib/python3.3 is:
pyalpm 0.6.2-1
python3-beautifulsoup4 4.3.2-1
python3-setuptools 1.3-1
I think the most important are the files in /usr/bin, especially /usr/bin/python3.3, so that configure doesn't find python.
This files/folders were removed before reconfiguring python package, but the error is appeared. So.. lets try to understand, what's python wants. Google shows me such pages like this {http://www.linuxforums.org/forum/red-hat-fedora-linux/138085-how-uninstall-python.html} All i knowed from them is "If you remove the python that was installed by your distro, you will break your system so if you do not want to end up reinstalling your OS, leave it as it is." I find gd article..Will read it at home) {http://answers.oreilly.com/topic/1243-how-to-configure-python/}
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
BLFS libxcb-1.9.3 make error
