[Expat-bugs] [ expat-Bugs-1032878 ] Build 1.95.8 fail under AIX 4.3

SourceForge.net noreply at sourceforge.net
Fri Sep 24 11:43:22 CEST 2004


Bugs item #1032878, was opened at 2004-09-22 21:30
Message generated for change (Comment added) made by papadopo
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1032878&group_id=10127

Category: Build control
Group: Platform Specific
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Greg Stein (gstein)
Summary: Build 1.95.8 fail under AIX 4.3

Initial Comment:
> export CC=xlc
> ./configure --prefix=$HOME/xml
checking build system type... rs6000-ibm-aix4.3.2.0
checking host system type... rs6000-ibm-aix4.3.2.0
checking for gcc... xlc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... no
checking whether xlc accepts -g... yes
checking for non-GNU ld... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... no
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependant libraries... pass_all
checking command to parse /usr/bin/nm -B output... ok
checking how to run the C preprocessor... xlc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... no
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for xlc option to produce PIC... none
checking if xlc static flag -bnso -bI:/lib/syscalls.exp 
works... yes
checking if xlc supports -c -o file.o... no
checking if we can lock with hard links... yes
checking whether the linker (/usr/bin/ld) supports shared 
libraries... yes
checking how to hardcode library paths into programs... 
immediate
checking whether stripping libraries is possible... no
checking dynamic linker characteristics... aix4.3.2.0 ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
creating libtool
checking for gcc... (cached) xlc
checking whether we are using the GNU C compiler... 
(cached) no
checking whether xlc accepts -g... (cached) yes
checking for a BSD-compatible install... conftools/install-
sh -c
checking for ANSI C header files... (cached) yes
checking whether byte ordering is bigendian... yes
checking for xlc option to accept ANSI C... none needed
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking for memmove... yes
checking for bcopy... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for unistd.h... (cached) yes
checking for off_t... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... no
checking check.h usability... no
checking check.h presence... no
checking for check.h... no
checking for check.h... (cached) no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating expat_config.h
> make
        /bin/sh ./libtool --silent --mode=compile xlc -g -
DHAVE_EXPAT_CONFIG_H   -I./lib -I. -o lib/xmlparse.lo -
c lib/xmlparse.c
"lib/expat.h", line 46.27: 1506-275 (S) Unexpected 
text ',' encountered.
make: 1254-004 The error code from the last command 
is 1.


Stop.
>


/* Solution */
delete last ',' in enum XML_Status  

----------------------------------------------------------------------

Comment By: Dimitri Papadopoulos (papadopo)
Date: 2004-09-24 11:43

Message:
Logged In: YES 
user_id=52414

Yes, most C compilers on commercial Unix systems are still
implementing C89, not C99.

I think it's a good idea to avoid C99 for now, such as '//'
comments and final ',' in lists.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1032878&group_id=10127


More information about the Expat-bugs mailing list