After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 353703 - Configure script on Zos does not work.
Configure script on Zos does not work.
Status: RESOLVED NOTGNOME
Product: libxml2
Classification: Platform
Component: general
2.4.29
Other All
: Normal normal
: ---
Assigned To: Daniel Veillard
libxml QA maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-31 16:48 UTC by Wendell Nichols
Modified: 2017-06-14 12:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Wendell Nichols 2006-08-31 16:48:44 UTC
Please describe the problem:
checking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.


Steps to reproduce:
1. just type configure.
2. 
3. 


Actual results:
I get:
configure: error: C++ preprocessor "/lib/cpp" fails sanity check

Expected results:
It should build the makefiles.  The doc says system 390/zos is supported and most of the configure script works... 

Does this happen every time?
yes

Other information:
I realize that you probably dont' have a zos system to test this on but if you can suggest ways that I can find out what is going on here or even remvove the C++ bindings altogether as I dont' need them.  

The last bit of my config.log:
am__untar='${AMTAR} xf -'
bindir='${exec_prefix}/bin'
build='i370-ibm-openedition'
build_alias=''
build_cpu='i370'
build_os='openedition'
build_vendor='ibm'
datadir='${prefix}/share'
exec_prefix='NONE'
host='i370-ibm-openedition'
host_alias=''
host_cpu='i370'
host_os='openedition'
host_vendor='ibm'
includedir='${prefix}/include'
infodir='${prefix}/info'
install_sh='/tib/perl/libxml2-2.6.26/install-sh'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localstatedir='${prefix}/var'
mandir='${prefix}/man'
mkdir_p='$(mkinstalldirs)'
oldincludedir='/usr/include'
prefix='NONE'
program_transform_name='s,x,x,'
pythondir=''
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define HAVE_INTTYPES_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STDINT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRINGS_H 1
#define HAVE_STRING_H 1
#define HAVE_STRING_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_UNISTD_H 1
#define PACKAGE "libxml2"
#define PACKAGE_BUGREPORT ""
#define PACKAGE_NAME ""
#define PACKAGE_STRING ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define PROTOTYPES 1
#define STDC_HEADERS 1
#define VERSION "2.6.26"
#define __PROTOTYPES 1
#endif
#ifdef __cplusplus
void exit (int);

configure: exit 1
bash-2.03$
Comment 1 Daniel Veillard 2006-08-31 22:52:08 UTC
Seems to be a long standing libtool bug, see the thread when this was
posted to the mailing-list last month:

http://mail.gnome.org/archives/xml/2006-July/msg00190.html

Apparently this bug will be fixed in libtool 2.0, as was reported
see msg00203.html,

  the bug ain't really libxml2's fault but affects us,

Daniel
Comment 2 Snark 2012-08-25 18:21:17 UTC
What's the status of this?
Comment 3 André Klapper 2013-10-20 13:37:47 UTC
(In reply to comment #2)
> What's the status of this?

I'm not sure if such vague/unaddressed questions && setting NEEDINFO help anybody...
Comment 4 Nick Wellnhofer 2017-06-14 12:09:24 UTC
Closing 10 year old z/OS libtool issue as "not-gnome".