Bug 178691 - Wrong apr_off_t type makes mod_mono build fail on 32bit archs
Wrong apr_off_t type makes mod_mono build fail on 32bit archs
Product: Fedora
Classification: Fedora
Component: apr (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Joe Orton
Depends On:
  Show dependency treegraph
Reported: 2006-01-23 10:44 EST by Matthias Saou
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-01-30 08:38:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matthias Saou 2006-01-23 10:44:42 EST
I've recompiled successfully mod_mono on FC development x86_64, but the very
same source package fails on i386 with :

configure:21429: gcc -c -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=pentium4
-fasynchronous-unwind-tables  -I/usr/include/apr-1  -I/usr/include/httpd 
conftest.c >&5
In file included from /usr/include/httpd/ap_config.h:25,
                 from /usr/include/httpd/httpd.h:43,
                 from conftest.c:51:
/usr/include/apr-1/apr.h:270: error: expected '=', ',', ';', 'asm' or
'__attribute__' before 'apr_off_t'

Which makes it fallback to apache 1.3 when trying to detect the apache
version (which is 2.0 obviously).

That line reads "typedef  off64_t           apr_off_t;" which apparently
32bit gcc doesn't like. Changing the type made the detection work, and the
build to succeed, but I'm not 100% sure the type I've set is correct.
Comment 1 Joe Orton 2006-01-30 08:38:50 EST
mod_mono needs to use `apr-1-config --cppflags` etc in CPPFLAGS etc, or use
apxs, otherwise it won't pick up necessary flags like -D_LARGEFILE64_SOURCE.
Comment 2 Matthias Saou 2006-01-30 09:35:03 EST
Indeed, that was the problem, as compilation works after changing that in
configure. Thanks a lot!

Note You need to log in before you can comment on or make changes to this bug.