Xorg header files present but killing compiles (sw13.37)
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Xorg header files present but killing compiles (sw13.37)
Hi there,
I have a frustrating problem which repeats itself whenever I try to compile anything requiring the X11 headers. I've put some illustrative output below.
Code:
...
/usr/include/X11/Xlib.h:3589:14: error: storage class specified for parameter 'XLocaleOfOM'
/usr/include/X11/Xlib.h:3596:3: error: expected '=', ',', ';', 'asm' or '__attribute__' before '_X_SENTINEL'
/usr/include/X11/Xlib.h:3598:13: error: storage class specified for parameter 'XDestroyOC'
... etc. etc. etc. etc. etc. and etc.!
screenshot.c:187:69: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
screenshot.c:273:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
screenshot.c:288:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
/usr/include/X11/Xlib.h:3575:14: error: old-style parameter declarations in prototyped function definition
/usr/include/X11/Xlib.h:3576:5: error: parameter name omitted
screenshot.c:307:1: error: expected '{' at end of input
make[2]: *** [screenshot.o] Error 1
make[2]: Leaving directory `/usr/src/denemo-0.9.2/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/denemo-0.9.2'
make: *** [all] Error 2
The header files themselves don't *look* mangled to my naive eye. Just to be sure, I reinstalled the libX11 package from the official sw distribution and got the same errors.
This has happened with all X applications I have tried to compile in the last two weeks or so, so it is almost certainly an issue with my system.
Any ideas?
Bests,
jj
EDIT: I've reverted back to gcc and utils 4.5.2 to match the official distribution and still the same error!
Last edited by forestcreature; 01-08-2012 at 07:03 PM.
I don't know about the validity of your X related libraries, but for sure there are serious errors in your application. Here is one the line that clearly shows this:
screenshot.c:307:1: error: expected '{' at end of input
that is an explicit coding error in a C language. So I suggest to re download the stable version of this application or wait for a fix.
Thanks for the answer. That's what I thought, but as I said - this happens when I'm compiling any software requiring X, whether stable or development release. This is what bothers me...
Thanks for the help so far. The errors are a heck of a lot of lines, so when I get time I'll have to upload an archive somewhere. If you think that I should ask in a gcc specific mailinglist or something then tell me to piss off - I won't be offended
In brief though, the stable, latest version of any well-known X app (e.g. Xclock) returns these kinds of syntax errors, whilst something else I compiled (ANYTHING else which doesn't require the Xorg headers does not.
Sorry, can't spend more time on this tonight but if anyone still cares I'll try and give proper examples.
Just noticed that the software you were trying to compile has been listed and tried it myself.
It has quite a few extra deps including one that doesn't have a slackbuild available so I'm thinking that in the process of adding some extra packages you managed to break some part of the development system.
At this point I would start by making a list of anything that was added to the system and cleaning out as much as possible and going back and uninstalling everything from the 'd' series and reinstalling it all to ensure you have a clean c/c++ compiler and headers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.