lxml

building lxml failed due to problem with architecture type

Asked by Roland Hedberg

I can't build lxml from source.
I run OS X 10.5.4 on an Intel machine.

During the build I get lots of errors on the compilation of src/lxml/lxml.etree.c and eventually it all ends with:
lipo: can't figure out the architecture type of: /var/folders/rV/rVVBSX2U2Ri30k+BYmxEHU+++TQ/-Tmp-//ccJ0kYY7.out

Basically I have the same problem with easy_install

 $ easy_install lxml==dev
Searching for lxml==dev
Reading http://pypi.python.org/simple/lxml/
Reading http://codespeak.net/lxml
Best match: lxml dev
Downloading http://codespeak.net/svn/lxml/trunk#egg=lxml-dev
Doing subversion checkout from http://codespeak.net/svn/lxml/trunk to /var/folders/rV/rVVBSX2U2Ri30k+BYmxEHU+++TQ/-Tmp-/easy_install-ZmCjQy/trunk
Processing trunk
Running setup.py -q bdist_egg --dist-dir /var/folders/rV/rVVBSX2U2Ri30k+BYmxEHU+++TQ/-Tmp-/easy_install-ZmCjQy/trunk/egg-dist-tmp-vi-gKW
Building lxml version 2.2.alpha1-57839.
NOTE: Trying to build without Cython, pre-generated 'src/lxml/lxml.etree.c' needs to be available.
Using build configuration of libxslt 1.1.12
Building against libxml2/libxslt in the following directory: /usr/lib
warning: no files found matching 'lxml.etree.c' under directory 'src/lxml'
warning: no files found matching 'lxml.objectify.c' under directory 'src/lxml'
warning: no files found matching 'lxml.etree.h' under directory 'src/lxml'
warning: no files found matching 'lxml.etree_api.h' under directory 'src/lxml'
warning: no files found matching '*.html' under directory 'doc'
powerpc-apple-darwin9-gcc-4.0.1: src/lxml/lxml.etree.c: No such file or directory
powerpc-apple-darwin9-gcc-4.0.1: no input files
i686-apple-darwin9-gcc-4.0.1: src/lxml/lxml.etree.c: No such file or directory
i686-apple-darwin9-gcc-4.0.1: no input files
lipo: can't figure out the architecture type of: /var/folders/rV/rVVBSX2U2Ri30k+BYmxEHU+++TQ/-Tmp-//cc8s6Iqb.out
error: Setup script exited with error: command 'gcc' failed with exit status 1

Question information

Language:
English Edit question
Status:
Answered
For:
lxml Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
scoder (scoder) said : 		#1

Roland Hedberg wrote:
> [...]
> Building lxml version 2.2.alpha1-57839.
> NOTE: Trying to build without Cython, pre-generated 'src/lxml/lxml.etree.c' needs to be available.
> [...]
> warning: no files found matching 'lxml.etree.c' under directory 'src/lxml'

You trying to build an unreleased SVN version of lxml without having Cython
installed. Please read the build documentation.

http://codespeak.net/lxml/build.html

Stefan

Revision history for this message
Roland Hedberg (roland-hedberg) said : 		#2

Stefan Behnel wrote:
> Your question #44244 on lxml changed:
> https://answers.launchpad.net/lxml/+question/44244
>
> Status: Open => Answered
>
> Stefan Behnel proposed the following answer:
>
> Roland Hedberg wrote:
>> [...]
>> Building lxml version 2.2.alpha1-57839.
>> NOTE: Trying to build without Cython, pre-generated 'src/lxml/lxml.etree.c' needs to be available.
>> [...]
>> warning: no files found matching 'lxml.etree.c' under directory 'src/lxml'
>
> You trying to build an unreleased SVN version of lxml without having Cython
> installed. Please read the build documentation.
>
> http://codespeak.net/lxml/build.html

So, I have done and I get the same problem that stumped me before.
I've downloaded Cython and that part seems to work.

I guess this might not be a lxml problem per se but a problem with the
build environment on my Mac.

-- Roland

Revision history for this message
scoder (scoder) said : 		#3

Roland Hedberg wrote:
> So, I have done and I get the same problem that stumped me before.
> I've downloaded Cython and that part seems to work.

Interpreting your very short problem description: you no longer get warnings
from the compiler that it has nothing to compile, but you still get the same
linker error at the end? That sounds like there's something seriously broken
in your setup.

BTW, the mailing list is a much better place for this kind of questions, as
there are usually other Mac users listening who might be able to help you.

Stefan

Can you help with this problem?

Provide an answer of your own, or ask Roland Hedberg for more information if necessary.

To post a message you must log in.