You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2004/04/02 18:17:46 UTC
DO NOT REPLY [Bug 28155] -
Error "pthread.h: present but cannot be compiled" during Configuration
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28155>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28155
Error "pthread.h: present but cannot be compiled" during Configuration
trawick@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From trawick@apache.org 2004-04-02 16:17 -------
If your compiler cannot successfully compile /usr/include/pthread.h, that is not
an Apache problem ;) Check with IBM support to see if there are compiler
compatibility fixes to pthread.h. This could also be an issue with the
fixincludes step of gcc build/install, where on AIX and Solaris and perhaps
other platforms, certain levels of gcc will construct modified versions of
certain system header files to be used for gcc compiles.
Alternately, you could look at the line 554 in the file mentioned below
/usr/include/pthread.h:554: error: parse error before '*' token
and see if you can identify what is causing gcc not to compile it properly.
I seem to recall an issue in an old level of AIX 4.3 where there was a backslash
for preprocessor continuation in a system header file, with no space before the
backslash. gcc puked but the IBM compiler didn't complain.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org