Kurt Raschke wrote:
> Trying to build yazproxy 1.01 with USEMARCON 1.51 on
Mac OS X 10.4
> results in the following error:
>
> g++ -DPACKAGE_NAME=\"\"
-DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=
\"\"
> -DPACKAGE_STRING=\"\"
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE=
\"yazproxy\"
> -DVERSION=\"1.0.1\" -DSTDC_HEADERS=1 -
DHAVE_SYS_TYPES_H=1
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -
DHAVE_STRING_H=1
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -
DHAVE_INTTYPES_H=1
> -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 - DHAVE_DLFCN_H=1
-DHAVE_USEMARCON=1
> -DHAVE_SETRLIMIT=1 - DHAVE_GETRLIMIT=1
-DHAVE_GETTIMEOFDAY=1
> -DHAVE_PWD_H=1 - DHAVE_SYS_RESOURCE_H=1
-DHAVE_SYS_STAT_H=1
> -DHAVE_SYS_TIME_H=1 - DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_WAIT_H=1
> -DHAVE_UNISTD_H=1 - DHAVE_LIBDL=1 -DHAVE_XSLT=1 -I. -I.
> -I/Users/kurt/Desktop/yaz-2.1.12/ include
-DYAZ_POSIX_THREADS=1
> -D_REENTRANT -DYAZ_USE_NEW_LOG=1 -I/
> Users/kurt/Desktop/yaz++-0.9/include -I./../include
-I/sw/include/
> libxml2 -I/sw/include
-I/Users/kurt/Desktop/usemarcon151/library -g - O2
> -MT yaz-proxy.lo -MD -MP -MF .deps/yaz-proxy.Tpo -c
yaz-proxy.cpp
> -fno-common -DPIC -o .libs/yaz-proxy.o
> /Users/kurt/Desktop/usemarcon151/library/ytab.h:485:
error: expected
> identifier before numeric constant
> /Users/kurt/Desktop/usemarcon151/library/ytab.h:485:
error: expected
> `}' before numeric constant
> /Users/kurt/Desktop/usemarcon151/library/ytab.h:485:
error: expected
> unqualified-id before numeric constant
> /Users/kurt/Desktop/usemarcon151/library/ytab.h:504:
error: expected
> unqualified-id before 'public'
> /Users/kurt/Desktop/usemarcon151/library/ytab.h:506:
error: virtual
> outside class declaration
> /Users/kurt/Desktop/usemarcon151/library/ytab.h:506:
error: function
> 'void yyerror(char*)' is initialized like a variable
>
> ...and it continues on for some while about ytab.h.
>
> I'm rather perplexed by this error; ytab.h certainly
compiles fine as a
> part of the USEMARCON package, so why does it suddenly
fail when
> compiled as a part of yazproxy?
>
> Other relevant software versions:
> gcc version 4.0.1
> yaz 2.1.12
> yaz++ 0.9
>
> Thanks in advance for any assistance with this issue.
>
> -Kurt
I really can't tell, as do not know the ytab.h header from
the USEMARCON
package, but I have some suggestions which you might want to
try:
a) figure out whith which -D options the USEMACON package
compiles fine
on it's own, and which -D options during the yazproxy
compile might
change the compiled source such that compilation fails.
Eventually try
manually to add the -D options of yazproxy one-by-one to the
USEMACON
package compile command.
b) grep for the culprit -D options in the USEMACON package
source code
and see which part of the source then is included/excluded.
It might
very well be that -D options fro yazproxy do nasty things to
USEMACON.
Thsi might give you a good clue of where things went wrong
in the first
place.
Marc Cromme, Index Data
>
> _______________________________________________
> Yazlist mailing list
> Yazlist lists.indexdata.dk
> http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list
--
Marc Cromme, cand. polyt, Ph.D
Senior Developer, Project Manager
Index Data Aps
Købmagergade 43, 2
1150 Copenhagen K.
Denmark
tel: +45 3341 0100
fax: +45 3341 0101
http://www.indexdata.com
INDEX DATA Means Business
for Open Source and Open Standards
_______________________________________________
Yazlist mailing list
Yazlistlists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list
|