Am 25.06.13 07:10, schrieb Friedrich Dominicus:
"jtuchel@objektfabrik.de" <jtuchel@objektfabrik.de> writes:
Hi Friedrich,
I guess what could help people understand more about what the actual differences might be is if you can exactly say under which Pharo version and on which VM your ODBC connection had been working before. Was it also on a 64 bit lInux? Even the same installation or some other 64 bit machine (I know from hard and painful experience that two Linux boxes can look very similar but still be completely different, just because a single link is missing)? No it was exactly this machine. But I updated Pharo to 2.0 and it may be that I updated some libraries on this Box also. But sorry, I can not tell really. I guess nobody really keeps track on the working machine on what you install when. You need it and then you fetch it.
That's the way we all do it, right? So are you saying ODBC in Pharo 1.x still works on that very same machine? Does ldd for the old VM yield the same kind of output? If so, it should be possible to limit the search to the 2.0 VM and Image and ignore the surroundings. That would sure be of great help.
So I am afraid you've now entered a stage in which you need to gradually change things (and keep track of them) and try different VMs, Images and libraries up until you find a combination that works. Or some bright soul who knows it all ;-) Well yes that might be necessary. Unfortunatly I know the same code runs fine on Windows and so it probabl has to do with the used/provided odbc libraries. I was just wondering if anyone else uses this combination. But AFAIKT it seems ODBC is not "really" used with Pharo. Hmm, I have no idea to be honest. I am not even using Pharo much. I somehow mistrust ODBC on Linux per se, but that is based on experiences from around 2005, so a very uninformed opinion rather than based on (current) facts.
Joachim