On 11/20/14 12:42, Philippe Makowski wrote: >> I suppose that the problem is that firebird also fails to start. What do >> we see in system log? > not so easy to get from automated build
It's needed to confirm that firebird fails to start. This is almost obvious. But it also tells how did it fail - was it exit() or segfault or unresolved external or something else... >> Not 100% sure, but looks like all this can be related with IPV6 support... >> > Yes I suspect that too > but build made just after IPV6 related commit didn't had this problem it > seems : > http://ci.ibphoenix.com/job/Firebird_trunk_on_Mageia_64/252/ > > or can it be both IPV6 and FDB changes ? because the first build that > failed was the one just after FDB updates I see no way how can FDB changes affect server start. The only change in engine is related to changing list of SQL keywords - hardly a reason for not start. I.e. we need to know why does server not start. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
