I am planning to use EiffelStudio on OpenBSD, and was wondering about
the status of these builds.
OpenBSD had a major ABI change between 5.4 and 5.5 (they change the
format of time_t from 'long' to 'long long'). Unfortunately, this breaks
all binaries that were compiled for an earlier version.
Which version was used to compile the OpenBSD packages? Or do I need to
use the PorterPackage? Any current hints on bootstrapping it for myself
(I had compiled to with OpenBSD long time ago, but probably forgot most
of the steps required)?
We are still compiling against OpenBSD 4.8 for higher backward compatibility. If really EiffelStudio does not work under 5.5, I would recommend recompiling it yourself.
Although not documented, once you have extracted the PorterPackage, do the following:
Are there any updates planned to the build process to support newer OpenBSD versions? estudio fails to run with loader errors in OpenBSD 6.4.
Bernd Schoeller
未读,
2019年1月20日 17:00:462019/1/20
回复作者
登录即可回复作者
转发
登录即可转发
删除
您无权在此群组中删除帖子
复制链接
举报消息
显示原始帖子
要么此群组的电子邮件地址为匿名状态,要么您得查看成员电子邮件地址权限才能查看原始帖子
收件人 eiffel...@googlegroups.com
On 20/01/2019 18:54, ri...@oddlyaccurate.com wrote:
> Are there any updates planned to the build process to support newer OpenBSD versions? estudio fails to run with loader errors in OpenBSD 6.4.
Hi Rick,
Some time ago, I tried getting it to run on OpenBSD a few years ago. My
experiences are described in
Now, the main blocker at that time was that the porter package (the
package containing pre-compiled EiffelStudio source code which normally
makes porting to a new platform easy) required the use of ftime, which
has been removed from OpenBSD (when they dropped libcompat).
Now, I am not sure if the porter package still requires 'ftime'. Things
might have improved, considering it is a deprecated API. I had submitted
a patch to remove it, but at that time it was still required by Windows.
You might want to take the path that I have described in the article
above. Beware that even after I got ES to run, there were still some
open issues; for example the debugger crashed on me.