Hi, I could fix the error, it turned out that bison couldn't process vls14_parse.y correctly. The reason is an incompatibility between the bison used by the buildtools (version 1.25) and the bison I have installed on my system (version 2.1). If the buildtools can find a bison during build time, the one which comes with the package will not be compiled and the installed version will be used instead. Making the installed bison unavailable i.e. by renaming it fixes the issue temporarily so that a compatible version of the buildtools can be created.
This bug and its workaround were discovered by Markus Döhr, and I can confirm it. At least until the .y files of maxdb have been made compatible, somebody who understands the build system well enough should make the compilation and installation of the buildtool bison unconditional. Thanks a lot for all the help! - Chris On Tue, 2006-08-15 at 03:54, "Döhr, Markus ICC-H" wrote: > > TARGET: ':ls/vls14_parse.y' STATUS: ERROR > > > > ERROR: error while touching vls14_parse.o > > > > ->2, No such file or directory > > > > > > I get this error twice. All the following errors seem to be dependency > > errors due to vls14_parse.y. I'd appreciate if somebody could help me > > with this. > > IIRC I had the same error trying to compile on Solaris/X86 (32bit). > > Do you use the buildtool provided "bison"? > > > Regards, > > SIEGENIA-AUBI KG > Informationswesen > > i.A. > > Markus Döhr > SAP-CC/BC, SAPDB-DBA > > Tel.: +49 6503 917-152 > Fax: +49 6503 917-7152 > E-Mail: [EMAIL PROTECTED] > Internet: http://www.siegenia-aubi.com > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
