Package Details: openwatcom-v2 2.0_2024_03_01-1

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: 8
Popularity: 0.31
First Submitted: 2015-08-19 14:48 (UTC)
Last Updated: 2024-03-19 18:07 (UTC)

Latest Comments

1 2 Next › Last »

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.

DarkShadow44 commented on 2022-05-25 20:34 (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.

VorpalWay commented on 2022-05-25 14:45 (UTC)

Thanks, fixed it. Not sure about the git package though. AFAIK aur helpers don't detect it when the name is the same.

This is true, though aurutils ships with an example (/usr/share/doc/aurutils/examples/vercmp-devel) script that will list any -git/svn/etc packages that are out of date.

I noticed you changed from Current-Build to Last-CI-build. I don't know what the difference are between those. Though Last-CI-build seems a few hours newer. I think "Current-Build" was probably more correct, in the README it is labelled as "Current Release Build" which sounds more stable at least.

DarkShadow44 commented on 2022-05-24 23:52 (UTC)

Thanks, fixed it. Not sure about the git package though. AFAIK aur helpers don't detect it when the name is the same.

VorpalWay commented on 2022-05-24 19:32 (UTC)

The package is also broken:

==> ERROR: Failure while downloading https://github.com/open-watcom/open-watcom-v2/releases/download/Current-build/ow-snapshot.tar.gz
    Aborting...

They have changed format to .tar.xz since this PKGBUILD was last updated.

VorpalWay commented on 2022-05-24 19:30 (UTC)

Hi. I believe this would be better as a -git package that downloaded the tag Current-Build rather than the tar.gz. That way aur helpers (such as aurutils) can help detect when this needs to be updated and rebuilt.

tekmonkey commented on 2022-01-06 13:47 (UTC) (edited on 2022-01-06 13:52 (UTC) by tekmonkey)

hey, apologies beforehand if this is a noob question:

I installed openwatcom-v2 on endeavour OS but it did not copy the owsetenv.sh to /etc/profile.d

is there something going wrong or did i miss something?

See topic here: https://bbs.archlinux.org/viewtopic.php?id=272857

I noticed the PKGBUILD does

cp "${srcdir}/owsetenv.sh" ${pkgdir}/opt/watcom/

is that intentional? why not /etc/profile.d?

DarkShadow44 commented on 2020-03-15 14:37 (UTC)

@AndrevS Fixed the script. Not sure how that ever worked though, I didn't change it before.