Compilation flags are invalid on OS X

Bug #1371954 reported by Charlie_X
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released

Bug Description

As long as libxml2 and libxslt are around (installed by MacPorts or Homebrew) then lxml installs fine on MacOS X.

However, building from source is another matter. There seems to be a problem disabling the optimisation flags leading to errors like: 'error: invalid integral value '0 -g' error: command '/usr/bin/clang' failed with exit status 1`

Commenting out the line that sets these flags "solves" the problem. I assume this is due to a slight difference between clang and gcc.

This was tested with lxml 3.4.0 on OS X 10.10 (Mavericks) with Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)

Revision history for this message
scoder (scoder) wrote :

what line is that? and does it help to reverse the flags into "-g -O0" instead of "-O0 -g" (which I assume you're using)?

Revision history for this message
Charlie_X (charlie) wrote :

It's from the standard tox configuration. Changing it as you suggest does resolve the problem. Do we need to add a check for clang?

Revision history for this message
scoder (scoder) wrote :

No, if the order is a problem, I can just change it:

Changed in lxml:
assignee: nobody → scoder (scoder)
importance: Undecided → Low
status: New → Fix Committed
Revision history for this message
scoder (scoder) wrote :

Fixed in lxml 3.4.1.

Changed in lxml:
milestone: none → 3.4
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers