From noreply at sourceforge.net Mon Dec 4 22:13:37 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 04 Dec 2006 13:13:37 -0800 Subject: [Expat-bugs] [ expat-Bugs-1490371 ] additional config for INSTALL_ROOT Message-ID: Bugs item #1490371, was opened at 2006-05-17 11:36 Message generated for change (Comment added) made by todd_rinaldo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1490371&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: www.libexpat.org Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: additional config for INSTALL_ROOT Initial Comment: When I install expat 2.0.0, it shows me the following error always. but expat 1.9.5 is fine. camelot# make install make: Fatal error in reader: Makefile, line 48: Unexpected end of line seen the line 48 is as following: 47:ifndef INSTALL_ROOT 48:INSTALL_ROOT=$(DESTDIR) 49:if ---------------------------------------------------------------------- Comment By: Todd Rinaldo (todd_rinaldo) Date: 2006-12-04 15:13 Message: Logged In: YES user_id=1660778 Originator: NO I too am having this problem... downloaded the gz, not the CVS ./configure --prefix=/apps/customdir/perl588_32/site ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-26 12:07 Message: Logged In: YES user_id=290026 Originator: NO What happens if you check out from CVS and then run make-release.sh to build your own tarball? Does that work? If no response I'll close this issue. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-10-04 11:54 Message: Logged In: NO Same problem with the .gz file expat-2.0.0 Solaris 5.10 root cosmo #./configure checking build system type... sparc-sun-solaris2.10 checking host system type... sparc-sun-solaris2.10 checking for gcc... gcc checking for C compiler default output file name... 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... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... egrep checking for ld used by gcc... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking for /usr/ccs/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/ccs/bin/nm -p checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -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... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking how to run the C++ preprocessor... g++ -E checking for g77... no checking for f77... f77 checking whether we are using the GNU Fortran 77 compiler... no checking whether f77 accepts -g... yes checking the maximum length of command line arguments... 262144 checking command to parse /usr/ccs/bin/nm -p output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/ccs/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... yes checking dynamic linker characteristics... solaris2.10 ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... no checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ static flag -static works... no checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.10 ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for f77 option to produce PIC... -fPIC checking if f77 PIC flag -fPIC works... no checking if f77 static flag -static works... no checking if f77 supports -c -o file.o... yes checking whether the f77 linker (/usr/ccs/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... f90: Warning: Option -print-search-dirs passed to ld, if ld is invoked, ignored otherwise Usage: f90 [ options ] files. Use 'f90 -flags' for details solaris2.10 ld.so checking how to hardcode library paths into programs... immediate checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ANSI C... (cached) none needed checking for a BSD-compatible install... conftools/install-sh -c checking whether gcc accepts -fexceptions... yes checking for ANSI C header files... (cached) yes checking whether byte ordering is bigendian... yes 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... yes checking for an ANSI C99-conforming __func__... yes configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h config.status: expat_config.h is unchanged root cosmo #make make: Fatal error in reader: Makefile, line 48: Unexpected end of line seen ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-07-27 14:32 Message: Logged In: NO Sorry, it's Solaris 9 :-). But you get the idea - same error as other people. I also tried './configure --prefix =/usr/local', no difference. Changed ifndef INSTALL_ROOT INSTALL_ROOT=$(DESTDIR) endif to INSTALL_ROOT=$(prefix) and it put eveything in /usr/local/usr/local. Perhaps a Solaris/GNU make syntax problem. Tried GNU make, no luck. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-07-27 13:46 Message: Logged In: NO I'm getting the same error, expat-2.0.0.tar.gz, Solaris 8 on Sparc, using Sun Forte 7 cc. zeus:/tmp/expat-2.0.0# which make /usr/ccs/bin/make zeus:/tmp/expat-2.0.0# which cc /opt/forte7/SUNWspro/bin/cc zeus:/tmp/expat-2.0.0# ./configure checking build system type... sparc-sun-solaris2.9 checking host system type... sparc-sun-solaris2.9 checking for gcc... no checking for cc... cc checking for C compiler default output file name... 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 cc accepts -g... yes checking for cc option to accept ANSI C... none needed checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... egrep checking for non-GNU ld... /usr/ucb/ld checking if the linker (/usr/ucb/ld) is GNU ld... no checking for /usr/ucb/ld option to reload object files... - r checking for BSD-compatible nm... /usr/ccs/bin/nm -p checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... cc -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 g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... CC checking whether we are using the GNU C++ compiler... no checking whether CC accepts -g... yes checking how to run the C++ preprocessor... CC -E checking for g77... no checking for f77... f77 checking whether we are using the GNU Fortran 77 compiler... no checking whether f77 accepts -g... yes checking the maximum length of command line arguments... 262144 checking command to parse /usr/ccs/bin/nm -p output from cc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking for cc option to produce PIC... -KPIC checking if cc PIC flag -KPIC works... yes checking if cc static flag -Bstatic works... yes checking if cc supports -c -o file.o... yes checking whether the cc linker (/usr/ucb/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.9 ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... no checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking whether the CC linker (/usr/ucb/ld) supports shared libraries... yes checking for CC option to produce PIC... -KPIC checking if CC PIC flag -KPIC works... yes checking if CC static flag -Bstatic works... yes checking if CC supports -c -o file.o... yes checking whether the CC linker (/usr/ucb/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.9 ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for f77 option to produce PIC... -KPIC checking if f77 PIC flag -KPIC works... yes checking if f77 static flag -Bstatic works... yes checking if f77 supports -c -o file.o... yes checking whether the f77 linker (/usr/ucb/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.9 ld.so checking how to hardcode library paths into programs... immediate checking for gcc... (cached) cc checking whether we are using the GNU C compiler... (cached) no checking whether cc accepts -g... (cached) yes checking for cc option to accept ANSI C... (cached) none needed 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 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... yes checking for an ANSI C99-conforming __func__... yes configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h zeus:/tmp/expat-2.0.0# make make: Fatal error in reader: Makefile, line 48: Unexpected end of line seen INSTALL_ROOT=$(DESTDIR) ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-06-01 16:01 Message: Logged In: YES user_id=290026 Could you please try a checkout from CVS. If you still have a problem, then maybe "make" on your system is too old, or otherwise different. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-06-01 15:33 Message: Logged In: NO I'm having the same problem building in a Solaris 10 on Sparc environment. I'm using 2.0.0 from a .gz tarball. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-05-17 12:19 Message: Logged In: YES user_id=290026 In which environment do you try to build expat? Is this a checkout from CVD or did you download the .gz archive? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1490371&group_id=10127 From noreply at sourceforge.net Mon Dec 11 20:50:47 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 11 Dec 2006 11:50:47 -0800 Subject: [Expat-bugs] [ expat-Bugs-1613457 ] Makefile.in problem on NETBSD 3.1 Message-ID: Bugs item #1613457, was opened at 2006-12-11 11:50 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1613457&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build control Group: Platform Specific Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: Makefile.in problem on NETBSD 3.1 Initial Comment: After running the configure script, then trying to run make, it errors out: squallbsr at karasu2 [~/source/expat-2.0.0]$ make make: "/Users/squallbsr/source/expat-2.0.0/Makefile" line 47: Need an operator make: "/Users/squallbsr/source/expat-2.0.0/Makefile" line 49: Need an operator make: Fatal errors encountered -- cannot continue This can be fixed by adjusting the ifndef INSTALL_ROOT section around lines 47-49 in Makefile.in I changed it to: INSTALL_ROOT ?= $(DESTDIR) which worked on NetBSD and for my application, this of course would need more testing as all I wanted was for expat to complile, not install. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1613457&group_id=10127 From noreply at sourceforge.net Mon Dec 11 20:54:03 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 11 Dec 2006 11:54:03 -0800 Subject: [Expat-bugs] [ expat-Bugs-1613457 ] Makefile.in problem on NETBSD 3.1 Message-ID: Bugs item #1613457, was opened at 2006-12-11 13:50 Message generated for change (Comment added) made by squallbsr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1613457&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build control Group: Platform Specific Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: Makefile.in problem on NETBSD 3.1 Initial Comment: After running the configure script, then trying to run make, it errors out: squallbsr at karasu2 [~/source/expat-2.0.0]$ make make: "/Users/squallbsr/source/expat-2.0.0/Makefile" line 47: Need an operator make: "/Users/squallbsr/source/expat-2.0.0/Makefile" line 49: Need an operator make: Fatal errors encountered -- cannot continue This can be fixed by adjusting the ifndef INSTALL_ROOT section around lines 47-49 in Makefile.in I changed it to: INSTALL_ROOT ?= $(DESTDIR) which worked on NetBSD and for my application, this of course would need more testing as all I wanted was for expat to complile, not install. ---------------------------------------------------------------------- Comment By: Bryan Rehbein (squallbsr) Date: 2006-12-11 13:54 Message: Logged In: YES user_id=950269 Originator: NO Bug reported by: br39290 at squall.us ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1613457&group_id=10127 From noreply at sourceforge.net Tue Dec 12 12:57:39 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 12 Dec 2006 03:57:39 -0800 Subject: [Expat-bugs] [ expat-Bugs-1613898 ] Make: Must be a separator on rules line 48. Stop. Message-ID: Bugs item #1613898, was opened at 2006-12-12 03:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1613898&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Make: Must be a separator on rules line 48. Stop. Initial Comment: Make: Must be a separator on rules line 48. Stop. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1613898&group_id=10127 From noreply at sourceforge.net Tue Dec 12 15:15:24 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 12 Dec 2006 06:15:24 -0800 Subject: [Expat-bugs] [ expat-Bugs-1613898 ] Make: Must be a separator on rules line 48. Stop. Message-ID: Bugs item #1613898, was opened at 2006-12-12 06:57 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1613898&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Duplicate Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Make: Must be a separator on rules line 48. Stop. Initial Comment: Make: Must be a separator on rules line 48. Stop. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-12-12 09:15 Message: Logged In: YES user_id=290026 Originator: NO Duplicate of issue # 1490371. You might want to state what OS / Make version you are running. It seems some legacy Make implementations cannot handle our make file. Closing this issue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1613898&group_id=10127 From noreply at sourceforge.net Tue Dec 12 20:17:22 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 12 Dec 2006 11:17:22 -0800 Subject: [Expat-bugs] [ expat-Patches-1437840 ] Compile fix rollup patch against 2.0.0 Message-ID: Patches item #1437840, was opened at 2006-02-23 21:58 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=1437840&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Open >Resolution: None Priority: 5 Private: No Submitted By: Mark F. Haigh (mfhaigh) Assigned to: Greg Stein (gstein) Summary: Compile fix rollup patch against 2.0.0 Initial Comment: The attached rollup patch fixes the following bugs: #1414066 - make failes on hpux #1033965 - Building application fails with Intel C compiler (1.95.7) #N/A - Build fails on Tru64 UNIX. The patch was tested on x86-64 Linux, i386 NetBSD, HP-UX 11i, and Tru64 5.1b. All tests passed on each machine. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-12-12 14:17 Message: Logged In: YES user_id=290026 Originator: NO I am preparing for a new release, and I came across this part of your patch: -ifndef INSTALL_ROOT INSTALL_ROOT=$(DESTDIR) -endif Why did you remove this logic? It was added due to bug # 985235 and patch # 779334. I am inclined to add it back, though some platforms have trouble with it. (see bug # 1490371). Maybe there is a way to improve it? Re-opening this issue. Karl ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-03-06 09:25 Message: Logged In: YES user_id=290026 Patch applied March 6, 2006. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-02-27 17:02 Message: Logged In: NO You could get really anal and note that the conversion from a pointer type to an integer type is implementation-defined by the C standard in the first place. But we all know it "just works" nearly everywhere. The code here is broken anyways. And since the value is never really _used_, it doesn't matter. But changing the cast to long prevents a warning on all architectures I know of except for Windows-64, which uses a 32 bit long and 64 bit pointers (LLP64 model). Using the newer C99 types is preferable, of course, and the best thing to do is to provide an autoconf-assisted stdint.h that can be used if the system doesn't have stdint.h. Note that uintptr_t and friends are optional types under C99 anyways! But, like I said, all this does is paper-over a (well-deserved) warning, nothing more. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-02-27 09:42 Message: Logged In: YES user_id=290026 Actually, it should be uintptr_t or intptr_t, but the question is, how many compilers recognize these types (were they not introduced with C99?). ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-02-27 09:26 Message: Logged In: YES user_id=290026 One question about the patch to runtests.c: - int callno = 1 + (int)XML_GetUserData(parser); + long callno = 1 + (long)XML_GetUserData(parser); Why changing from int to long? If we really want to be anal, why not change to ptrdiff_t, as callno hast to fit into a pointer? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-02-24 10:16 Message: Logged In: YES user_id=290026 Thanks. Seems to work on Cygwin as well. Will check it in if Greg has no objections. ---------------------------------------------------------------------- Comment By: Mark F. Haigh (mfhaigh) Date: 2006-02-23 23:10 Message: Logged In: YES user_id=1458985 The patch was against the 2.0.0 release. I'm attaching the same patch against CVS as of Feb 23, 2006, 8:00 PST. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-02-23 22:10 Message: Logged In: YES user_id=290026 Is this patch against CVS? It fails for me on Makefile.in: $ patch -i compile-rollup.patch -p 1 patching file lib/expat_external.h patching file Makefile.in Hunk #3 succeeded at 157 (offset 1 line). Hunk #4 FAILED at 172. 1 out of 4 hunks FAILED -- saving rejects to file Makefile.in.rej patching file tests/minicheck.h patching file tests/runtests.c ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=1437840&group_id=10127 From noreply at sourceforge.net Tue Dec 12 20:32:12 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 12 Dec 2006 11:32:12 -0800 Subject: [Expat-bugs] [ expat-Bugs-1613457 ] Makefile.in problem on NETBSD 3.1 Message-ID: Bugs item #1613457, was opened at 2006-12-11 14:50 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1613457&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build control Group: Platform Specific Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: Makefile.in problem on NETBSD 3.1 Initial Comment: After running the configure script, then trying to run make, it errors out: squallbsr at karasu2 [~/source/expat-2.0.0]$ make make: "/Users/squallbsr/source/expat-2.0.0/Makefile" line 47: Need an operator make: "/Users/squallbsr/source/expat-2.0.0/Makefile" line 49: Need an operator make: Fatal errors encountered -- cannot continue This can be fixed by adjusting the ifndef INSTALL_ROOT section around lines 47-49 in Makefile.in I changed it to: INSTALL_ROOT ?= $(DESTDIR) which worked on NetBSD and for my application, this of course would need more testing as all I wanted was for expat to complile, not install. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-12-12 14:32 Message: Logged In: YES user_id=290026 Originator: NO Apparently - after doing a Goole search - Solaris as well as BSD Make have issues with the "ifndef" syntax. Is there a way to keep the logic with another syntax? It looks as if "?=" does not have exactly the same logic. ---------------------------------------------------------------------- Comment By: Bryan Rehbein (squallbsr) Date: 2006-12-11 14:54 Message: Logged In: YES user_id=950269 Originator: NO Bug reported by: br39290 at squall.us ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1613457&group_id=10127 From noreply at sourceforge.net Wed Dec 13 18:27:15 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 13 Dec 2006 09:27:15 -0800 Subject: [Expat-bugs] [ expat-Bugs-1613457 ] Makefile.in problem on NETBSD 3.1 Message-ID: Bugs item #1613457, was opened at 2006-12-11 14:50 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1613457&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build control Group: Platform Specific Status: Open >Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: Makefile.in problem on NETBSD 3.1 Initial Comment: After running the configure script, then trying to run make, it errors out: squallbsr at karasu2 [~/source/expat-2.0.0]$ make make: "/Users/squallbsr/source/expat-2.0.0/Makefile" line 47: Need an operator make: "/Users/squallbsr/source/expat-2.0.0/Makefile" line 49: Need an operator make: Fatal errors encountered -- cannot continue This can be fixed by adjusting the ifndef INSTALL_ROOT section around lines 47-49 in Makefile.in I changed it to: INSTALL_ROOT ?= $(DESTDIR) which worked on NetBSD and for my application, this of course would need more testing as all I wanted was for expat to complile, not install. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-12-13 12:27 Message: Logged In: YES user_id=290026 Originator: NO Well, I thought about it, and "?=" seems acceptable. It only assigns if the symbol is undefined, whereas "ifndef" assigns when the symbol is the empty string or undefined. I'll change that accordingly. Committed in Makefile.in rev. 1.56. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-12-12 14:32 Message: Logged In: YES user_id=290026 Originator: NO Apparently - after doing a Goole search - Solaris as well as BSD Make have issues with the "ifndef" syntax. Is there a way to keep the logic with another syntax? It looks as if "?=" does not have exactly the same logic. ---------------------------------------------------------------------- Comment By: Bryan Rehbein (squallbsr) Date: 2006-12-11 14:54 Message: Logged In: YES user_id=950269 Originator: NO Bug reported by: br39290 at squall.us ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1613457&group_id=10127 From noreply at sourceforge.net Wed Dec 13 18:29:24 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 13 Dec 2006 09:29:24 -0800 Subject: [Expat-bugs] [ expat-Bugs-1490371 ] additional config for INSTALL_ROOT Message-ID: Bugs item #1490371, was opened at 2006-05-17 12:36 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1490371&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: www.libexpat.org >Group: Test Required Status: Open >Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: additional config for INSTALL_ROOT Initial Comment: When I install expat 2.0.0, it shows me the following error always. but expat 1.9.5 is fine. camelot# make install make: Fatal error in reader: Makefile, line 48: Unexpected end of line seen the line 48 is as following: 47:ifndef INSTALL_ROOT 48:INSTALL_ROOT=$(DESTDIR) 49:if ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-12-13 12:29 Message: Logged In: YES user_id=290026 Originator: NO It seems the ifndef syntax is only supported by GNU Make. I think that using "?=" instead is acceptable, although it is not the same. It only assigns if the symbol is undefined, whereas "ifndef" assigns when the symbol is the empty string or undefined. Made the change accordingly. Committed in Makefile.in rev. 1.56. ---------------------------------------------------------------------- Comment By: Todd Rinaldo (todd_rinaldo) Date: 2006-12-04 16:13 Message: Logged In: YES user_id=1660778 Originator: NO I too am having this problem... downloaded the gz, not the CVS ./configure --prefix=/apps/customdir/perl588_32/site ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-26 13:07 Message: Logged In: YES user_id=290026 Originator: NO What happens if you check out from CVS and then run make-release.sh to build your own tarball? Does that work? If no response I'll close this issue. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-10-04 12:54 Message: Logged In: NO Same problem with the .gz file expat-2.0.0 Solaris 5.10 root cosmo #./configure checking build system type... sparc-sun-solaris2.10 checking host system type... sparc-sun-solaris2.10 checking for gcc... gcc checking for C compiler default output file name... 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... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... egrep checking for ld used by gcc... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking for /usr/ccs/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/ccs/bin/nm -p checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -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... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking how to run the C++ preprocessor... g++ -E checking for g77... no checking for f77... f77 checking whether we are using the GNU Fortran 77 compiler... no checking whether f77 accepts -g... yes checking the maximum length of command line arguments... 262144 checking command to parse /usr/ccs/bin/nm -p output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/ccs/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... yes checking dynamic linker characteristics... solaris2.10 ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... no checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ static flag -static works... no checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.10 ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for f77 option to produce PIC... -fPIC checking if f77 PIC flag -fPIC works... no checking if f77 static flag -static works... no checking if f77 supports -c -o file.o... yes checking whether the f77 linker (/usr/ccs/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... f90: Warning: Option -print-search-dirs passed to ld, if ld is invoked, ignored otherwise Usage: f90 [ options ] files. Use 'f90 -flags' for details solaris2.10 ld.so checking how to hardcode library paths into programs... immediate checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ANSI C... (cached) none needed checking for a BSD-compatible install... conftools/install-sh -c checking whether gcc accepts -fexceptions... yes checking for ANSI C header files... (cached) yes checking whether byte ordering is bigendian... yes 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... yes checking for an ANSI C99-conforming __func__... yes configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h config.status: expat_config.h is unchanged root cosmo #make make: Fatal error in reader: Makefile, line 48: Unexpected end of line seen ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-07-27 15:32 Message: Logged In: NO Sorry, it's Solaris 9 :-). But you get the idea - same error as other people. I also tried './configure --prefix =/usr/local', no difference. Changed ifndef INSTALL_ROOT INSTALL_ROOT=$(DESTDIR) endif to INSTALL_ROOT=$(prefix) and it put eveything in /usr/local/usr/local. Perhaps a Solaris/GNU make syntax problem. Tried GNU make, no luck. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-07-27 14:46 Message: Logged In: NO I'm getting the same error, expat-2.0.0.tar.gz, Solaris 8 on Sparc, using Sun Forte 7 cc. zeus:/tmp/expat-2.0.0# which make /usr/ccs/bin/make zeus:/tmp/expat-2.0.0# which cc /opt/forte7/SUNWspro/bin/cc zeus:/tmp/expat-2.0.0# ./configure checking build system type... sparc-sun-solaris2.9 checking host system type... sparc-sun-solaris2.9 checking for gcc... no checking for cc... cc checking for C compiler default output file name... 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 cc accepts -g... yes checking for cc option to accept ANSI C... none needed checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... egrep checking for non-GNU ld... /usr/ucb/ld checking if the linker (/usr/ucb/ld) is GNU ld... no checking for /usr/ucb/ld option to reload object files... - r checking for BSD-compatible nm... /usr/ccs/bin/nm -p checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... cc -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 g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... CC checking whether we are using the GNU C++ compiler... no checking whether CC accepts -g... yes checking how to run the C++ preprocessor... CC -E checking for g77... no checking for f77... f77 checking whether we are using the GNU Fortran 77 compiler... no checking whether f77 accepts -g... yes checking the maximum length of command line arguments... 262144 checking command to parse /usr/ccs/bin/nm -p output from cc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking for cc option to produce PIC... -KPIC checking if cc PIC flag -KPIC works... yes checking if cc static flag -Bstatic works... yes checking if cc supports -c -o file.o... yes checking whether the cc linker (/usr/ucb/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.9 ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... no checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking whether the CC linker (/usr/ucb/ld) supports shared libraries... yes checking for CC option to produce PIC... -KPIC checking if CC PIC flag -KPIC works... yes checking if CC static flag -Bstatic works... yes checking if CC supports -c -o file.o... yes checking whether the CC linker (/usr/ucb/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.9 ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for f77 option to produce PIC... -KPIC checking if f77 PIC flag -KPIC works... yes checking if f77 static flag -Bstatic works... yes checking if f77 supports -c -o file.o... yes checking whether the f77 linker (/usr/ucb/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.9 ld.so checking how to hardcode library paths into programs... immediate checking for gcc... (cached) cc checking whether we are using the GNU C compiler... (cached) no checking whether cc accepts -g... (cached) yes checking for cc option to accept ANSI C... (cached) none needed 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 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... yes checking for an ANSI C99-conforming __func__... yes configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h zeus:/tmp/expat-2.0.0# make make: Fatal error in reader: Makefile, line 48: Unexpected end of line seen INSTALL_ROOT=$(DESTDIR) ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-06-01 17:01 Message: Logged In: YES user_id=290026 Could you please try a checkout from CVS. If you still have a problem, then maybe "make" on your system is too old, or otherwise different. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-06-01 16:33 Message: Logged In: NO I'm having the same problem building in a Solaris 10 on Sparc environment. I'm using 2.0.0 from a .gz tarball. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-05-17 13:19 Message: Logged In: YES user_id=290026 In which environment do you try to build expat? Is this a checkout from CVD or did you download the .gz archive? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1490371&group_id=10127 From noreply at sourceforge.net Wed Dec 13 18:31:41 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 13 Dec 2006 09:31:41 -0800 Subject: [Expat-bugs] [ expat-Patches-1437840 ] Compile fix rollup patch against 2.0.0 Message-ID: Patches item #1437840, was opened at 2006-02-23 21:58 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=1437840&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Mark F. Haigh (mfhaigh) Assigned to: Greg Stein (gstein) Summary: Compile fix rollup patch against 2.0.0 Initial Comment: The attached rollup patch fixes the following bugs: #1414066 - make failes on hpux #1033965 - Building application fails with Intel C compiler (1.95.7) #N/A - Build fails on Tru64 UNIX. The patch was tested on x86-64 Linux, i386 NetBSD, HP-UX 11i, and Tru64 5.1b. All tests passed on each machine. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-12-13 12:31 Message: Logged In: YES user_id=290026 Originator: NO I re-introduced the ifndef logic, but using "?=" instead. See bug # 1613457. Committed as Makefile.in rev. 1.56. Closing this issue. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-12-12 14:17 Message: Logged In: YES user_id=290026 Originator: NO I am preparing for a new release, and I came across this part of your patch: -ifndef INSTALL_ROOT INSTALL_ROOT=$(DESTDIR) -endif Why did you remove this logic? It was added due to bug # 985235 and patch # 779334. I am inclined to add it back, though some platforms have trouble with it. (see bug # 1490371). Maybe there is a way to improve it? Re-opening this issue. Karl ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-03-06 09:25 Message: Logged In: YES user_id=290026 Patch applied March 6, 2006. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-02-27 17:02 Message: Logged In: NO You could get really anal and note that the conversion from a pointer type to an integer type is implementation-defined by the C standard in the first place. But we all know it "just works" nearly everywhere. The code here is broken anyways. And since the value is never really _used_, it doesn't matter. But changing the cast to long prevents a warning on all architectures I know of except for Windows-64, which uses a 32 bit long and 64 bit pointers (LLP64 model). Using the newer C99 types is preferable, of course, and the best thing to do is to provide an autoconf-assisted stdint.h that can be used if the system doesn't have stdint.h. Note that uintptr_t and friends are optional types under C99 anyways! But, like I said, all this does is paper-over a (well-deserved) warning, nothing more. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-02-27 09:42 Message: Logged In: YES user_id=290026 Actually, it should be uintptr_t or intptr_t, but the question is, how many compilers recognize these types (were they not introduced with C99?). ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-02-27 09:26 Message: Logged In: YES user_id=290026 One question about the patch to runtests.c: - int callno = 1 + (int)XML_GetUserData(parser); + long callno = 1 + (long)XML_GetUserData(parser); Why changing from int to long? If we really want to be anal, why not change to ptrdiff_t, as callno hast to fit into a pointer? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-02-24 10:16 Message: Logged In: YES user_id=290026 Thanks. Seems to work on Cygwin as well. Will check it in if Greg has no objections. ---------------------------------------------------------------------- Comment By: Mark F. Haigh (mfhaigh) Date: 2006-02-23 23:10 Message: Logged In: YES user_id=1458985 The patch was against the 2.0.0 release. I'm attaching the same patch against CVS as of Feb 23, 2006, 8:00 PST. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-02-23 22:10 Message: Logged In: YES user_id=290026 Is this patch against CVS? It fails for me on Makefile.in: $ patch -i compile-rollup.patch -p 1 patching file lib/expat_external.h patching file Makefile.in Hunk #3 succeeded at 157 (offset 1 line). Hunk #4 FAILED at 172. 1 out of 4 hunks FAILED -- saving rejects to file Makefile.in.rej patching file tests/minicheck.h patching file tests/runtests.c ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=1437840&group_id=10127 From noreply at sourceforge.net Thu Dec 14 01:17:32 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 13 Dec 2006 16:17:32 -0800 Subject: [Expat-bugs] [ expat-Bugs-1490371 ] additional config for INSTALL_ROOT Message-ID: Bugs item #1490371, was opened at 2006-05-17 11:36 Message generated for change (Comment added) made by todd_rinaldo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1490371&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: www.libexpat.org Group: Test Required Status: Open Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: additional config for INSTALL_ROOT Initial Comment: When I install expat 2.0.0, it shows me the following error always. but expat 1.9.5 is fine. camelot# make install make: Fatal error in reader: Makefile, line 48: Unexpected end of line seen the line 48 is as following: 47:ifndef INSTALL_ROOT 48:INSTALL_ROOT=$(DESTDIR) 49:if ---------------------------------------------------------------------- Comment By: Todd Rinaldo (todd_rinaldo) Date: 2006-12-13 18:17 Message: Logged In: YES user_id=1660778 Originator: NO Yep removing the 3 lines seems to correct the problem on Solaris CC ifndef INSTALL_ROOT INSTALL_ROOT=$(DESTDIR) endif ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-12-13 11:29 Message: Logged In: YES user_id=290026 Originator: NO It seems the ifndef syntax is only supported by GNU Make. I think that using "?=" instead is acceptable, although it is not the same. It only assigns if the symbol is undefined, whereas "ifndef" assigns when the symbol is the empty string or undefined. Made the change accordingly. Committed in Makefile.in rev. 1.56. ---------------------------------------------------------------------- Comment By: Todd Rinaldo (todd_rinaldo) Date: 2006-12-04 15:13 Message: Logged In: YES user_id=1660778 Originator: NO I too am having this problem... downloaded the gz, not the CVS ./configure --prefix=/apps/customdir/perl588_32/site ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-26 12:07 Message: Logged In: YES user_id=290026 Originator: NO What happens if you check out from CVS and then run make-release.sh to build your own tarball? Does that work? If no response I'll close this issue. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-10-04 11:54 Message: Logged In: NO Same problem with the .gz file expat-2.0.0 Solaris 5.10 root cosmo #./configure checking build system type... sparc-sun-solaris2.10 checking host system type... sparc-sun-solaris2.10 checking for gcc... gcc checking for C compiler default output file name... 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... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... egrep checking for ld used by gcc... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking for /usr/ccs/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/ccs/bin/nm -p checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -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... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking how to run the C++ preprocessor... g++ -E checking for g77... no checking for f77... f77 checking whether we are using the GNU Fortran 77 compiler... no checking whether f77 accepts -g... yes checking the maximum length of command line arguments... 262144 checking command to parse /usr/ccs/bin/nm -p output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/ccs/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... yes checking dynamic linker characteristics... solaris2.10 ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... no checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ static flag -static works... no checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.10 ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for f77 option to produce PIC... -fPIC checking if f77 PIC flag -fPIC works... no checking if f77 static flag -static works... no checking if f77 supports -c -o file.o... yes checking whether the f77 linker (/usr/ccs/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... f90: Warning: Option -print-search-dirs passed to ld, if ld is invoked, ignored otherwise Usage: f90 [ options ] files. Use 'f90 -flags' for details solaris2.10 ld.so checking how to hardcode library paths into programs... immediate checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ANSI C... (cached) none needed checking for a BSD-compatible install... conftools/install-sh -c checking whether gcc accepts -fexceptions... yes checking for ANSI C header files... (cached) yes checking whether byte ordering is bigendian... yes 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... yes checking for an ANSI C99-conforming __func__... yes configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h config.status: expat_config.h is unchanged root cosmo #make make: Fatal error in reader: Makefile, line 48: Unexpected end of line seen ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-07-27 14:32 Message: Logged In: NO Sorry, it's Solaris 9 :-). But you get the idea - same error as other people. I also tried './configure --prefix =/usr/local', no difference. Changed ifndef INSTALL_ROOT INSTALL_ROOT=$(DESTDIR) endif to INSTALL_ROOT=$(prefix) and it put eveything in /usr/local/usr/local. Perhaps a Solaris/GNU make syntax problem. Tried GNU make, no luck. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-07-27 13:46 Message: Logged In: NO I'm getting the same error, expat-2.0.0.tar.gz, Solaris 8 on Sparc, using Sun Forte 7 cc. zeus:/tmp/expat-2.0.0# which make /usr/ccs/bin/make zeus:/tmp/expat-2.0.0# which cc /opt/forte7/SUNWspro/bin/cc zeus:/tmp/expat-2.0.0# ./configure checking build system type... sparc-sun-solaris2.9 checking host system type... sparc-sun-solaris2.9 checking for gcc... no checking for cc... cc checking for C compiler default output file name... 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 cc accepts -g... yes checking for cc option to accept ANSI C... none needed checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... egrep checking for non-GNU ld... /usr/ucb/ld checking if the linker (/usr/ucb/ld) is GNU ld... no checking for /usr/ucb/ld option to reload object files... - r checking for BSD-compatible nm... /usr/ccs/bin/nm -p checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... cc -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 g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... CC checking whether we are using the GNU C++ compiler... no checking whether CC accepts -g... yes checking how to run the C++ preprocessor... CC -E checking for g77... no checking for f77... f77 checking whether we are using the GNU Fortran 77 compiler... no checking whether f77 accepts -g... yes checking the maximum length of command line arguments... 262144 checking command to parse /usr/ccs/bin/nm -p output from cc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking for cc option to produce PIC... -KPIC checking if cc PIC flag -KPIC works... yes checking if cc static flag -Bstatic works... yes checking if cc supports -c -o file.o... yes checking whether the cc linker (/usr/ucb/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.9 ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... no checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking whether the CC linker (/usr/ucb/ld) supports shared libraries... yes checking for CC option to produce PIC... -KPIC checking if CC PIC flag -KPIC works... yes checking if CC static flag -Bstatic works... yes checking if CC supports -c -o file.o... yes checking whether the CC linker (/usr/ucb/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.9 ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for f77 option to produce PIC... -KPIC checking if f77 PIC flag -KPIC works... yes checking if f77 static flag -Bstatic works... yes checking if f77 supports -c -o file.o... yes checking whether the f77 linker (/usr/ucb/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.9 ld.so checking how to hardcode library paths into programs... immediate checking for gcc... (cached) cc checking whether we are using the GNU C compiler... (cached) no checking whether cc accepts -g... (cached) yes checking for cc option to accept ANSI C... (cached) none needed 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 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... yes checking for an ANSI C99-conforming __func__... yes configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h zeus:/tmp/expat-2.0.0# make make: Fatal error in reader: Makefile, line 48: Unexpected end of line seen INSTALL_ROOT=$(DESTDIR) ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-06-01 16:01 Message: Logged In: YES user_id=290026 Could you please try a checkout from CVS. If you still have a problem, then maybe "make" on your system is too old, or otherwise different. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-06-01 15:33 Message: Logged In: NO I'm having the same problem building in a Solaris 10 on Sparc environment. I'm using 2.0.0 from a .gz tarball. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-05-17 12:19 Message: Logged In: YES user_id=290026 In which environment do you try to build expat? Is this a checkout from CVD or did you download the .gz archive? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1490371&group_id=10127 From noreply at sourceforge.net Tue Dec 19 11:02:22 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 19 Dec 2006 02:02:22 -0800 Subject: [Expat-bugs] [ expat-Bugs-1618673 ] expat 2.0.0 compile problem on SCO-Unix 5.0.5 Message-ID: Bugs item #1618673, was opened at 2006-12-19 02:02 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1618673&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: www.libexpat.org Group: Third-party Bug Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: expat 2.0.0 compile problem on SCO-Unix 5.0.5 Initial Comment: Message from mstabile at metsogeda.it ---------------------------------- Hi, I'm trying to compile your expat 2.0.0 on a sco5.0.5 server but i'm facing with some problems. first: in Makefile.in INSTALL_ROOT ?= $(DESTDIR) or previous ifndef ... sentence don't work . It work (It doesn't give "Must be a separator on rules line 47 (bu39)." message) only with INSTALL_ROOT = $(DESTDIR) Second and hardest problem is: executing make I get an error. with debug mode the message is: ..... + eval cc -I./lib -I. -g -belf -DHAVE_EXPAT_CONFIG_H -o xmlwf/.libs/xmlwf xmlwf/ xmlwf.o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o ./.libs/libexpat.s o -Wl,-R,/usr/local/lib + cc -I./lib -I. -g -belf -DHAVE_EXPAT_CONFIG_H -o xmlwf/.libs/xmlwf xmlwf/xmlwf .o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o ./.libs/libexpat.so -Wl, -R,/usr/local/lib command line: fatal error: illegal value for -R: /usr/local/lib + exit 1 *** Error code 1 (bu21) > -------------- executing cc in debug mode i get cc: 'ld' '-Ra,XPG4PLUS,elf' '-Y' 'P,/usr/ccs/lib:/lib:/usr/lib' '/usr/ccs/lib/c rt1.o' '/usr/ccs/lib/values-Xa.o' '-o' 'xmlwf/.libs/xmlwf' 'xmlwf/xmlwf.o' 'xmlw f/xmlfile.o' 'xmlwf/codepage.o' 'xmlwf/readfilemap.o' './.libs/libexpat.so' '-R' '/usr/local/lib' '-Qy' '-lcrypt' '-lgen' '-lc' '/usr/ccs/lib/crtn.o' cc: process: /usr/ccs/bin/elf/ld command line: fatal error: illegal value for -R: /usr/local/lib So the problem is the -R parameter passed to ld command that does not allow /usr/local/lib as argument as you can see from these part of ld man --------- ....... -Rarg[,arg,...] Set runtime-behavior characteristics. The option accepts a comma-separated list of arguments. Note that there is no space between -R and its arguments. Each argument is one of the accepted values for the -a, -b, or -X flags of cc(CP), and should match the flags used when the objects were compiled. The default is -Rxpg4plus,elf,a for the ELF ld, and -Rxpg4plus,coff,a for the COFF ld. The ELF ld ignores -Rcoff and -Ribcs2; the COFF ld ignores -Relf. Multiple -R arguments may be given; the last argument of each type ( -a, -b, or -X) is the one used. For example, -Ransi,a -Rxpg4,coff is equivalent to -Rxpg4,coff,a. ........ So, I belive some ld parameter must be changed but what? TIA , I hope you can send me the solution ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1618673&group_id=10127 From noreply at sourceforge.net Tue Dec 19 11:26:57 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 19 Dec 2006 02:26:57 -0800 Subject: [Expat-bugs] [ expat-Bugs-1618673 ] expat 2.0.0 compile problem on SCO-Unix 5.0.5 Message-ID: Bugs item #1618673, was opened at 2006-12-19 02:02 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1618673&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: www.libexpat.org Group: Third-party Bug Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: expat 2.0.0 compile problem on SCO-Unix 5.0.5 Initial Comment: Message from mstabile at metsogeda.it ---------------------------------- Hi, I'm trying to compile your expat 2.0.0 on a sco5.0.5 server but i'm facing with some problems. first: in Makefile.in INSTALL_ROOT ?= $(DESTDIR) or previous ifndef ... sentence don't work . It work (It doesn't give "Must be a separator on rules line 47 (bu39)." message) only with INSTALL_ROOT = $(DESTDIR) Second and hardest problem is: executing make I get an error. with debug mode the message is: ..... + eval cc -I./lib -I. -g -belf -DHAVE_EXPAT_CONFIG_H -o xmlwf/.libs/xmlwf xmlwf/ xmlwf.o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o ./.libs/libexpat.s o -Wl,-R,/usr/local/lib + cc -I./lib -I. -g -belf -DHAVE_EXPAT_CONFIG_H -o xmlwf/.libs/xmlwf xmlwf/xmlwf .o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o ./.libs/libexpat.so -Wl, -R,/usr/local/lib command line: fatal error: illegal value for -R: /usr/local/lib + exit 1 *** Error code 1 (bu21) > -------------- executing cc in debug mode i get cc: 'ld' '-Ra,XPG4PLUS,elf' '-Y' 'P,/usr/ccs/lib:/lib:/usr/lib' '/usr/ccs/lib/c rt1.o' '/usr/ccs/lib/values-Xa.o' '-o' 'xmlwf/.libs/xmlwf' 'xmlwf/xmlwf.o' 'xmlw f/xmlfile.o' 'xmlwf/codepage.o' 'xmlwf/readfilemap.o' './.libs/libexpat.so' '-R' '/usr/local/lib' '-Qy' '-lcrypt' '-lgen' '-lc' '/usr/ccs/lib/crtn.o' cc: process: /usr/ccs/bin/elf/ld command line: fatal error: illegal value for -R: /usr/local/lib So the problem is the -R parameter passed to ld command that does not allow /usr/local/lib as argument as you can see from these part of ld man --------- ....... -Rarg[,arg,...] Set runtime-behavior characteristics. The option accepts a comma-separated list of arguments. Note that there is no space between -R and its arguments. Each argument is one of the accepted values for the -a, -b, or -X flags of cc(CP), and should match the flags used when the objects were compiled. The default is -Rxpg4plus,elf,a for the ELF ld, and -Rxpg4plus,coff,a for the COFF ld. The ELF ld ignores -Rcoff and -Ribcs2; the COFF ld ignores -Relf. Multiple -R arguments may be given; the last argument of each type ( -a, -b, or -X) is the one used. For example, -Ransi,a -Rxpg4,coff is equivalent to -Rxpg4,coff,a. ........ So, I belive some ld parameter must be changed but what? TIA , I hope you can send me the solution ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-12-19 02:26 Message: Logged In: NO Message from mstabile at metsogeda.it ----------------------------------- Command cc -I./lib -I. -g -belf -DHAVE_EXPAT_CONFIG_H -o xmlwf/.libs/xmlwf xmlwf/xmlwf.o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o ./.libs/libexpat.so -Wl,-L,/usr/local/lib seems to work and create xmlwf/.libs/xmlwf How libtool should be changed? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1618673&group_id=10127 From noreply at sourceforge.net Tue Dec 19 16:30:31 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 19 Dec 2006 07:30:31 -0800 Subject: [Expat-bugs] [ expat-Bugs-1618673 ] expat 2.0.0 compile problem on SCO-Unix 5.0.5 Message-ID: Bugs item #1618673, was opened at 2006-12-19 05:02 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1618673&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: www.libexpat.org Group: Third-party Bug Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: expat 2.0.0 compile problem on SCO-Unix 5.0.5 Initial Comment: Message from mstabile at metsogeda.it ---------------------------------- Hi, I'm trying to compile your expat 2.0.0 on a sco5.0.5 server but i'm facing with some problems. first: in Makefile.in INSTALL_ROOT ?= $(DESTDIR) or previous ifndef ... sentence don't work . It work (It doesn't give "Must be a separator on rules line 47 (bu39)." message) only with INSTALL_ROOT = $(DESTDIR) Second and hardest problem is: executing make I get an error. with debug mode the message is: ..... + eval cc -I./lib -I. -g -belf -DHAVE_EXPAT_CONFIG_H -o xmlwf/.libs/xmlwf xmlwf/ xmlwf.o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o ./.libs/libexpat.s o -Wl,-R,/usr/local/lib + cc -I./lib -I. -g -belf -DHAVE_EXPAT_CONFIG_H -o xmlwf/.libs/xmlwf xmlwf/xmlwf .o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o ./.libs/libexpat.so -Wl, -R,/usr/local/lib command line: fatal error: illegal value for -R: /usr/local/lib + exit 1 *** Error code 1 (bu21) > -------------- executing cc in debug mode i get cc: 'ld' '-Ra,XPG4PLUS,elf' '-Y' 'P,/usr/ccs/lib:/lib:/usr/lib' '/usr/ccs/lib/c rt1.o' '/usr/ccs/lib/values-Xa.o' '-o' 'xmlwf/.libs/xmlwf' 'xmlwf/xmlwf.o' 'xmlw f/xmlfile.o' 'xmlwf/codepage.o' 'xmlwf/readfilemap.o' './.libs/libexpat.so' '-R' '/usr/local/lib' '-Qy' '-lcrypt' '-lgen' '-lc' '/usr/ccs/lib/crtn.o' cc: process: /usr/ccs/bin/elf/ld command line: fatal error: illegal value for -R: /usr/local/lib So the problem is the -R parameter passed to ld command that does not allow /usr/local/lib as argument as you can see from these part of ld man --------- ....... -Rarg[,arg,...] Set runtime-behavior characteristics. The option accepts a comma-separated list of arguments. Note that there is no space between -R and its arguments. Each argument is one of the accepted values for the -a, -b, or -X flags of cc(CP), and should match the flags used when the objects were compiled. The default is -Rxpg4plus,elf,a for the ELF ld, and -Rxpg4plus,coff,a for the COFF ld. The ELF ld ignores -Rcoff and -Ribcs2; the COFF ld ignores -Relf. Multiple -R arguments may be given; the last argument of each type ( -a, -b, or -X) is the one used. For example, -Ransi,a -Rxpg4,coff is equivalent to -Rxpg4,coff,a. ........ So, I belive some ld parameter must be changed but what? TIA , I hope you can send me the solution ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-12-19 10:30 Message: Logged In: YES user_id=290026 Originator: NO All our Unix build experts have been unresponsive for a while. I am not sure I can really help you there. I can only recommend to search Google for problems with ld on SCO. And, in the spirit of support for OpenSource projects, why don't you ditch SCO in favour of Linux? :-) ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-12-19 05:26 Message: Logged In: NO Message from mstabile at metsogeda.it ----------------------------------- Command cc -I./lib -I. -g -belf -DHAVE_EXPAT_CONFIG_H -o xmlwf/.libs/xmlwf xmlwf/xmlwf.o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o ./.libs/libexpat.so -Wl,-L,/usr/local/lib seems to work and create xmlwf/.libs/xmlwf How libtool should be changed? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1618673&group_id=10127 From noreply at sourceforge.net Tue Dec 19 16:43:27 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 19 Dec 2006 07:43:27 -0800 Subject: [Expat-bugs] [ expat-Bugs-1618673 ] expat 2.0.0 compile problem on SCO-Unix 5.0.5 Message-ID: Bugs item #1618673, was opened at 2006-12-19 05:02 Message generated for change (Comment added) made by fdrake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1618673&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: www.libexpat.org Group: Third-party Bug Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: expat 2.0.0 compile problem on SCO-Unix 5.0.5 Initial Comment: Message from mstabile at metsogeda.it ---------------------------------- Hi, I'm trying to compile your expat 2.0.0 on a sco5.0.5 server but i'm facing with some problems. first: in Makefile.in INSTALL_ROOT ?= $(DESTDIR) or previous ifndef ... sentence don't work . It work (It doesn't give "Must be a separator on rules line 47 (bu39)." message) only with INSTALL_ROOT = $(DESTDIR) Second and hardest problem is: executing make I get an error. with debug mode the message is: ..... + eval cc -I./lib -I. -g -belf -DHAVE_EXPAT_CONFIG_H -o xmlwf/.libs/xmlwf xmlwf/ xmlwf.o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o ./.libs/libexpat.s o -Wl,-R,/usr/local/lib + cc -I./lib -I. -g -belf -DHAVE_EXPAT_CONFIG_H -o xmlwf/.libs/xmlwf xmlwf/xmlwf .o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o ./.libs/libexpat.so -Wl, -R,/usr/local/lib command line: fatal error: illegal value for -R: /usr/local/lib + exit 1 *** Error code 1 (bu21) > -------------- executing cc in debug mode i get cc: 'ld' '-Ra,XPG4PLUS,elf' '-Y' 'P,/usr/ccs/lib:/lib:/usr/lib' '/usr/ccs/lib/c rt1.o' '/usr/ccs/lib/values-Xa.o' '-o' 'xmlwf/.libs/xmlwf' 'xmlwf/xmlwf.o' 'xmlw f/xmlfile.o' 'xmlwf/codepage.o' 'xmlwf/readfilemap.o' './.libs/libexpat.so' '-R' '/usr/local/lib' '-Qy' '-lcrypt' '-lgen' '-lc' '/usr/ccs/lib/crtn.o' cc: process: /usr/ccs/bin/elf/ld command line: fatal error: illegal value for -R: /usr/local/lib So the problem is the -R parameter passed to ld command that does not allow /usr/local/lib as argument as you can see from these part of ld man --------- ....... -Rarg[,arg,...] Set runtime-behavior characteristics. The option accepts a comma-separated list of arguments. Note that there is no space between -R and its arguments. Each argument is one of the accepted values for the -a, -b, or -X flags of cc(CP), and should match the flags used when the objects were compiled. The default is -Rxpg4plus,elf,a for the ELF ld, and -Rxpg4plus,coff,a for the COFF ld. The ELF ld ignores -Rcoff and -Ribcs2; the COFF ld ignores -Relf. Multiple -R arguments may be given; the last argument of each type ( -a, -b, or -X) is the one used. For example, -Ransi,a -Rxpg4,coff is equivalent to -Rxpg4,coff,a. ........ So, I belive some ld parameter must be changed but what? TIA , I hope you can send me the solution ---------------------------------------------------------------------- >Comment By: Fred L. Drake, Jr. (fdrake) Date: 2006-12-19 10:43 Message: Logged In: YES user_id=3066 Originator: NO > All our Unix build experts have been unresponsive for a while. Sadly, that's me. I've never used SCO Unix myself. Whether a new libtool fixes this problem, I don't know. If anyone can verify that, we can see about using an updated libtool. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-12-19 10:30 Message: Logged In: YES user_id=290026 Originator: NO All our Unix build experts have been unresponsive for a while. I am not sure I can really help you there. I can only recommend to search Google for problems with ld on SCO. And, in the spirit of support for OpenSource projects, why don't you ditch SCO in favour of Linux? :-) ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-12-19 05:26 Message: Logged In: NO Message from mstabile at metsogeda.it ----------------------------------- Command cc -I./lib -I. -g -belf -DHAVE_EXPAT_CONFIG_H -o xmlwf/.libs/xmlwf xmlwf/xmlwf.o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o ./.libs/libexpat.so -Wl,-L,/usr/local/lib seems to work and create xmlwf/.libs/xmlwf How libtool should be changed? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1618673&group_id=10127 From noreply at sourceforge.net Tue Dec 19 19:48:59 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 19 Dec 2006 10:48:59 -0800 Subject: [Expat-bugs] [ expat-Bugs-1618673 ] expat 2.0.0 compile problem on SCO-Unix 5.0.5 Message-ID: Bugs item #1618673, was opened at 2006-12-19 05:02 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1618673&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: www.libexpat.org Group: Third-party Bug Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: expat 2.0.0 compile problem on SCO-Unix 5.0.5 Initial Comment: Message from mstabile at metsogeda.it ---------------------------------- Hi, I'm trying to compile your expat 2.0.0 on a sco5.0.5 server but i'm facing with some problems. first: in Makefile.in INSTALL_ROOT ?= $(DESTDIR) or previous ifndef ... sentence don't work . It work (It doesn't give "Must be a separator on rules line 47 (bu39)." message) only with INSTALL_ROOT = $(DESTDIR) Second and hardest problem is: executing make I get an error. with debug mode the message is: ..... + eval cc -I./lib -I. -g -belf -DHAVE_EXPAT_CONFIG_H -o xmlwf/.libs/xmlwf xmlwf/ xmlwf.o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o ./.libs/libexpat.s o -Wl,-R,/usr/local/lib + cc -I./lib -I. -g -belf -DHAVE_EXPAT_CONFIG_H -o xmlwf/.libs/xmlwf xmlwf/xmlwf .o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o ./.libs/libexpat.so -Wl, -R,/usr/local/lib command line: fatal error: illegal value for -R: /usr/local/lib + exit 1 *** Error code 1 (bu21) > -------------- executing cc in debug mode i get cc: 'ld' '-Ra,XPG4PLUS,elf' '-Y' 'P,/usr/ccs/lib:/lib:/usr/lib' '/usr/ccs/lib/c rt1.o' '/usr/ccs/lib/values-Xa.o' '-o' 'xmlwf/.libs/xmlwf' 'xmlwf/xmlwf.o' 'xmlw f/xmlfile.o' 'xmlwf/codepage.o' 'xmlwf/readfilemap.o' './.libs/libexpat.so' '-R' '/usr/local/lib' '-Qy' '-lcrypt' '-lgen' '-lc' '/usr/ccs/lib/crtn.o' cc: process: /usr/ccs/bin/elf/ld command line: fatal error: illegal value for -R: /usr/local/lib So the problem is the -R parameter passed to ld command that does not allow /usr/local/lib as argument as you can see from these part of ld man --------- ....... -Rarg[,arg,...] Set runtime-behavior characteristics. The option accepts a comma-separated list of arguments. Note that there is no space between -R and its arguments. Each argument is one of the accepted values for the -a, -b, or -X flags of cc(CP), and should match the flags used when the objects were compiled. The default is -Rxpg4plus,elf,a for the ELF ld, and -Rxpg4plus,coff,a for the COFF ld. The ELF ld ignores -Rcoff and -Ribcs2; the COFF ld ignores -Relf. Multiple -R arguments may be given; the last argument of each type ( -a, -b, or -X) is the one used. For example, -Ransi,a -Rxpg4,coff is equivalent to -Rxpg4,coff,a. ........ So, I belive some ld parameter must be changed but what? TIA , I hope you can send me the solution ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2006-12-19 13:48 Message: Logged In: YES user_id=290026 Originator: NO When I made the Expat 2.0 tarball I used libtool 1.5.22. Is that new enough? ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2006-12-19 10:43 Message: Logged In: YES user_id=3066 Originator: NO > All our Unix build experts have been unresponsive for a while. Sadly, that's me. I've never used SCO Unix myself. Whether a new libtool fixes this problem, I don't know. If anyone can verify that, we can see about using an updated libtool. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-12-19 10:30 Message: Logged In: YES user_id=290026 Originator: NO All our Unix build experts have been unresponsive for a while. I am not sure I can really help you there. I can only recommend to search Google for problems with ld on SCO. And, in the spirit of support for OpenSource projects, why don't you ditch SCO in favour of Linux? :-) ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-12-19 05:26 Message: Logged In: NO Message from mstabile at metsogeda.it ----------------------------------- Command cc -I./lib -I. -g -belf -DHAVE_EXPAT_CONFIG_H -o xmlwf/.libs/xmlwf xmlwf/xmlwf.o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o ./.libs/libexpat.so -Wl,-L,/usr/local/lib seems to work and create xmlwf/.libs/xmlwf How libtool should be changed? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1618673&group_id=10127 From noreply at sourceforge.net Sun Dec 31 02:21:05 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 30 Dec 2006 17:21:05 -0800 Subject: [Expat-bugs] [ expat-Bugs-1597115 ] 'make check' for expat-2.0.0 fails Message-ID: Bugs item #1597115, was opened at 2006-11-15 08:53 Message generated for change (Comment added) made by carenas You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1597115&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build control Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Sergei (sergeiste) Assigned to: Greg Stein (gstein) Summary: 'make check' for expat-2.0.0 fails Initial Comment: Hello, I am trying to build expat-2.0.0 in the framework of my http://appsfromscratch.berlios.de/ project and 'make check' fails with this screen output: " gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -o tests/runtests.o -c tests/runtests.c gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -o tests/chardata.o -c tests/chardata.c gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -o tests/minicheck.o -c tests/minicheck.c /bin/sh ./libtool --silent --mode=link gcc -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -o tests/runtests tests/runtests.o tests/chardat a.o tests/minicheck.o libexpat.la g++ -c -o tests/runtestspp.o tests/runtestspp.cpp tests/runtests.c: In function 'void test_line_number_after_parse()': tests/runtests.c:410: error: 'XML_Size' was not declared in this scope tests/runtests.c:410: error: expected `;' before 'lineno' tests/runtests.c:414: error: 'lineno' was not declared in this scope tests/runtests.c: In function 'void test_column_number_after_parse()': tests/runtests.c:428: error: 'XML_Size' was not declared in this scope tests/runtests.c:428: error: expected `;' before 'colno' tests/runtests.c:432: error: 'colno' was not declared in this scope tests/runtests.c: In function 'void test_line_number_after_error()': tests/runtests.c:514: error: 'XML_Size' was not declared in this scope tests/runtests.c:514: error: expected `;' before 'lineno' tests/runtests.c:518: error: 'lineno' was not declared in this scope tests/runtests.c: In function 'void test_column_number_after_error()': tests/runtests.c:534: error: 'XML_Size' was not declared in this scope tests/runtests.c:534: error: expected `;' before 'colno' tests/runtests.c:538: error: 'colno' was not declared in this scope make: *** [tests/runtestspp.o] Error 1 ". My system is: Linux comp.home.net 2.6.12-27mdk-i686-up-4GB #1 Tue Sep 26 12:41:29 MDT 2006 i686 AMD Athlon(tm) XP 1900+ unknown GNU/Linux ---------------------------------------------------------------------- Comment By: Carlo Marcelo Arenas Belon (carenas) Date: 2006-12-30 17:21 Message: Logged In: YES user_id=36771 Originator: NO using the system headers instead of the ones that are being installed is a bug, and was fixed in CVS in version 1.54 of Makefile.in with a reference to bug 1408143 ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-25 09:34 Message: Logged In: YES user_id=290026 Originator: NO CVS based tarball tested by Sergei and found to work OK. Closing this issue as fixed. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-22 06:35 Message: Logged In: YES user_id=290026 Originator: NO Sending it by e-mail is hard not having your address. Anyway, all that make-release.sh does is run buildconf.sh. Whether I do it or you should make no difference, except for the likelyhood that the installed versions of libtool and autoconf are not the same, but that applies for each of us Expat developers as well. I also don't have Linux at home, but must wait to get access at work, which is not always possible. You may have to wait a while. ---------------------------------------------------------------------- Comment By: Sergei (sergeiste) Date: 2006-11-21 22:17 Message: Logged In: YES user_id=1270005 Originator: YES You can make a tarball and send it to me by Email. Again, my point is that I run the standard ./configure make make check make install sequence. Consider me your QA, who performs exactly the same actions end user does. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-21 19:23 Message: Logged In: YES user_id=290026 Originator: NO The final tarball would be a new release. I am not sure when we will do one. Anyway, after the checkout, you can run ./make_release.sh HEAD That should give you a proper tarball. The result should be the same as with buildconf.sh. ---------------------------------------------------------------------- Comment By: Sergei (sergeiste) Date: 2006-11-21 16:18 Message: Logged In: YES user_id=1270005 Originator: YES Regarding " It's just a simple to do a CVS checkout and less work for me. Instructions here: http://sourceforge.net/cvs/?group_id=10127 " - my points are different. End users are supposed to run ./configure make make check make install without the ./buildconf.sh'. End users (at least myself) are going to use the tarball, not CVS checkout. So, before you close the bug, I'd like to make sure that the final tarball will live up to ./configure make make check make install expectation. I recently helped to close a bug in a GNU utility, and the mantainer gave me a link to a GNU server with 'alpha' in its hostname (don't exactly remember it), so I was able to try the final tarball, not the CVS checkout. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-21 15:37 Message: Logged In: YES user_id=290026 Originator: NO It's just a simple to do a CVS checkout and less work for me. Instructions here: http://sourceforge.net/cvs/?group_id=10127 ---------------------------------------------------------------------- Comment By: Sergei (sergeiste) Date: 2006-11-21 15:24 Message: Logged In: YES user_id=1270005 Originator: YES Regarding "Well, if nobody objects then I intend to close this issue as fixed" - is there a ready to use tarball to be downloaded in which the problem is hopefully fixed ? If yes, I'd prefer to check it first. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-21 05:53 Message: Logged In: YES user_id=290026 Originator: NO Well, if nobody objects then I intend to close this issue as fixed. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-17 11:24 Message: Logged In: YES user_id=290026 Originator: NO Well, I just tried this on Fedora Core 4 with an up-to-date CVS checkout: First I uninstalled Expat and all header files I could find. Then I ran: ./buildconf.sh ./configure --prefix=/home/kwaclaw/expat_test make make check and I had no problems. Maybe you try CVS and see how it goes. ---------------------------------------------------------------------- Comment By: Sergei (sergeiste) Date: 2006-11-17 09:42 Message: Logged In: YES user_id=1270005 Originator: YES Regarding "For anyone who is impatient I can only recommend to follow the advice (found through Google) to copy the headers to the install location first, and then make check should work " I do not think it will be the case for me - because my tool does not run with root privileges and by default does not install into system location. It's the intent of my tool, I am developing to be able to try the versions I like and not to screw up. So, if the existing build mechanism is unable to find the required *.h file(s) under /AppsFromScratchWD/build/expat-2.0.0 (the build directory), why does anybody think it will find them under /AppsFromScratchWD/install/expat-2.0.0 which is the install directory ? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-17 08:55 Message: Logged In: YES user_id=290026 Originator: NO You are correct, obviously. But in this case the issue was to find out if the Expat code or test code was in error or just make check. I am pretty sure the code is correct, but the proof would be to run make install first. I any case, I will have to leave the final decision which solution is best to our Make experts. For anyone who is impatient I can only recommend to follow the advice (found through Google) to copy the headers to the install location first, and then make check should work. Karl ---------------------------------------------------------------------- Comment By: Steve Kelem (skelem) Date: 2006-11-17 08:46 Message: Logged In: YES user_id=177313 Originator: NO Changing the build order to make make install make check is counter-intuitive and dangerous. The idea behind doing the check first is to make sure that the software is going to work before installing it. I've messed up installation of a software package enough times by "assuming it will all work" and installing before really checking out a package. I found that I've messed up the whole company, having them lose hours of work. Get "make check" to work before the installation of the software. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-16 16:35 Message: Logged In: YES user_id=290026 Originator: NO Obviously, there is an issue with make check. Asking why there is an issue really doesn't help resolving it. It is also not clear which is the best solution. I am not a Unix/Make expert and our Make authorities are "asleep", as I already said. Fred and Greg - this means you! ---------------------------------------------------------------------- Comment By: Sergei (sergeiste) Date: 2006-11-16 16:07 Message: Logged In: YES user_id=1270005 Originator: YES Regarding " In the Makefile, change CPPFLAGS = to CPPFLAGS = $(INCLUDES) $(DEFS) " - why doesn't 'configure' generate the correct 'Makefile' in the first place ? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-16 11:05 Message: Logged In: YES user_id=290026 Originator: NO Could anyone try the suggestion made in bug# 1557638? (See previous post) ---------------------------------------------------------------------- Comment By: Steve Kelem (skelem) Date: 2006-11-16 10:30 Message: Logged In: YES user_id=177313 Originator: NO In the Makefile, change CPPFLAGS = to CPPFLAGS = $(INCLUDES) $(DEFS) ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-16 10:18 Message: Logged In: YES user_id=290026 Originator: NO No expat_external.h is used, it is included from within expat.h, as I already said before. ---------------------------------------------------------------------- Comment By: Sergei (sergeiste) Date: 2006-11-16 09:17 Message: Logged In: YES user_id=1270005 Originator: YES Regarding " I already answered this: Using an older version of expat_external.h explains your errors. It's not too difficult to find yourself. " - no, the problem is that 'expat_external.h' is NOT used at all. This is the list of files included into the problematic 'tests/runtests.c': #include #include #include #include #include #include "expat.h" #include "chardata.h" #include "minicheck.h" #include " - there is NO 'expat_external.h' in the list, that's what I wrote earlier and that's why I'm saying that 'tests/runtests.c' cannot be compiled by construction. If you still think whatever (old, new, right, wrong) 'expat_external.h' is included into 'tests/runtests.c', could you please explain me how ? I.e. through which include file from the above list, or at which line number of 'tests/runtests.c' ? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-16 08:46 Message: Logged In: YES user_id=290026 Originator: NO I already answered this: Using an older version of expat_external.h explains your errors. It's not too difficult to find yourself. ---------------------------------------------------------------------- Comment By: Sergei (sergeiste) Date: 2006-11-15 21:01 Message: Logged In: YES user_id=1270005 Originator: YES Could you please answer one simple question: "from which file XML_Size is supposed to get value ?". It's a simple question - isn't it ? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-15 19:24 Message: Logged In: YES user_id=290026 Originator: NO When we released Expat 2.0 make check worked for us. So, your issue is not an issue with Expat, but maybe with make check. As I already said, it's likely picking up the headers of an installed version and if an older version is installed, its likely using revision 1.4 or older of expat_external.h, which would explain your errors. expat_external.h is included by expat.h, btw. However, if you run make install first, then make check should succeed. Or you copy the header file to the install location first. ---------------------------------------------------------------------- Comment By: Sergei (sergeiste) Date: 2006-11-15 18:12 Message: Logged In: YES user_id=1270005 Originator: YES I don't quite get the explanations. The essence of my tool is that it builds and installs everything in local directories, e.g. for 'expat' they are: /maxtor5/sergei/AppsFromScratchWD/build/expat-2.0.0 /maxtor5/sergei/AppsFromScratchWD/install/expat-2.0.0 , so why should 'expat' behave differently than other libs/apps ? I mean, the whole point of 'make check' is that everything should be checked in local directory. Could you please specifically address the issue of 'lib/expat_external.h' ? Here are my points: 1) compilation fails because XML_Size is undefined - see the above " tests/runtests.c:410: error: 'XML_Size' was not declared in this scope ". Is this correct - (YES/NO) ? 2) output of "grep '#include ' /maxtor5/sergei/AppsFromScratchWD/build/expat-2.0.0/tests/runtests.c": " #include #include #include #include #include #include "expat.h" #include "chardata.h" #include "minicheck.h" #include "; 3) output of "grep -r XML_Size /maxtor5/sergei/AppsFromScratchWD/build/expat-2.0.0 | grep "\.h" | grep -v "\.html" | grep typedef": " /maxtor5/sergei/AppsFromScratchWD/build/expat-2.0.0/amiga/include/libraries/expat.h:typedef unsigned long XML_Size; /maxtor5/sergei/AppsFromScratchWD/build/expat-2.0.0/lib/expat_external.h:typedef unsigned __int64 XML_Size; /maxtor5/sergei/AppsFromScratchWD/build/expat-2.0.0/lib/expat_external.h:typedef unsigned long long XML_Size; /maxtor5/sergei/AppsFromScratchWD/build/expat-2.0.0/lib/expat_external.h:typedef unsigned long XML_Size; " - of the above the file of potential interest for me is /maxtor5/sergei/AppsFromScratchWD/build/expat-2.0.0/lib/expat_external.h - because the other one, /maxtor5/sergei/AppsFromScratchWD/build/expat-2.0.0/amiga/include/libraries/expat.h appears to be amiga-specific - not my case. So, I draw the conclusion that 'lib/expat_external.h' the file of interest. Is this correct (YES/NO) ? 4) if '3)' is correct, then 'tests/runtests.c' cannot be compiled by definition - its list of include files (see '2)', here is is again): " #include #include #include #include #include #include "expat.h" #include "chardata.h" #include "minicheck.h" #include " , and there is no 'lib/expat_external.h' in the above list. Is there an error in the chain of reasoning I gave ? If yes, where is it ? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-15 10:49 Message: Logged In: YES user_id=290026 Originator: NO To be more precise - make check is probably picking up the wrong header files, that is the installed ones instead of the new ones. You could fake it by copying the new header files over the installed ones. Karl ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-15 10:28 Message: Logged In: YES user_id=290026 Originator: NO Well, it seems to me that make check is picking up the installed version of Expat, which in your case is probably the one coming with your Linux installation. If you know how to write Make files, maybe you have a look and tell me how to fix this. I am the Windows guy around here, and the Linux guys are all asleep. Karl ---------------------------------------------------------------------- Comment By: Sergei (sergeiste) Date: 2006-11-15 10:20 Message: Logged In: YES user_id=1270005 Originator: YES "Well, have you tried it with make install first?" - No, I haven't. The point of my tool is that it runs commands for me. I can change order of make targets, i.e. I can make it make make install make check , but at the moment I'm in the middle of long build, so I'd prefer not to interfere with the process. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-15 10:06 Message: Logged In: YES user_id=290026 Originator: NO Well, have you tried it with make install first? ---------------------------------------------------------------------- Comment By: Sergei (sergeiste) Date: 2006-11-15 09:34 Message: Logged In: YES user_id=1270005 Originator: YES Quick 'grep -r' shows: /maxtor5/sergei/AppsFromScratchWD/build/expat-2.0.0/lib/expat_external.h:typedef unsigned __int64 XML_Size; /maxtor5/sergei/AppsFromScratchWD/build/expat-2.0.0/lib/expat_external.h:typedef unsigned long long XML_Size; /maxtor5/sergei/AppsFromScratchWD/build/expat-2.0.0/lib/expat_external.h:typedef unsigned long XML_Size; , i.e. apparently 'tests/runtests.c' whose compilation fails apparently needs'lib/expat_external.h' to be included in order to make XML_Size defined/declared. ---------------------------------------------------------------------- Comment By: Sergei (sergeiste) Date: 2006-11-15 09:20 Message: Logged In: YES user_id=1270005 Originator: YES Regarding "What happens if you run make install first?" - I assumed standard ./configure make make check make install sequence, i.e. I didn't run 'make install' before 'make check'. Shouldn't stuff be installed only after it is checked ? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2006-11-15 09:07 Message: Logged In: YES user_id=290026 Originator: NO What happens if you run make install first? ---------------------------------------------------------------------- Comment By: Sergei (sergeiste) Date: 2006-11-15 08:55 Message: Logged In: YES user_id=1270005 Originator: YES Compiler info: " [3] 18:53 sergei at comp.home.net:/maxtor5/sergei/AppsFromScratchWD> gcc -v Using built-in specs. Target: i586-mandriva-linux-gnu Configured with: ../configure --prefix=/usr --libexecdir=/usr/lib --with-slibdir=/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --enable-languages=c,c++,ada,f95,objc,java --host=i586-mandriva-linux-gnu --with-system-zlib --enable-long-long --enable-__cxa_atexit --enable-clocale=gnu --disable-libunwind-exceptions --enable-java-awt=gtk --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre --enable-gtk-cairo --disable-libjava-multilib Thread model: posix gcc version 4.0.1 (4.0.1-5mdk for Mandriva Linux release 2006.0) ". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1597115&group_id=10127