From noreply at sourceforge.net  Thu May  1 13:04:32 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu May  1 15:04:36 2003
Subject: [Expat-bugs] [ expat-Bugs-730947 ] unknown encoding handler... bug?
	or i'm just stupid?
Message-ID: <E19BJM8-000539-00@sc8-sf-web1.sourceforge.net>

Bugs item #730947, was opened at 2003-05-01 12:04
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=730947&group_id=10127

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: unknown encoding handler... bug? or i'm just stupid?

Initial Comment:
i have  a simple written handler for windows-1250 
encoding like this (expat 1.95.5, win32):




int encoding_handler(void *data, const char *name, 
XML_Encoding *info)


{


  int i;


  if(strcmp(name,"windows-1250")!=0) return 0;




  for(i=0;i<256;i++) 


    info->map[i] = windows1250[i]; /* windows1250 
is windows-1250 to unicode mapping table */


  


  info->data = NULL; 


  info->convert = NULL;


  info->release = NULL;  




  return 1;


}




handler was set up using this code:


XML_SetUnknownEncodingHandler(parser,  
encoding_handler, NULL);




and when i try to parse this xml file:


<?xml version="1.0" encoding="windows-1250"?>




<document>


</document>




i get unknown encoding error. maybe i'm crazy but 
really need help (and no fourum exist, anyway:))


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

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

From noreply at sourceforge.net  Thu May  1 20:29:02 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu May  1 22:29:09 2003
Subject: [Expat-bugs] [ expat-Bugs-730947 ] unknown encoding handler... bug?
	or i'm just stupid?
Message-ID: <E19BQII-0007bS-00@sc8-sf-web2.sourceforge.net>

Bugs item #730947, was opened at 2003-05-01 15:04
Message generated for change (Comment added) made by kwaclaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=730947&group_id=10127

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: unknown encoding handler... bug? or i'm just stupid?

Initial Comment:
i have  a simple written handler for windows-1250 
encoding like this (expat 1.95.5, win32):




int encoding_handler(void *data, const char *name, 
XML_Encoding *info)


{


  int i;


  if(strcmp(name,"windows-1250")!=0) return 0;




  for(i=0;i<256;i++) 


    info->map[i] = windows1250[i]; /* windows1250 
is windows-1250 to unicode mapping table */


  


  info->data = NULL; 


  info->convert = NULL;


  info->release = NULL;  




  return 1;


}




handler was set up using this code:


XML_SetUnknownEncodingHandler(parser,  
encoding_handler, NULL);




and when i try to parse this xml file:


<?xml version="1.0" encoding="windows-1250"?>




<document>


</document>




i get unknown encoding error. maybe i'm crazy but 
really need help (and no fourum exist, anyway:))


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

>Comment By: Karl Waclawek (kwaclaw)
Date: 2003-05-01 22:29

Message:
Logged In: YES 
user_id=290026

How is your Expat compiled, for UTF-8 or for UTF-16 
(XML_UNICODE_WCHAR_T defined)?
Also, check if that file has been saved as "Unicode" 
in Windows (look at it with a hex editor).



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

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

From beebe at math.utah.edu  Sat May  3 10:43:43 2003
From: beebe at math.utah.edu (Nelson H. F. Beebe)
Date: Sat May  3 12:29:14 2003
Subject: [Expat-bugs] expat-1.95.6: build feedback
Message-ID: <CMM.0.92.0.1051976623.beebe@suncore.math.utah.edu>

I made build attempts for expat-1.95.6 in 53 build environments on 16
Unix platforms.  Most ultimately succeeded, but none without help.

* The check package is required from expat-1.95.3 on, but nowhere
  in the top-level documentation could I find any warning of that.  I
  ultimately found a mention of it in the expat bug mail archives.  Once
  I got check-0.8.4 installed, progress was better.

* configure should verify that check.h and -lcheck are available, and if
  not, issue a prominent warning that shows the installer where to find
  the check package:  I found it at

	http://check.sourceforge.net/

  which leads to the distribution file at

	http://easynews.dl.sourceforge.net/sourceforge/check/check-0.8.4.tar.gz

* On most systems, even after check-0.8.4 was installed, check.h
  could not be found.  The problem is in the settings of INCLUDES and
  CFLAGS in the Makefile: both should have -I$(prefix)/include, since
  few compilers search that directory by default.  Ideally, CFLAGS
  should be set to something like

	CFLAGS = @CFLAGS@ $(INCLUDES)

  in Makefile.in to avoid duplication of the -I options.

* The order of -I options is critical; most of my systems
  had expat-1.95.2 installed, but there are new symbols in the latest
  expat.h.  These options must therefore be in the order

	  -I. -I$(srcdir)/lib -I$(prefix)/include

* Most systems do not automatically search $(prefix)/lib for
  libraries.  I therefore had to temporarily set
  LDFLAGS=-L$(prefix)/lib.

* The test programs run by "make check" need to be linked with
  the new version of the library, not an older one already installed
  on the system.  Thus, LDFLAGS needs to be set to

	  -L$(srcdir)/.libs/ -L$(prefix)/lib

  and then should also have the appropriate -R or -rpath or -Wl,-rpath
  setting that causes the linker to record in the executable the
  location of the shared libraries that were found at link time.
  Unfortunately, the setting of those is a portability nightmare.  At
  my site, I take care of them with automated build scripts that set
  them appropriately for each compiler/platform combination.

-------------------------------------------------------------------------------
- Nelson H. F. Beebe                    Tel: +1 801 581 5254                  -
- Center for Scientific Computing       FAX: +1 801 581 4148                  -
- University of Utah                    Internet e-mail: beebe@math.utah.edu  -
- Department of Mathematics, 110 LCB        beebe@acm.org  beebe@computer.org -
- 155 S 1400 E RM 233                       beebe@ieee.org                    -
- Salt Lake City, UT 84112-0090, USA    URL: http://www.math.utah.edu/~beebe  -
-------------------------------------------------------------------------------

From karl at waclawek.net  Sat May  3 21:20:01 2003
From: karl at waclawek.net (Karl Waclawek)
Date: Sat May  3 20:14:17 2003
Subject: [Expat-bugs] expat-1.95.6: build feedback
References: <CMM.0.92.0.1051976623.beebe@suncore.math.utah.edu>
Message-ID: <001701c311d2$e7306a20$0207a8c0@karl>


----- Original Message ----- 
From: "Nelson H. F. Beebe" <beebe@math.utah.edu>
To: <expat-bugs@python.org>
Cc: <beebe@math.utah.edu>
Sent: Saturday, May 03, 2003 11:43 AM


> I made build attempts for expat-1.95.6 in 53 build environments on 16
> Unix platforms.  Most ultimately succeeded, but none without help.
<snip>good stuff</snip>

Nelson,

many thanks for your detailed description of these build problems.
We appreciate your feedback, and our build experts will definitely
consider your suggestions.

Regards,

Karl

From noreply at sourceforge.net  Mon May  5 10:49:32 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon May  5 12:49:37 2003
Subject: [Expat-bugs] [ expat-Bugs-732794 ] Build issues on Unix platforms
Message-ID: <E19Cj9g-0006Px-00@sc8-sf-web1.sourceforge.net>

Bugs item #732794, was opened at 2003-05-05 12:49
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=732794&group_id=10127

Category: Build control
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Karl Waclawek (kwaclaw)
Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: Build issues on Unix platforms

Initial Comment:
Nelson Beebe reported a few issues while building
Expat 1.95.6 on various Unix platforms.
Attached as file beebe.txt.

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

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

From noreply at sourceforge.net  Thu May  8 01:20:26 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu May  8 03:20:39 2003
Subject: [Expat-bugs] [ expat-Bugs-676844 ] expat.h compile error: enum
	XML_Status
Message-ID: <E19Dfha-0000f1-00@sc8-sf-web4.sourceforge.net>

Bugs item #676844, was opened at 2003-01-29 16:37
Message generated for change (Comment added) made by pdon
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=676844&group_id=10127

Category: Build control
Group: None
Status: Open
Resolution: Fixed
Priority: 9
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: expat.h compile error: enum XML_Status

Initial Comment:
c++ -DHAVE_CONFIG_H -I. -I. -I../../autocfg -g -O2 -c
context.cpp  -fPIC -DPIC -o .libs/context.lo
In file included from parser.h:45,
                 from guard.h:143,
                 from context.cpp:45:
/usr/include/expat.h:657: use of enum `XML_Status'
without previous declaration
/usr/include/expat.h:736: multiple definition of `enum
XML_Status'


when building sablotron.

Hand editing the file to place the def of enum
XML_Status before any references to it fixes the problem.

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

Comment By: Donche, Pieter (pdon)
Date: 2003-05-08 09:20

Message:
Logged In: YES 
user_id=774177

SUN Sparc Enterprise 2170 Solaris 2.8 
gcc 3.2
Downloaded expat-1.95.6.tar.gz
./configure, make, make install OK
Downloaded Sablot-0.98.tar.gz (Sablotron package,
from www.gingerall.com)
./configure says:
...
checking expat.h presence... yes
expat.h: present but cannot be compiled
expat.h: check for missing prerequisite headers?
expat.h: proceeding with the preprocessor's result
##-------------------------------------------------##
## Report this to bug-autoconf@gnu.org ##
##-------------------------------------------------##
checking for expat.h... yes
checking wether expat.h is broken... yes
error: You probably have expat version 1.95.6. Please refer to
 http://sourceforge.net/tracker/index.php?
func=detail&aid=676844&group_id=10127&atid=110127
for a description of the problem

-- Looked at that web-page. Don't see a solution there.
Wath is the solution ?
Pieter.Donche@ua.ac.be


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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-04-16 15:59

Message:
Logged In: YES 
user_id=290026

Changed priority to highest to make it more visible,
so that double reporting incidents occur less frequently.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-03-27 11:42

Message:
Logged In: NO 

Same problem and the same fix under Linux and gcc 2.95.2.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-03-07 12:20

Message:
Logged In: NO 

same problem, same fix when building 1.95.6 on vms
(just downloaded .tar.gz & processed - got the rpm, but
don't know what to do with it - not an archive type I know
how to handle on vms, or windows either)
              - chris.sharman@ccagroup.co.uk

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-03-01 03:03

Message:
Logged In: YES 
user_id=290026

Strange - I had no problems with MS VC++ 6.0.
Which service pack level have you applied?

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

Comment By: Jacob Levy (jyljyljyl)
Date: 2003-03-01 02:35

Message:
Logged In: YES 
user_id=63723

This makes Expat 1.95.6 unusable for people who create
libraries that depend on Expat but don't include their own
copy of Expat. Sure, I can edit expat.h and fix it, but my
users should not be expected to do that.

For that reason I'm staying with Expat 1.95.5 until this
problem is fixed. It'd be really nice if you could make
Expat 1.95.7 soon..

In my case GCC 2.95.2 and VC++ 6.0 are complaining.


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

Comment By: Melvyn Sopacua (nyvlem)
Date: 2003-02-14 08:56

Message:
Logged In: YES 
user_id=212431

Yes, that works.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-02-06 21:47

Message:
Logged In: YES 
user_id=290026

But current CVS works for you, right?

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

Comment By: Melvyn Sopacua (nyvlem)
Date: 2003-02-06 21:17

Message:
Logged In: YES 
user_id=212431

> So far only gcc3.2 has complained.

Nope:
/usr/local/include/expat.h:657: use of enum `XML_Status' 
without previous declaration
/usr/local/include/expat.h:736: multiple definition of `enum 
XML_Status'
gmake[2]: *** [context.lo] Error 1
gmake[2]: Leaving directory 
`/home/mdev/cvs/sablot/src/engine'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/home/mdev/cvs/sablot/src'
gmake: *** [all-recursive] Error 1

$ gcc --version
2.95.3

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-01-31 15:43

Message:
Logged In: YES 
user_id=290026

It *is* fixed in CVS. Are you sure you checked out the 
right version, which is expat.h 1.51?

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-01-31 11:34

Message:
Logged In: NO 

I just got the same error, already fixed it. But don't 
understand why it isn't fixed in CVS ?

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

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2003-01-29 19:44

Message:
Logged In: YES 
user_id=3066

I've not checked the C89 standard yet, but Expat 1.95.6 is 
certainly dodgy in this case.  ;-(  The first draft of the C spec I 
found online certainly seemed to imply that any use of an 
incomplete enum is not allowed; I'm not likely to go out and 
buy a copy of the final spec to check further.  ;-)

As noted, this has been fixed in CVS.  Fixed the summary to 
better indicate what this report is about, and lowered the 
priority to get it out of the way for maintainers.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-01-29 16:51

Message:
Logged In: YES 
user_id=290026

So far only gcc3.2 has complained.
Not sure if this is a bug, since most compilers accept it,
but it has been fixed in CVS already anyway.

Set resolution status to fixed, but leave open.
There may be other users who would report this as a bug
and I want them to see the open report instead of 
having duplicates created.

Assigned to Fred - since he may know more about
whether this truly is a bug.

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

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

From noreply at sourceforge.net  Thu May  8 01:20:45 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu May  8 03:20:55 2003
Subject: [Expat-bugs] [ expat-Bugs-676844 ] expat.h compile error: enum
	XML_Status
Message-ID: <E19Dfht-0004Cc-00@sc8-sf-web2.sourceforge.net>

Bugs item #676844, was opened at 2003-01-29 16:37
Message generated for change (Comment added) made by pdon
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=676844&group_id=10127

Category: Build control
Group: None
Status: Open
Resolution: Fixed
Priority: 9
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: expat.h compile error: enum XML_Status

Initial Comment:
c++ -DHAVE_CONFIG_H -I. -I. -I../../autocfg -g -O2 -c
context.cpp  -fPIC -DPIC -o .libs/context.lo
In file included from parser.h:45,
                 from guard.h:143,
                 from context.cpp:45:
/usr/include/expat.h:657: use of enum `XML_Status'
without previous declaration
/usr/include/expat.h:736: multiple definition of `enum
XML_Status'


when building sablotron.

Hand editing the file to place the def of enum
XML_Status before any references to it fixes the problem.

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

Comment By: Donche, Pieter (pdon)
Date: 2003-05-08 09:20

Message:
Logged In: YES 
user_id=774177

SUN Sparc Enterprise 2170 Solaris 2.8 
gcc 3.2
Downloaded expat-1.95.6.tar.gz
./configure, make, make install OK
Downloaded Sablot-0.98.tar.gz (Sablotron package,
from www.gingerall.com)
./configure says:
...
checking expat.h presence... yes
expat.h: present but cannot be compiled
expat.h: check for missing prerequisite headers?
expat.h: proceeding with the preprocessor's result
##-------------------------------------------------##
## Report this to bug-autoconf@gnu.org ##
##-------------------------------------------------##
checking for expat.h... yes
checking wether expat.h is broken... yes
error: You probably have expat version 1.95.6. Please refer to
 http://sourceforge.net/tracker/index.php?
func=detail&aid=676844&group_id=10127&atid=110127
for a description of the problem

-- Looked at that web-page. Don't see a solution there.
Wath is the solution ?
Pieter.Donche@ua.ac.be


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

Comment By: Donche, Pieter (pdon)
Date: 2003-05-08 09:20

Message:
Logged In: YES 
user_id=774177

SUN Sparc Enterprise 2170 Solaris 2.8 
gcc 3.2
Downloaded expat-1.95.6.tar.gz
./configure, make, make install OK
Downloaded Sablot-0.98.tar.gz (Sablotron package,
from www.gingerall.com)
./configure says:
...
checking expat.h presence... yes
expat.h: present but cannot be compiled
expat.h: check for missing prerequisite headers?
expat.h: proceeding with the preprocessor's result
##-------------------------------------------------##
## Report this to bug-autoconf@gnu.org ##
##-------------------------------------------------##
checking for expat.h... yes
checking wether expat.h is broken... yes
error: You probably have expat version 1.95.6. Please refer to
 http://sourceforge.net/tracker/index.php?
func=detail&aid=676844&group_id=10127&atid=110127
for a description of the problem

-- Looked at that web-page. Don't see a solution there.
Wath is the solution ?
Pieter.Donche@ua.ac.be


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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-04-16 15:59

Message:
Logged In: YES 
user_id=290026

Changed priority to highest to make it more visible,
so that double reporting incidents occur less frequently.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-03-27 11:42

Message:
Logged In: NO 

Same problem and the same fix under Linux and gcc 2.95.2.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-03-07 12:20

Message:
Logged In: NO 

same problem, same fix when building 1.95.6 on vms
(just downloaded .tar.gz & processed - got the rpm, but
don't know what to do with it - not an archive type I know
how to handle on vms, or windows either)
              - chris.sharman@ccagroup.co.uk

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-03-01 03:03

Message:
Logged In: YES 
user_id=290026

Strange - I had no problems with MS VC++ 6.0.
Which service pack level have you applied?

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

Comment By: Jacob Levy (jyljyljyl)
Date: 2003-03-01 02:35

Message:
Logged In: YES 
user_id=63723

This makes Expat 1.95.6 unusable for people who create
libraries that depend on Expat but don't include their own
copy of Expat. Sure, I can edit expat.h and fix it, but my
users should not be expected to do that.

For that reason I'm staying with Expat 1.95.5 until this
problem is fixed. It'd be really nice if you could make
Expat 1.95.7 soon..

In my case GCC 2.95.2 and VC++ 6.0 are complaining.


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

Comment By: Melvyn Sopacua (nyvlem)
Date: 2003-02-14 08:56

Message:
Logged In: YES 
user_id=212431

Yes, that works.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-02-06 21:47

Message:
Logged In: YES 
user_id=290026

But current CVS works for you, right?

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

Comment By: Melvyn Sopacua (nyvlem)
Date: 2003-02-06 21:17

Message:
Logged In: YES 
user_id=212431

> So far only gcc3.2 has complained.

Nope:
/usr/local/include/expat.h:657: use of enum `XML_Status' 
without previous declaration
/usr/local/include/expat.h:736: multiple definition of `enum 
XML_Status'
gmake[2]: *** [context.lo] Error 1
gmake[2]: Leaving directory 
`/home/mdev/cvs/sablot/src/engine'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/home/mdev/cvs/sablot/src'
gmake: *** [all-recursive] Error 1

$ gcc --version
2.95.3

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-01-31 15:43

Message:
Logged In: YES 
user_id=290026

It *is* fixed in CVS. Are you sure you checked out the 
right version, which is expat.h 1.51?

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-01-31 11:34

Message:
Logged In: NO 

I just got the same error, already fixed it. But don't 
understand why it isn't fixed in CVS ?

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

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2003-01-29 19:44

Message:
Logged In: YES 
user_id=3066

I've not checked the C89 standard yet, but Expat 1.95.6 is 
certainly dodgy in this case.  ;-(  The first draft of the C spec I 
found online certainly seemed to imply that any use of an 
incomplete enum is not allowed; I'm not likely to go out and 
buy a copy of the final spec to check further.  ;-)

As noted, this has been fixed in CVS.  Fixed the summary to 
better indicate what this report is about, and lowered the 
priority to get it out of the way for maintainers.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-01-29 16:51

Message:
Logged In: YES 
user_id=290026

So far only gcc3.2 has complained.
Not sure if this is a bug, since most compilers accept it,
but it has been fixed in CVS already anyway.

Set resolution status to fixed, but leave open.
There may be other users who would report this as a bug
and I want them to see the open report instead of 
having duplicates created.

Assigned to Fred - since he may know more about
whether this truly is a bug.

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

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

From noreply at sourceforge.net  Thu May  8 07:18:12 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu May  8 09:18:30 2003
Subject: [Expat-bugs] [ expat-Bugs-676844 ] expat.h compile error: enum
	XML_Status
Message-ID: <E19DlHo-0006wc-00@sc8-sf-web1.sourceforge.net>

Bugs item #676844, was opened at 2003-01-29 10:37
Message generated for change (Comment added) made by kwaclaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=676844&group_id=10127

Category: Build control
Group: None
Status: Open
Resolution: Fixed
Priority: 9
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: expat.h compile error: enum XML_Status

Initial Comment:
c++ -DHAVE_CONFIG_H -I. -I. -I../../autocfg -g -O2 -c
context.cpp  -fPIC -DPIC -o .libs/context.lo
In file included from parser.h:45,
                 from guard.h:143,
                 from context.cpp:45:
/usr/include/expat.h:657: use of enum `XML_Status'
without previous declaration
/usr/include/expat.h:736: multiple definition of `enum
XML_Status'


when building sablotron.

Hand editing the file to place the def of enum
XML_Status before any references to it fixes the problem.

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

>Comment By: Karl Waclawek (kwaclaw)
Date: 2003-05-08 09:18

Message:
Logged In: YES 
user_id=290026

See above - original submission:

Hand editing the file to place the def of enum 
XML_Status before any references to it fixes the 
problem.     

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

Comment By: Donche, Pieter (pdon)
Date: 2003-05-08 03:20

Message:
Logged In: YES 
user_id=774177

SUN Sparc Enterprise 2170 Solaris 2.8 
gcc 3.2
Downloaded expat-1.95.6.tar.gz
./configure, make, make install OK
Downloaded Sablot-0.98.tar.gz (Sablotron package,
from www.gingerall.com)
./configure says:
...
checking expat.h presence... yes
expat.h: present but cannot be compiled
expat.h: check for missing prerequisite headers?
expat.h: proceeding with the preprocessor's result
##-------------------------------------------------##
## Report this to bug-autoconf@gnu.org ##
##-------------------------------------------------##
checking for expat.h... yes
checking wether expat.h is broken... yes
error: You probably have expat version 1.95.6. Please refer to
 http://sourceforge.net/tracker/index.php?
func=detail&aid=676844&group_id=10127&atid=110127
for a description of the problem

-- Looked at that web-page. Don't see a solution there.
Wath is the solution ?
Pieter.Donche@ua.ac.be


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

Comment By: Donche, Pieter (pdon)
Date: 2003-05-08 03:20

Message:
Logged In: YES 
user_id=774177

SUN Sparc Enterprise 2170 Solaris 2.8 
gcc 3.2
Downloaded expat-1.95.6.tar.gz
./configure, make, make install OK
Downloaded Sablot-0.98.tar.gz (Sablotron package,
from www.gingerall.com)
./configure says:
...
checking expat.h presence... yes
expat.h: present but cannot be compiled
expat.h: check for missing prerequisite headers?
expat.h: proceeding with the preprocessor's result
##-------------------------------------------------##
## Report this to bug-autoconf@gnu.org ##
##-------------------------------------------------##
checking for expat.h... yes
checking wether expat.h is broken... yes
error: You probably have expat version 1.95.6. Please refer to
 http://sourceforge.net/tracker/index.php?
func=detail&aid=676844&group_id=10127&atid=110127
for a description of the problem

-- Looked at that web-page. Don't see a solution there.
Wath is the solution ?
Pieter.Donche@ua.ac.be


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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-04-16 09:59

Message:
Logged In: YES 
user_id=290026

Changed priority to highest to make it more visible,
so that double reporting incidents occur less frequently.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-03-27 05:42

Message:
Logged In: NO 

Same problem and the same fix under Linux and gcc 2.95.2.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-03-07 06:20

Message:
Logged In: NO 

same problem, same fix when building 1.95.6 on vms
(just downloaded .tar.gz & processed - got the rpm, but
don't know what to do with it - not an archive type I know
how to handle on vms, or windows either)
              - chris.sharman@ccagroup.co.uk

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-02-28 21:03

Message:
Logged In: YES 
user_id=290026

Strange - I had no problems with MS VC++ 6.0.
Which service pack level have you applied?

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

Comment By: Jacob Levy (jyljyljyl)
Date: 2003-02-28 20:35

Message:
Logged In: YES 
user_id=63723

This makes Expat 1.95.6 unusable for people who create
libraries that depend on Expat but don't include their own
copy of Expat. Sure, I can edit expat.h and fix it, but my
users should not be expected to do that.

For that reason I'm staying with Expat 1.95.5 until this
problem is fixed. It'd be really nice if you could make
Expat 1.95.7 soon..

In my case GCC 2.95.2 and VC++ 6.0 are complaining.


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

Comment By: Melvyn Sopacua (nyvlem)
Date: 2003-02-14 02:56

Message:
Logged In: YES 
user_id=212431

Yes, that works.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-02-06 15:47

Message:
Logged In: YES 
user_id=290026

But current CVS works for you, right?

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

Comment By: Melvyn Sopacua (nyvlem)
Date: 2003-02-06 15:17

Message:
Logged In: YES 
user_id=212431

> So far only gcc3.2 has complained.

Nope:
/usr/local/include/expat.h:657: use of enum `XML_Status' 
without previous declaration
/usr/local/include/expat.h:736: multiple definition of `enum 
XML_Status'
gmake[2]: *** [context.lo] Error 1
gmake[2]: Leaving directory 
`/home/mdev/cvs/sablot/src/engine'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/home/mdev/cvs/sablot/src'
gmake: *** [all-recursive] Error 1

$ gcc --version
2.95.3

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-01-31 09:43

Message:
Logged In: YES 
user_id=290026

It *is* fixed in CVS. Are you sure you checked out the 
right version, which is expat.h 1.51?

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-01-31 05:34

Message:
Logged In: NO 

I just got the same error, already fixed it. But don't 
understand why it isn't fixed in CVS ?

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

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2003-01-29 13:44

Message:
Logged In: YES 
user_id=3066

I've not checked the C89 standard yet, but Expat 1.95.6 is 
certainly dodgy in this case.  ;-(  The first draft of the C spec I 
found online certainly seemed to imply that any use of an 
incomplete enum is not allowed; I'm not likely to go out and 
buy a copy of the final spec to check further.  ;-)

As noted, this has been fixed in CVS.  Fixed the summary to 
better indicate what this report is about, and lowered the 
priority to get it out of the way for maintainers.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-01-29 10:51

Message:
Logged In: YES 
user_id=290026

So far only gcc3.2 has complained.
Not sure if this is a bug, since most compilers accept it,
but it has been fixed in CVS already anyway.

Set resolution status to fixed, but leave open.
There may be other users who would report this as a bug
and I want them to see the open report instead of 
having duplicates created.

Assigned to Fred - since he may know more about
whether this truly is a bug.

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

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

From christian.ferrari at primeur.com  Fri May  9 18:28:30 2003
From: christian.ferrari at primeur.com (Christian Ferrari)
Date: Fri May  9 14:19:24 2003
Subject: [Expat-bugs] Little bug fix in expat-1.95.6
Message-ID: <3EBBC91E.7030304@primeur.com>

The supplied "conftools/expat.m4" sets

EXPAT_CFLAGS="-I$with_expat/include"
CFLAGS="$CFLAGS $EXPAT_CFLAGS"

before
AC_CHECK_HEADERS(expat.h, , expat_found=no)

on some systems (for example "i686-pc-linux-gnu", "gcc 2.96") it may be 
broken (the bug exploits during "checking expat.h presence" where 
preprocessor is used and CFLAGS {-I/mypath/expat} are not passed to 
command).

The attached version addresses this little bug.

Regards
Christian

-- 
______________________________________

Christian Ferrari
c/o PRIMEUR ITALIA
Via E. Mattei, 1/106 A
30020 Marcon (VE) - ITALY

Tel.:    +39 041 5950998
Fax:     +39 041 5951024
Mobile:  +39 348 8960572
E-mail:  Christian.Ferrari@primeur.com
Web:     http://www.primeur.com/
-------------- next part --------------
dnl Check if --with-expat[=PREFIX] is specified and
dnl Expat >= 1.95.0 is installed in the system.
dnl If yes, substitute EXPAT_CPPFLAGS, EXPAT_LIBS with regard to
dnl the specified PREFIX and set with_expat to PREFIX, or 'yes' if PREFIX
dnl has not been specified. Also HAVE_LIBEXPAT, HAVE_EXPAT_H are defined.
dnl If --with-expat has not been specified, set with_expat to 'no'.
dnl In addition, an Automake conditional EXPAT_INSTALLED is set accordingly.
dnl This is necessary to adapt a whole lot of packages that have expat
dnl bundled as a static library.
AC_DEFUN(AM_WITH_EXPAT,
[ AC_ARG_WITH(expat,
	      [  --with-expat=PREFIX     Use system Expat library],
	      , with_expat=no)

  AM_CONDITIONAL(EXPAT_INSTALLED, test $with_expat != no)

  EXPAT_CPPFLAGS=
  EXPAT_LIBS=
  if test $with_expat != no; then
	if test $with_expat != yes; then
		EXPAT_CPPFLAGS="-I$with_expat/include"
		EXPAT_LIBS="-L$with_expat/lib"
	fi
	AC_CHECK_LIB(expat, XML_ParserCreate,
		     [ EXPAT_LIBS="$EXPAT_LIBS -lexpat"
		       expat_found=yes ],
		     [ expat_found=no ],
		     "$EXPAT_LIBS")
	if test $expat_found = no; then
		AC_MSG_ERROR([Could not find the Expat library])
	fi
	expat_save_CPPFLAGS="$CPPFLAGS"
	CPPFLAGS="$CPPFLAGS $EXPAT_CPPFLAGS"
	AC_CHECK_HEADERS(expat.h, , expat_found=no)
	if test $expat_found = no; then
		AC_MSG_ERROR([Could not find expat.h])
	fi
	CPPFLAGS="$expat_save_CPPFLAGS"
  fi

  AC_SUBST(EXPAT_CPPFLAGS)
  AC_SUBST(EXPAT_LIBS)
])
From noreply at sourceforge.net  Wed May 14 03:47:17 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed May 14 05:47:22 2003
Subject: [Expat-bugs] [ expat-Bugs-737590 ] Expat 1.95.6 for Windows - How
	to use
Message-ID: <E19Fsqz-0007tD-00@sc8-sf-web1.sourceforge.net>

Bugs item #737590, was opened at 2003-05-14 02:47
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=737590&group_id=10127

Category: None
Group: Not a Bug
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Expat 1.95.6 for Windows - How to use

Initial Comment:
I am a student not familiar to the procedure of making 
non standard libraries available to Visual C++ .NET.

I have downloaded the above including the static lib.

But where and how exactly do I have to tell my Linker 
where to look for these files?? Or do I have to copy them 
anywhere?
 
Currently I get the following message (and several others 
looking similar):

test error LNK2001: unresolved external symbol "void 
__cdecl XML_SetCharacterDataHandler(struct 
XML_ParserStruct *,void (__cdecl*)(void *,char const 
*,int))" (?
XML_SetCharacterDataHandler@@$$J0YAXPAUXML_P
arserStruct@@P6AXPAXPBDH@Z@Z)

The sentence "build and install in the usual manner" 
from the reference isnīt helpful to me.

So what is the usual manner???

Thanks a lot
Werner Gerstmayr
Germany



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

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

From chr020 at email.mot.com  Thu May 15 15:15:17 2003
From: chr020 at email.mot.com (Rose Ran)
Date: Thu May 15 15:18:50 2003
Subject: [Expat-bugs] Regarding expat in VXWORKS
Message-ID: <3EC3E745.C7FA8C12@email.mot.com>

Hello,

I downloaded the expat libs from the website. I used the functions
"XML_SetElementHandler" and
"XML_Parse" to parse my xml file. These codes worked very well when I
ran it in solaris. However
when I ran the same codes in "VXWORKS", it always only parsed the xml
file "Header" part,
and exited after that. The body part of "xml" can't get parsed any way.
Is any idea what could
cause this?

Thanks a lot for your help!

Rose


From noreply at sourceforge.net  Thu May 15 13:39:57 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu May 15 15:40:04 2003
Subject: [Expat-bugs] [ expat-Bugs-737590 ] Expat 1.95.6 for Windows - How
	to use
Message-ID: <E19GOa5-0002CP-00@sc8-sf-web4.sourceforge.net>

Bugs item #737590, was opened at 2003-05-14 05:47
Message generated for change (Comment added) made by kwaclaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=737590&group_id=10127

Category: None
Group: Not a Bug
>Status: Closed
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Expat 1.95.6 for Windows - How to use

Initial Comment:
I am a student not familiar to the procedure of making 
non standard libraries available to Visual C++ .NET.

I have downloaded the above including the static lib.

But where and how exactly do I have to tell my Linker 
where to look for these files?? Or do I have to copy them 
anywhere?
 
Currently I get the following message (and several others 
looking similar):

test error LNK2001: unresolved external symbol "void 
__cdecl XML_SetCharacterDataHandler(struct 
XML_ParserStruct *,void (__cdecl*)(void *,char const 
*,int))" (?
XML_SetCharacterDataHandler@@$$J0YAXPAUXML_P
arserStruct@@P6AXPAXPBDH@Z@Z)

The sentence "build and install in the usual manner" 
from the reference isnīt helpful to me.

So what is the usual manner???

Thanks a lot
Werner Gerstmayr
Germany



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

>Comment By: Karl Waclawek (kwaclaw)
Date: 2003-05-15 15:39

Message:
Logged In: YES 
user_id=290026

Currently we do not have anyone on the team using
VC++.NET. However, the Expat source distribution
comes with a .dsw file for VC++ 6.0. So, if you know 
how to use VC++ 6.0 then it should be no problem for
you to open the workspace and study the sample 
projects.

I suppose that Microsoft provides documentation on 
how to migrate from VC++ 6.0 to the new .NET 
compiler. 

Since this is not a bug or feature request, I am closing 
this report. Please direct further inquiries to
expat-discuss@libexpat.org (mailing list).


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

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

From noreply at sourceforge.net  Thu May 15 14:26:45 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu May 15 16:26:49 2003
Subject: [Expat-bugs] [ expat-Bugs-737590 ] Expat 1.95.6 for Windows - How
	to use
Message-ID: <E19GPJN-0004R6-00@sc8-sf-web4.sourceforge.net>

Bugs item #737590, was opened at 2003-05-14 02:47
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=737590&group_id=10127

Category: None
Group: Not a Bug
Status: Closed
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Expat 1.95.6 for Windows - How to use

Initial Comment:
I am a student not familiar to the procedure of making 
non standard libraries available to Visual C++ .NET.

I have downloaded the above including the static lib.

But where and how exactly do I have to tell my Linker 
where to look for these files?? Or do I have to copy them 
anywhere?
 
Currently I get the following message (and several others 
looking similar):

test error LNK2001: unresolved external symbol "void 
__cdecl XML_SetCharacterDataHandler(struct 
XML_ParserStruct *,void (__cdecl*)(void *,char const 
*,int))" (?
XML_SetCharacterDataHandler@@$$J0YAXPAUXML_P
arserStruct@@P6AXPAXPBDH@Z@Z)

The sentence "build and install in the usual manner" 
from the reference isnīt helpful to me.

So what is the usual manner???

Thanks a lot
Werner Gerstmayr
Germany



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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-05-15 13:26

Message:
Logged In: NO 

Yes, the VC++7 opens and knows how to compile .dsws and
.dsps. However, if Werner uses compiled version of library -
here's what could be done:
1. In the "Solution Explorer" or "Class View" pane you
right-click the name of project you want to add expat to
2. Choose "Properties"
3. Under "Configuration Properties" you choose "Linker" and
then "Input" branches
4. In "Additional Dependecies" place name of .lib file you
want to add
5. OK-close Property Pages dialog
6. If it is needed to point out the directory expat's .lib
resides, open Tools > Options menu
7. Choose branches "Projects" > "VC++ Directories"
8. In "Show directories for:" choose either "Include files"
(to point at the directory, where you installed includes) or
"Library files" (to point... well, you know what :) )
9. Add directory name as you would in VC++6
10. Voila!

Another thing is that using two different .libs for either
static or dynamic linkage of expat is simply not enought -
there is also one #define (or /D) issue to workout in your
project file.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-05-15 12:39

Message:
Logged In: YES 
user_id=290026

Currently we do not have anyone on the team using
VC++.NET. However, the Expat source distribution
comes with a .dsw file for VC++ 6.0. So, if you know 
how to use VC++ 6.0 then it should be no problem for
you to open the workspace and study the sample 
projects.

I suppose that Microsoft provides documentation on 
how to migrate from VC++ 6.0 to the new .NET 
compiler. 

Since this is not a bug or feature request, I am closing 
this report. Please direct further inquiries to
expat-discuss@libexpat.org (mailing list).


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

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

From noreply at sourceforge.net  Thu May 15 14:50:30 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu May 15 16:50:33 2003
Subject: [Expat-bugs] [ expat-Bugs-737590 ] Expat 1.95.6 for Windows - How
	to use
Message-ID: <E19GPgM-0006AI-00@sc8-sf-web2.sourceforge.net>

Bugs item #737590, was opened at 2003-05-14 05:47
Message generated for change (Comment added) made by kwaclaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=737590&group_id=10127

Category: None
Group: Not a Bug
Status: Closed
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Expat 1.95.6 for Windows - How to use

Initial Comment:
I am a student not familiar to the procedure of making 
non standard libraries available to Visual C++ .NET.

I have downloaded the above including the static lib.

But where and how exactly do I have to tell my Linker 
where to look for these files?? Or do I have to copy them 
anywhere?
 
Currently I get the following message (and several others 
looking similar):

test error LNK2001: unresolved external symbol "void 
__cdecl XML_SetCharacterDataHandler(struct 
XML_ParserStruct *,void (__cdecl*)(void *,char const 
*,int))" (?
XML_SetCharacterDataHandler@@$$J0YAXPAUXML_P
arserStruct@@P6AXPAXPBDH@Z@Z)

The sentence "build and install in the usual manner" 
from the reference isnīt helpful to me.

So what is the usual manner???

Thanks a lot
Werner Gerstmayr
Germany



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

>Comment By: Karl Waclawek (kwaclaw)
Date: 2003-05-15 16:50

Message:
Logged In: YES 
user_id=290026

Thanks for providing us with VC++.NET information.

The use of the XML_STATIC define for static linking
is documented in the Win32/ReadMe.txt file and
also demonstrated in the "elements" example project.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-05-15 16:26

Message:
Logged In: NO 

Yes, the VC++7 opens and knows how to compile .dsws and
.dsps. However, if Werner uses compiled version of library -
here's what could be done:
1. In the "Solution Explorer" or "Class View" pane you
right-click the name of project you want to add expat to
2. Choose "Properties"
3. Under "Configuration Properties" you choose "Linker" and
then "Input" branches
4. In "Additional Dependecies" place name of .lib file you
want to add
5. OK-close Property Pages dialog
6. If it is needed to point out the directory expat's .lib
resides, open Tools > Options menu
7. Choose branches "Projects" > "VC++ Directories"
8. In "Show directories for:" choose either "Include files"
(to point at the directory, where you installed includes) or
"Library files" (to point... well, you know what :) )
9. Add directory name as you would in VC++6
10. Voila!

Another thing is that using two different .libs for either
static or dynamic linkage of expat is simply not enought -
there is also one #define (or /D) issue to workout in your
project file.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-05-15 15:39

Message:
Logged In: YES 
user_id=290026

Currently we do not have anyone on the team using
VC++.NET. However, the Expat source distribution
comes with a .dsw file for VC++ 6.0. So, if you know 
how to use VC++ 6.0 then it should be no problem for
you to open the workspace and study the sample 
projects.

I suppose that Microsoft provides documentation on 
how to migrate from VC++ 6.0 to the new .NET 
compiler. 

Since this is not a bug or feature request, I am closing 
this report. Please direct further inquiries to
expat-discuss@libexpat.org (mailing list).


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

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

From noreply at sourceforge.net  Fri May 30 14:26:02 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri May 30 16:26:32 2003
Subject: [Expat-bugs] [ expat-Bugs-676844 ] expat.h compile error: enum
	XML_Status
Message-ID: <E19LqRu-0000vv-00@sc8-sf-web3.sourceforge.net>

Bugs item #676844, was opened at 2003-01-29 07:37
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=676844&group_id=10127

Category: Build control
Group: None
Status: Open
Resolution: Fixed
Priority: 9
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: expat.h compile error: enum XML_Status

Initial Comment:
c++ -DHAVE_CONFIG_H -I. -I. -I../../autocfg -g -O2 -c
context.cpp  -fPIC -DPIC -o .libs/context.lo
In file included from parser.h:45,
                 from guard.h:143,
                 from context.cpp:45:
/usr/include/expat.h:657: use of enum `XML_Status'
without previous declaration
/usr/include/expat.h:736: multiple definition of `enum
XML_Status'


when building sablotron.

Hand editing the file to place the def of enum
XML_Status before any references to it fixes the problem.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-05-30 13:26

Message:
Logged In: NO 

I have the same problem has other senders, but the fix is
unclear as you did not indicate which file needs fixing (I
assume expat.h) or line number  to place the def of enum
XML_Status.  Please assume people are stupid..

checking expat.h usability... no
checking expat.h presence... yes
configure: WARNING: expat.h: present but cannot be compiled
configure: WARNING: expat.h: check for missing prerequisite
headers?
configure: WARNING: expat.h: proceeding with the
preprocessor's result
configure: WARNING:     ##
------------------------------------ ##
configure: WARNING:     ## Report this to
bug-autoconf@gnu.org. ##
configure: WARNING:     ##
------------------------------------ ##
checking for expat.h... yes
checking whether expat.h is broken... yes
configure: error: You probably have expat version 1.95.6.
Please refer to:
 
http://sourceforge.net/tracker/index.php?func=detail&aid=676844&group_id=10127&atid=110127
  for a description of the problem.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-05-08 06:18

Message:
Logged In: YES 
user_id=290026

See above - original submission:

Hand editing the file to place the def of enum 
XML_Status before any references to it fixes the 
problem.     

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

Comment By: Donche, Pieter (pdon)
Date: 2003-05-08 00:20

Message:
Logged In: YES 
user_id=774177

SUN Sparc Enterprise 2170 Solaris 2.8 
gcc 3.2
Downloaded expat-1.95.6.tar.gz
./configure, make, make install OK
Downloaded Sablot-0.98.tar.gz (Sablotron package,
from www.gingerall.com)
./configure says:
...
checking expat.h presence... yes
expat.h: present but cannot be compiled
expat.h: check for missing prerequisite headers?
expat.h: proceeding with the preprocessor's result
##-------------------------------------------------##
## Report this to bug-autoconf@gnu.org ##
##-------------------------------------------------##
checking for expat.h... yes
checking wether expat.h is broken... yes
error: You probably have expat version 1.95.6. Please refer to
 http://sourceforge.net/tracker/index.php?
func=detail&aid=676844&group_id=10127&atid=110127
for a description of the problem

-- Looked at that web-page. Don't see a solution there.
Wath is the solution ?
Pieter.Donche@ua.ac.be


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

Comment By: Donche, Pieter (pdon)
Date: 2003-05-08 00:20

Message:
Logged In: YES 
user_id=774177

SUN Sparc Enterprise 2170 Solaris 2.8 
gcc 3.2
Downloaded expat-1.95.6.tar.gz
./configure, make, make install OK
Downloaded Sablot-0.98.tar.gz (Sablotron package,
from www.gingerall.com)
./configure says:
...
checking expat.h presence... yes
expat.h: present but cannot be compiled
expat.h: check for missing prerequisite headers?
expat.h: proceeding with the preprocessor's result
##-------------------------------------------------##
## Report this to bug-autoconf@gnu.org ##
##-------------------------------------------------##
checking for expat.h... yes
checking wether expat.h is broken... yes
error: You probably have expat version 1.95.6. Please refer to
 http://sourceforge.net/tracker/index.php?
func=detail&aid=676844&group_id=10127&atid=110127
for a description of the problem

-- Looked at that web-page. Don't see a solution there.
Wath is the solution ?
Pieter.Donche@ua.ac.be


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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-04-16 06:59

Message:
Logged In: YES 
user_id=290026

Changed priority to highest to make it more visible,
so that double reporting incidents occur less frequently.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-03-27 02:42

Message:
Logged In: NO 

Same problem and the same fix under Linux and gcc 2.95.2.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-03-07 03:20

Message:
Logged In: NO 

same problem, same fix when building 1.95.6 on vms
(just downloaded .tar.gz & processed - got the rpm, but
don't know what to do with it - not an archive type I know
how to handle on vms, or windows either)
              - chris.sharman@ccagroup.co.uk

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-02-28 18:03

Message:
Logged In: YES 
user_id=290026

Strange - I had no problems with MS VC++ 6.0.
Which service pack level have you applied?

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

Comment By: Jacob Levy (jyljyljyl)
Date: 2003-02-28 17:35

Message:
Logged In: YES 
user_id=63723

This makes Expat 1.95.6 unusable for people who create
libraries that depend on Expat but don't include their own
copy of Expat. Sure, I can edit expat.h and fix it, but my
users should not be expected to do that.

For that reason I'm staying with Expat 1.95.5 until this
problem is fixed. It'd be really nice if you could make
Expat 1.95.7 soon..

In my case GCC 2.95.2 and VC++ 6.0 are complaining.


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

Comment By: Melvyn Sopacua (nyvlem)
Date: 2003-02-13 23:56

Message:
Logged In: YES 
user_id=212431

Yes, that works.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-02-06 12:47

Message:
Logged In: YES 
user_id=290026

But current CVS works for you, right?

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

Comment By: Melvyn Sopacua (nyvlem)
Date: 2003-02-06 12:17

Message:
Logged In: YES 
user_id=212431

> So far only gcc3.2 has complained.

Nope:
/usr/local/include/expat.h:657: use of enum `XML_Status' 
without previous declaration
/usr/local/include/expat.h:736: multiple definition of `enum 
XML_Status'
gmake[2]: *** [context.lo] Error 1
gmake[2]: Leaving directory 
`/home/mdev/cvs/sablot/src/engine'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/home/mdev/cvs/sablot/src'
gmake: *** [all-recursive] Error 1

$ gcc --version
2.95.3

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-01-31 06:43

Message:
Logged In: YES 
user_id=290026

It *is* fixed in CVS. Are you sure you checked out the 
right version, which is expat.h 1.51?

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-01-31 02:34

Message:
Logged In: NO 

I just got the same error, already fixed it. But don't 
understand why it isn't fixed in CVS ?

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

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2003-01-29 10:44

Message:
Logged In: YES 
user_id=3066

I've not checked the C89 standard yet, but Expat 1.95.6 is 
certainly dodgy in this case.  ;-(  The first draft of the C spec I 
found online certainly seemed to imply that any use of an 
incomplete enum is not allowed; I'm not likely to go out and 
buy a copy of the final spec to check further.  ;-)

As noted, this has been fixed in CVS.  Fixed the summary to 
better indicate what this report is about, and lowered the 
priority to get it out of the way for maintainers.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-01-29 07:51

Message:
Logged In: YES 
user_id=290026

So far only gcc3.2 has complained.
Not sure if this is a bug, since most compilers accept it,
but it has been fixed in CVS already anyway.

Set resolution status to fixed, but leave open.
There may be other users who would report this as a bug
and I want them to see the open report instead of 
having duplicates created.

Assigned to Fred - since he may know more about
whether this truly is a bug.

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

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

From noreply at sourceforge.net  Fri May 30 14:47:17 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri May 30 16:47:49 2003
Subject: [Expat-bugs] [ expat-Bugs-676844 ] expat.h compile error: enum
	XML_Status
Message-ID: <E19LqmT-0003vf-00@sc8-sf-web1.sourceforge.net>

Bugs item #676844, was opened at 2003-01-29 10:37
Message generated for change (Comment added) made by kwaclaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=676844&group_id=10127

Category: Build control
Group: None
Status: Open
Resolution: Fixed
Priority: 9
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: expat.h compile error: enum XML_Status

Initial Comment:
c++ -DHAVE_CONFIG_H -I. -I. -I../../autocfg -g -O2 -c
context.cpp  -fPIC -DPIC -o .libs/context.lo
In file included from parser.h:45,
                 from guard.h:143,
                 from context.cpp:45:
/usr/include/expat.h:657: use of enum `XML_Status'
without previous declaration
/usr/include/expat.h:736: multiple definition of `enum
XML_Status'


when building sablotron.

Hand editing the file to place the def of enum
XML_Status before any references to it fixes the problem.

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

>Comment By: Karl Waclawek (kwaclaw)
Date: 2003-05-30 16:47

Message:
Logged In: YES 
user_id=290026

Yes, the file to fix is expat.h.

Two things you can do:

1) get the latest expat.h from CVS, or

2) use your editor to search expat.h for the first
    location where XML_STATUS is used and then
    move the definition of XML_STATUS to some
    location before that point.


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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-05-30 16:26

Message:
Logged In: NO 

I have the same problem has other senders, but the fix is
unclear as you did not indicate which file needs fixing (I
assume expat.h) or line number  to place the def of enum
XML_Status.  Please assume people are stupid..

checking expat.h usability... no
checking expat.h presence... yes
configure: WARNING: expat.h: present but cannot be compiled
configure: WARNING: expat.h: check for missing prerequisite
headers?
configure: WARNING: expat.h: proceeding with the
preprocessor's result
configure: WARNING:     ##
------------------------------------ ##
configure: WARNING:     ## Report this to
bug-autoconf@gnu.org. ##
configure: WARNING:     ##
------------------------------------ ##
checking for expat.h... yes
checking whether expat.h is broken... yes
configure: error: You probably have expat version 1.95.6.
Please refer to:
 
http://sourceforge.net/tracker/index.php?func=detail&aid=676844&group_id=10127&atid=110127
  for a description of the problem.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-05-08 09:18

Message:
Logged In: YES 
user_id=290026

See above - original submission:

Hand editing the file to place the def of enum 
XML_Status before any references to it fixes the 
problem.     

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

Comment By: Donche, Pieter (pdon)
Date: 2003-05-08 03:20

Message:
Logged In: YES 
user_id=774177

SUN Sparc Enterprise 2170 Solaris 2.8 
gcc 3.2
Downloaded expat-1.95.6.tar.gz
./configure, make, make install OK
Downloaded Sablot-0.98.tar.gz (Sablotron package,
from www.gingerall.com)
./configure says:
...
checking expat.h presence... yes
expat.h: present but cannot be compiled
expat.h: check for missing prerequisite headers?
expat.h: proceeding with the preprocessor's result
##-------------------------------------------------##
## Report this to bug-autoconf@gnu.org ##
##-------------------------------------------------##
checking for expat.h... yes
checking wether expat.h is broken... yes
error: You probably have expat version 1.95.6. Please refer to
 http://sourceforge.net/tracker/index.php?
func=detail&aid=676844&group_id=10127&atid=110127
for a description of the problem

-- Looked at that web-page. Don't see a solution there.
Wath is the solution ?
Pieter.Donche@ua.ac.be


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

Comment By: Donche, Pieter (pdon)
Date: 2003-05-08 03:20

Message:
Logged In: YES 
user_id=774177

SUN Sparc Enterprise 2170 Solaris 2.8 
gcc 3.2
Downloaded expat-1.95.6.tar.gz
./configure, make, make install OK
Downloaded Sablot-0.98.tar.gz (Sablotron package,
from www.gingerall.com)
./configure says:
...
checking expat.h presence... yes
expat.h: present but cannot be compiled
expat.h: check for missing prerequisite headers?
expat.h: proceeding with the preprocessor's result
##-------------------------------------------------##
## Report this to bug-autoconf@gnu.org ##
##-------------------------------------------------##
checking for expat.h... yes
checking wether expat.h is broken... yes
error: You probably have expat version 1.95.6. Please refer to
 http://sourceforge.net/tracker/index.php?
func=detail&aid=676844&group_id=10127&atid=110127
for a description of the problem

-- Looked at that web-page. Don't see a solution there.
Wath is the solution ?
Pieter.Donche@ua.ac.be


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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-04-16 09:59

Message:
Logged In: YES 
user_id=290026

Changed priority to highest to make it more visible,
so that double reporting incidents occur less frequently.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-03-27 05:42

Message:
Logged In: NO 

Same problem and the same fix under Linux and gcc 2.95.2.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-03-07 06:20

Message:
Logged In: NO 

same problem, same fix when building 1.95.6 on vms
(just downloaded .tar.gz & processed - got the rpm, but
don't know what to do with it - not an archive type I know
how to handle on vms, or windows either)
              - chris.sharman@ccagroup.co.uk

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-02-28 21:03

Message:
Logged In: YES 
user_id=290026

Strange - I had no problems with MS VC++ 6.0.
Which service pack level have you applied?

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

Comment By: Jacob Levy (jyljyljyl)
Date: 2003-02-28 20:35

Message:
Logged In: YES 
user_id=63723

This makes Expat 1.95.6 unusable for people who create
libraries that depend on Expat but don't include their own
copy of Expat. Sure, I can edit expat.h and fix it, but my
users should not be expected to do that.

For that reason I'm staying with Expat 1.95.5 until this
problem is fixed. It'd be really nice if you could make
Expat 1.95.7 soon..

In my case GCC 2.95.2 and VC++ 6.0 are complaining.


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

Comment By: Melvyn Sopacua (nyvlem)
Date: 2003-02-14 02:56

Message:
Logged In: YES 
user_id=212431

Yes, that works.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-02-06 15:47

Message:
Logged In: YES 
user_id=290026

But current CVS works for you, right?

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

Comment By: Melvyn Sopacua (nyvlem)
Date: 2003-02-06 15:17

Message:
Logged In: YES 
user_id=212431

> So far only gcc3.2 has complained.

Nope:
/usr/local/include/expat.h:657: use of enum `XML_Status' 
without previous declaration
/usr/local/include/expat.h:736: multiple definition of `enum 
XML_Status'
gmake[2]: *** [context.lo] Error 1
gmake[2]: Leaving directory 
`/home/mdev/cvs/sablot/src/engine'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/home/mdev/cvs/sablot/src'
gmake: *** [all-recursive] Error 1

$ gcc --version
2.95.3

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-01-31 09:43

Message:
Logged In: YES 
user_id=290026

It *is* fixed in CVS. Are you sure you checked out the 
right version, which is expat.h 1.51?

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

Comment By: Nobody/Anonymous (nobody)
Date: 2003-01-31 05:34

Message:
Logged In: NO 

I just got the same error, already fixed it. But don't 
understand why it isn't fixed in CVS ?

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

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2003-01-29 13:44

Message:
Logged In: YES 
user_id=3066

I've not checked the C89 standard yet, but Expat 1.95.6 is 
certainly dodgy in this case.  ;-(  The first draft of the C spec I 
found online certainly seemed to imply that any use of an 
incomplete enum is not allowed; I'm not likely to go out and 
buy a copy of the final spec to check further.  ;-)

As noted, this has been fixed in CVS.  Fixed the summary to 
better indicate what this report is about, and lowered the 
priority to get it out of the way for maintainers.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-01-29 10:51

Message:
Logged In: YES 
user_id=290026

So far only gcc3.2 has complained.
Not sure if this is a bug, since most compilers accept it,
but it has been fixed in CVS already anyway.

Set resolution status to fixed, but leave open.
There may be other users who would report this as a bug
and I want them to see the open report instead of 
having duplicates created.

Assigned to Fred - since he may know more about
whether this truly is a bug.

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

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

From noreply at sourceforge.net  Fri May 30 14:54:13 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri May 30 16:54:23 2003
Subject: [Expat-bugs] [ expat-Bugs-707469 ] external param entities
Message-ID: <E19LqtB-00027W-00@sc8-sf-web3.sourceforge.net>

Bugs item #707469, was opened at 2003-03-21 07:51
Message generated for change (Comment added) made by kwaclaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=707469&group_id=10127

Category: None
Group: None
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Pavel Hlavnicka (pavel_hlavnicka)
Assigned to: Nobody/Anonymous (nobody)
Summary: external param entities

Initial Comment:

Hi all,
perhaps, this is not a bug, perhaps it is. Give me some
explanation in the first case, please.

1) look at the example
2) It happens with 1.95.5 and 1.95.4 at least

We use expat in sablotron xslt processor. We do support
external entity parsing, and in addition we allow users
to tell, whether they want to parse public external
entities or not. In such a case we just return 1 from
our entity reference handler. (No entity parser is
created).

It results to a strange behavior, if following scenario
happens:

- the parsed document contains <!DOCTYPE blabla SYSTEM
"file.dtd">

- file.dtd contains the declaration of external public
parameter entity

- file.dtd references this entity

- file dtd defines other entities

This is sample file.dtd:
<!ENTITY % foo PUBLIC "xxx cvv" "data-e.dtd">
%foo;

<!ENTITY % baz "baz">
<!ENTITY % bar "somedata">
<!ENTITY %baz; "%bar;">

If %foo; is not referenced, all works fine, and &baz;
means "somedata". If %foo; is referenced, an error
occurs while parsing <!ENTITY %baz; "%bar;">, it seems,
that the entity expansion of %baz; and %bar; is empty.
If I replace <!ENTITY %baz; "%bar;"> with <!ENTITY baz
"%bar;"> paring goes fine, but &baz; points to an empty
string.

I played with a debugger a bit, and what I found was,
that if entity parser is not created in entity ref.
handler. dtd.paramEntityRead is not set to true, and
dtd.keepProcessing is set to false consequently. I'm
not sure, what the mission of dtd.keepProcessing is,
but it seems, that it stays valid a bit longer then
needed. Or do you really mean, that the whole file.dtd
content should be skipped, if the %foo; reference was
not resolved? If so, why I can see the compilation error?

Thank you very much and thanks for expat.


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

>Comment By: Karl Waclawek (kwaclaw)
Date: 2003-05-30 16:54

Message:
Logged In: YES 
user_id=290026

Closed issue, since no more arguments were brought
forward in favour of declaring this a bug.

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

Comment By: Pavel Hlavnicka (pavel_hlavnicka)
Date: 2003-03-24 09:20

Message:
Logged In: YES 
user_id=302801

OK, I do believe you :) This issue is too esoteric for me, I
hardly can tell you more points. Thanks again. I think, the
spec. is pretty confusing on DTD's etc. and the usability is
quite another question... but this is farly out of scope...

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-03-24 09:08

Message:
Logged In: YES 
user_id=290026

As it currentlyt stands I think Expat is right.
We have re-vamped exactly these parts of Expat in the
not so distant past, and it behaves as designed.

Now, this is not to say we could be wrong, but so far
I have not seen any argument or section in the specs 
that would convince me otherwise.

Btw, Expat has a high degree of conformance with the
XML-test-suite, which has been one of our goals
for the past few releases. There is a dicsussion of the
test results in bug #569461.



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

Comment By: Pavel Hlavnicka (pavel_hlavnicka)
Date: 2003-03-24 06:15

Message:
Logged In: YES 
user_id=302801

In the fact, I' don not really depend on this. People using
sablotron reported this behavior, and I do not need to solve
this problem once knowing it is an expat feature. 

Just note, that other processors went trough this data
smoothly (basically Java parsers).

It's your call, whether you tell it's ok or not :) Anyway,
thank you very much for all your explanations.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-03-21 11:34

Message:
Logged In: YES 
user_id=290026

The last line is processed because Expat checks it
for well-formedness. What "processed" means is 
defined in section 5.1:

<quote>
Definition: While they are not required to check the 
document for validity, they are required to process all 
the declarations they read in the internal DTD subset 
and in any parameter entity that they read, up to the 
first reference to a parameter entity that they do not 
read; that is to say, they must use the information in 
those declarations to normalize attribute values, include 
the replacement text of internal entities, and supply 
default attribute values.
</quote>

Now, check the excerpt from 5.1 that I quoted in my 
first reply.

IMO, this implies that the declaration is read and 
checked for well-formedness, but its information
is *not* used for normalizing attribute values, including 
the replacement text of internal entities, and supplying 
default attribute values

Maybe you could also ask this question on the xml-dev
mailing list.

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

Comment By: Pavel Hlavnicka (pavel_hlavnicka)
Date: 2003-03-21 11:23

Message:
Logged In: YES 
user_id=302801

Hard to tell. Another question is, why the last line (entity
declariation) is even processed. It should be skipped at
all, or not?

I can understand, that it could be a hrad job. As I looked
into the expat code, it seems, that the parsing is just
ignoring any output, but anything else works as usually.
Perhaps if DTD is not processed (dtd.keepProcessing ==
FALSE) you could expand any entity reference to some fake
value. It looks like a dirty solution, indeed.

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-03-21 11:09

Message:
Logged In: YES 
user_id=290026

As far as I can tell, the last line in data.dtd has
a reference to an undeclared entity (since the
corresponding declaration was ignored). That alone
is legal for non-validating processors - see
http://www.w3.org/TR/REC-xml#wf-entdeclared,
but the entity declaration itself would then become
mal-formed.

I think that section 5.1 does not mean that
non-processed entities are allowed to be mal-formed. 

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

Comment By: Pavel Hlavnicka (pavel_hlavnicka)
Date: 2003-03-21 09:36

Message:
Logged In: YES 
user_id=302801

Ok, makes sense, actually I've get lost reading this parts
of XML spec. 

But anyway... why the error is reported? If I understand
well,  all following entities should be ignored, but the
error is reported. (for ATTLIST is is the same).

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

Comment By: Karl Waclawek (kwaclaw)
Date: 2003-03-21 09:25

Message:
Logged In: YES 
user_id=290026

This has to do with section 5.1 of the spec
(http://www.w3.org/TR/REC-xml#proc-types):

<excerpt>
Except when standalone="yes", they must not process 
entity declarations or attribute-list declarations 
encountered after a reference to a parameter entity that 
is not read, since the entity may have contained 
overriding declarations.
</excerpt>

So, once %foo is not resolved/read, Expat must
not process any more entity and attribute declarations
in file.dtd. Try it again with standalone="yes".


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

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