Bug #465

ltostr() in buffer.c colides with HP-UX's gcc

Added by Anonymous 1043 days ago. Updated 460 days ago.

Status:Fixed Start:
Priority:Normal Due date:
Assigned to:- % Done:

0%

Category:core
Target version:1.4.17
Pending:

No

Resolution:

fixed


Description

i'm using HP-UX 11.11 and GCC 4.0.2 from hp-ux porting center

the function ltostr() in buffer.c colides with a function ltostr() contained in GCC's stdlib.h

it's not possible to compile lighttpd

renaming the function e.g. to LToStr() in complete source code of lighttpd solved the issue for me


find . -type f -exec perl -pi -e 's/ltostr/LToStr/g' {} \;

-- rene.petzold

Associated revisions

Revision 1951
Added by jan 460 days ago

renamed ltostr() to LI_ltostr() to fix compile on HP/UX (fixes #465)

Revision 1952
Added by jan 460 days ago

renamed ltostr() to LI_ltostr() (merged [1951] from 1.4.x, fixes #465)

History

03/11/2007 11:11 PM - Anonymous

Hi,

same happens using the HP ANSI C compiler suite. cc: "buffer.h", line 105: error 1584: Inconsistent type declaration: "ltostr".
cc: "buffer.h", line 105: error 1711: Inconsistent parameter list declaration for "ltostr".
cc: "/usr/include/sys/socket.h", line 504: warning 562: Redeclaration of "sendfile" with a different storage class specifier: "sendfile" will have internal linkage.
cc: "/usr/include/sys/socket.h", line 505: warning 562: Redeclaration of "sendpath" with a different storage class specifier: "sendpath" will have internal linkage.
  • Error code 1
cc -DHAVE_CONFIG_H -DLIBRARY_DIR=\"/usr/pkg/lib/lighttpd\" -I. -I.. -I/tmp/pkgsrc-obj/www/lighttpd/work.c3600/.buildlink/include -D_REENTRANT -D+EXTENSIONS_+ -DOPENSSL_NO_KRB5 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGE_FILES +O2 -c mod_flv_streaming.c -Wp,-M.deps/mod_flv_streaming.TPlo  +Z -DPIC -o .libs/mod_flv_streaming.o

same solution worked, too :)

regards,
florian

-- Florian Heigl

06/02/2007 10:19 PM - Anonymous

Would you please consider working on this bug?
You named your variable after one that is system declared, ok can happen, why not.
but not even looking into the issue for a year that's a bit strange, at least for
your potential users.

08/18/2007 12:29 PM - jan

  • Status changed from New to Fixed
  • Resolution set to fixed

fixed in r1951 for 1.4.x and r1952 for 1.5.0

Also available in: Atom PDF