From: <ren...@nl...> - 2007-09-26 14:55:30
|
Hi developer team, I am very happy to announce that I just solved my little BSF4Rexx problem=20 on Mac (Intel) so that 3.2.0 is ready to go when needed. On the other hand I was somewhat surprised when I found the reason: the=20 build process suddenly does not give the shared libraries the extension=20 ".dylib" anymore, but just leaves them without extension, which is=20 apparenlty fine for MacOSX because ooRexx does not have a problem. BSF4Rexx however, the Java JNIlib, happily linked against the older=20 libraries (I tell it to do so in the makefile), that were not overwritten=20 because they now have different names. Also, a "sudo make uninstall" does=20 not get rid of them anymore. This leaves the question when this did happen= =20 and why. Only when I did not see my debugging statements I got suspicious=20 of running with the right load modules, and wiped the directory and all=20 softlinks I have to the files. Anyway, Rony, the -DDEBUG2 on BSF4Rexx.cc (that also went to the wrong=20 list) is not really top priority anymore. best regards, Ren=E9 Vincent Jansen LDM - Data Modelling Support Group Finance Gustav Mahlerlaan t: +31203830718 m: +31624555577 --------------------------------------------------------------------------- This message (including any attachments) is confidential and may be privile= ged. If you have received it by mistake please notify the sender by return = e-mail and delete this message from your system. Any unauthorised use or di= ssemination of this message in whole or in part is strictly prohibited. Ple= ase note that e-mails are susceptible to change. ABN AMRO Bank N.V, which h= as its seat at Amsterdam, the Netherlands, and is registered in the Commerc= ial Register under number 33002587, including its group companies, shall no= t be liable for the improper or incomplete transmission of the information = contained in this communication nor for any delay in its receipt or damage = to your system. ABN AMRO Bank N.V. (or its group companies) does not guaran= tee that the integrity of this communication has been maintained nor that t= his communication is free of viruses, interceptions or interference. --------------------------------------------------------------------------- |