XCB error during install (Linux)



  • Hi,

    During configure I noticed that xbs_libs weren't installed so I re-ran with the -qt-xcb switch to use the xcb libs bundled with Qt.
    No problems there...

    Then during my gmake I got numerous errors that all the XCB_ATOM_* definitions were undeclared. I.E.:

    ../../../../3rdparty/xcb/xcb-util-wm/icccm.c:90:38: error: 'XCB_ATOM_WM_NAME' undeclared (first use in this function)
    ../../../../3rdparty/xcb/xcb-util-wm/icccm.c:134:38: error: 'XCB_ATOM_WM_ICON_NAME' undeclared (first use in this function)
    ../../../../3rdparty/xcb/xcb-util-wm/icccm.c:204:27: error: 'XCB_ATOM_WINDOW' undeclared (first use in this function)
    ../../../../3rdparty/xcb/xcb-util-wm/icccm.c:303:57: error: 'XCB_ATOM_STRING' undeclared (first use in this function)

    etc...

    Anything I'm missing?
    Thanks!
    -Adam


  • Lifetime Qt Champion

    HI and welcome to devnet,

    Did you just re-ran configure or did you do it from a clean state ?



  • I just re-ran configure. I know if you attempt to re-run gmake you have to clean previous attempts first. Didn't think you needed to clean anything for a failed configure?


  • Lifetime Qt Champion

    It's always better to call configure from a clean state.

    To avoid the "cleaning part" you can use out of source builds so if something goes wrong you also have the option to just erase everything and start again.



  • Ok. Clean slate = nuke the dir and start from a fresh tarball?


  • Lifetime Qt Champion

    Not necessarily, IIRC, it's make confclean but I always do out of source builds. It's way simpler especially when you build for several platforms.



  • Yeah no dice. After a clean I get the same error :(



  • Ended up installing XCB and was able to get Qt installed. Thanks for the help. ;)


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.