Package Details: openwatcom-v2 2.0_2024_05_02-2

Git Clone URL: https://aur.archlinux.org/openwatcom-v2.git (read-only, click to copy)
Package Base: openwatcom-v2
Description: The Open Watcom Fortran/C/C++ compiler, binary distribution -V2 fork
Upstream URL: https://github.com/open-watcom
Keywords: compiler cross
Licenses: custom:OWPL-1
Submitter: WFCody
Maintainer: DarkShadow44
Last Packager: DarkShadow44
Votes: 9
Popularity: 0.22
First Submitted: 2015-08-19 14:48 (UTC)
Last Updated: 2024-05-18 19:30 (UTC)

Latest Comments

1 2 3 Next › Last »

DarkShadow44 commented on 2024-05-24 20:15 (UTC)

You get the error when just running /opt/watcom/binl/wlink, without any parameters? Because that works fine for me.

lexbailey commented on 2024-05-24 17:35 (UTC)

some parts of this package appear to be broken. For example, if I run binl/wlink then I get an error:

Error! E2000: Error: could not open message resource file.

Looking back at the older comments, appears that this has happened before? The same error is not present in the latest stable release from github

DarkShadow44 commented on 2024-05-18 19:31 (UTC)

Sure, if you say you need it, I'll include it.

miffe commented on 2024-05-18 15:20 (UTC)

Please don't remove /opt/watcom/binw, it contains stuff needed to build for DOS, like dos4gw.exe and dos32a.exe

Thetic commented on 2024-05-17 20:25 (UTC)

@DarkShadow44 yes, thank you

DarkShadow44 commented on 2024-05-17 15:14 (UTC)

@Thetic Does it work with the new version? Because it does for me.

Thetic commented on 2024-05-04 02:47 (UTC) (edited on 2024-05-04 02:47 (UTC) by Thetic)

In version 2.0_2024_03_01-1, wmake is broken:

$ /opt/watcom/binl/wmake
Error: could not open message resource file.

I don't know whether this is a bug or a packaging issue.

DarkShadow44 commented on 2024-03-19 18:07 (UTC)

Apart from PIE/RELRO this should be fixed now.

DarkShadow44 commented on 2024-03-18 20:09 (UTC)

Regarding the out of date notification, I'm not exactly sure how I should handle this.

I opened an issue on their github, but currently I can't have a stable link for the latest version, so if I add checksum verification it will break with a new version. I'd prefer for this to not be a real git package though, not sure how to do that unless they also date-tag their latest release. Unless I always use the previous release (which is date-tagged)... How would you recommend dealing with this?

Not sure if missing PIE and RELRO is a problem, there's not much I can do without completely building the package myself. Is that causing issues?

I'll fix the permissions in the next update.

VorpalWay commented on 2022-05-27 08:40 (UTC)

Ah yes, because I thought that was missing. May bad. Anyways, If I clone the git repo as well, I could use the tag for proper git versioning. Not sure if that is best practice though.

I considered this too, I believe cloning the git repo and then not building is unconventional at least.

I also considered building openwatcom locally (making it a real -git package) but that really seems like quite a pain! The compilation is single threaded and takes quite a long time.

I don't really have a good solution to this.

1 2 3 Next › Last »