Bugs item #1812341, was opened at 2007-10-12 18:29 Message generated for change (Comment added) made by stmane You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1812341&group_id=56967
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 Group: MonetDB5 5.2 >Status: Closed >Resolution: Fixed Priority: 6 Private: No Submitted By: Fabian (mr-meltdown) Assigned to: Sjoerd Mullender (sjoerd) Summary: M5: distribution tarballs contain non-sense data Initial Comment: As detected on the monetdb-X ML, M5 spits out completely bogus data on --version due to some brain [EMAIL PROTECTED] The to be attached patch supplies a workaround for the coming release by removing the bogus information. The issue should be solved, ideally by just using a plain C file instead of MX. ---------------------------------------------------------------------- >Comment By: Stefan Manegold (stmane) Date: 2007-10-15 09:48 Message: Logged In: YES user_id=572415 Originator: NO Fixed by Niels' and Sjoerd's combined efforts to extract the configure-replaced part of mserver5.mx.in (i.e., function monet_version()) into a separate monet_version.c.in, tuning mserver5.mx.in back into a simple mserver5.mx, and fixing the buildtools (autogen) to handle .c.in files correctly. Thanks! ---------------------------------------------------------------------- Comment By: Sjoerd Mullender (sjoerd) Date: 2007-10-12 22:10 Message: Logged In: YES user_id=43607 Originator: NO I'm not sure you realize how much work it is to make new release candidates. The work is, admittedly, mostly waiting, but it does take the better part of a day to do it all. In other words, this is not something to take too lightly. Having thought about the issue a little, I think this can wait until after the release, unless something really important crops up. Lowering the priority. ---------------------------------------------------------------------- Comment By: Fabian (mr-meltdown) Date: 2007-10-12 21:50 Message: Logged In: YES user_id=963970 Originator: YES I think the least we should do, is to remove the invalid information (as my patch does). So yes. (If we hadn't found out the problem, we had a good reason to ignore it...) ---------------------------------------------------------------------- Comment By: Sjoerd Mullender (sjoerd) Date: 2007-10-12 21:44 Message: Logged In: YES user_id=43607 Originator: NO The problem is a combination of Mx and configure. The file that produces the bogus information is mserver.mx.in. This file, in order to be included in the source tar ball, is processed by configure to produce mserver5.mx, which is then processed by Mx to produce mserver5.c. The latter processing is necessary for a source tar ball, but the former isn't. It's only necessary so that the latter can be done. If we could somehow reverse the two processes and postpone the processing by configure until the configure run by the end user, all would be well. In the mean time, is this bug serious enough to jeopardize the release? (I.e., is it a show stopper?) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1812341&group_id=56967 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
