#9 cgkit2 build breaks in Linux

Bug
closed
nobody
None
5
2006-08-15
2006-07-30
Richard Jones
No

On Ubuntu at least, but I assume others, the setup
fails because INC_DIRS doesn't include '/usr/include'
which means setup can't find 'boost/python.hpp'

Discussion

  • Matthias Baas
    Matthias Baas
    2006-07-31

    Logged In: YES
    user_id=211477

    If there are no other (standard) libraries affected by
    this then I hesitate to consider this as a bug.

    You can always customize things like this in your
    config.cfg file by adding the line:

    INC_DIRS += ["/usr/include"]

    In the case of Boost, I think it's better to be explicit
    with the paths used for compilation. Some parts of cgkit
    require a fairly recent version of Boost and the version
    that comes with a user's Linux distribution might already
    be too old (this is the case when I test cgkit on Linux
    (SuSE 9.2) over here where I don't add /usr/include to
    INC_DIRS).

    But I'm no expert when it comes to
    configuring/compiling/installing packages on Linux, so if
    this turns out to be a problem for other users as well and
    this is in general considered as "weird" behavior then I
    might eventually add /usr/include to the default
    paths... ;)

    - Matthias -

     
  • Matthias Baas
    Matthias Baas
    2006-07-31

    • status: open --> pending
     
  • Richard Jones
    Richard Jones
    2006-08-12

    • status: pending --> open
     
  • Richard Jones
    Richard Jones
    2006-08-12

    Logged In: YES
    user_id=6405

    I have Boost 1.33.1 installed from Ubuntu. This would
    appear to be the latest version available.

    The error I'm referring to is in the setup.py file -
    the "Check if the boost/python.hpp header can be found..."
    bit: it only checks in INC_DIRS (which contains a single
    entry "supportlib/include") for the
    file 'boost/python.hpp'. It's never going to find it
    unless INC_DIRS actually contains the standard header
    installation point of '/usr/include'.

     
  • Logged In: YES
    user_id=428581

    I just ran into this and think it should be fixed. The
    default location when searching for headers is always
    /usr/include, any other behaviour is odd and will just
    confuse people.

     
  • Matthias Baas
    Matthias Baas
    2006-08-15

    • status: open --> closed
     
  • Matthias Baas
    Matthias Baas
    2006-08-15

    Logged In: YES
    user_id=211477

    Ah, all right, I see.
    I have removed that test from the setup script now, so it
    won't abort the build anymore.

    - Matthias -