Package Details: comcom32 0.0.alpha_3-2

Git Clone URL: https://aur.archlinux.org/comcom32.git (read-only, click to copy)
Package Base: comcom32
Description: 64 bit command interpreter for fdpp and dosemu2
Upstream URL: https://github.com/dosemu2/comcom64
Licenses: GPL-3.0-or-later
Conflicts: comcom32, comcom64
Provides: comcom32, comcom64
Submitter: severach
Maintainer: severach
Last Packager: severach
Votes: 1
Popularity: 0.000099
First Submitted: 2020-04-07 22:22 (UTC)
Last Updated: 2024-11-15 19:26 (UTC)

Dependencies (4)

Required by (3)

Sources (1)

Latest Comments

1 2 Next › Last »

simona commented on 2024-11-15 19:28 (UTC)

command.c:78:10: fatal error: go64.h: File o directory non esistente

simona commented on 2024-08-26 06:09 (UTC)

problem with djgpp-djcrx and djgpp-gcc

patlefort commented on 2024-08-24 19:31 (UTC)

Missing git in makedepends for the 32 bits version.

simona commented on 2024-07-01 08:45 (UTC)

gcc -E -x assembler-with-cpp asm.S | as --32 -o asm.o /usr/libexec/thunk_gen/parse_decls.sh 3 thunk_calls.tmp >plt.inc || (rm -f plt.inc ; false) cc -E -I. -fpic -P plt.S >plt.asm || (rm -f plt.asm ; false) plt.S:1:10: fatal error: dj64/plt.S.inc: File o directory non esistente 1 | #include <dj64/plt.S.inc> | ^~~~ compilation terminated.

severach commented on 2024-03-25 22:15 (UTC)

Conflicting with djgpp-djcrx-bootstrap forces people to build djgpp-djcrx and not just run with bootstrap forever. Aborting in prepare doesn't work well. Clean Chroot programs output build() errors but not prepare() errors. This won't matter soon since djgpp utils is going away for dj64dev.

We're a long ways off from building comcom-git. I did the first step building smallerc. I added you as a maintainer in case you need to fix stuff building the next packages: stsp/lfanew stsp/djstub stsp/dj64dev and probably more.

dreieck commented on 2024-03-25 20:51 (UTC) (edited on 2024-03-25 21:36 (UTC) by dreieck)

At which point does this conflict with djgpp-djcrx-bootstrap?

Or is this a "make conflict"?

Then you should not list it in the conflicts array but do a test in prepare(). (Package build is carried out without conflict tests, and built packages do not need to have a working compilation environment.)

(I am currently making a ↗ comcom-git $pkgbase (which should build both comcom32-git and comcom64-git), and I stumbled upon this strange conflicts entry in your PKGBUILD. I did implement such a test in prepare() -- you can check ↗ here.)

Regards!

dreieck commented on 2024-03-25 20:29 (UTC)

Unfortunately the -git version requires dj64-gcc which I can't find.

Regarding this I have created an ↗ upstream issue.

severach commented on 2024-03-25 19:33 (UTC)

No need as this doesn't build anything new and the -git doesn't compile yet. comcom32 is gone so isn't needed in any form. Delete and make new packages for comcom64.

dreieck commented on 2024-03-25 19:21 (UTC)

Don't forget to increment $pkgrel when you update the PKGBUILD without updating $pkgver (and then re-generate .SRCINFO and also add it to the git upload).

Seems you have just updated the PKGBUILD without a $pkgrel increment.

severach commented on 2024-03-25 18:47 (UTC) (edited on 2024-03-25 18:57 (UTC) by severach)

This is already a git package. Uncomment the -git line in the PKGBUILD. Unfortunately the -git version requires dj64-gcc which I can't find.

1 2 Next › Last »