Search Criteria
Package Details: pcc 1.1.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/pcc.git (read-only, click to copy) |
---|---|
Package Base: | pcc |
Description: | A Portable C Compiler |
Upstream URL: | http://pcc.ludd.ltu.se/ |
Keywords: | compiler lightweight portable |
Licenses: | custom:BSD |
Submitter: | andreas_baumann |
Maintainer: | edh |
Last Packager: | edh |
Votes: | 20 |
Popularity: | 0.000000 |
First Submitted: | 2009-03-13 10:02 (UTC) |
Last Updated: | 2020-09-15 09:23 (UTC) |
Latest Comments
1 2 3 Next › Last »
andreas_baumann commented on 2024-04-28 12:06 (UTC)
@Tpaefawzen: temporarily downloads from another location like https://mirrors.cloud.tencent.com/macports/distfiles/pcc/ is an idea (with the usual warning about downloading unknown stuff from the interwebs). Sadly also the CVS repo seems to be on the same server..
edh commented on 2024-04-28 08:48 (UTC)
@Tpaefawzen Unfortunately, upstream is down sometimes :/
Tpaefawzen commented on 2024-04-28 00:54 (UTC)
Could not obtain upstream source
andreas_baumann commented on 2022-06-25 18:05 (UTC) (edited on 2022-06-25 18:06 (UTC) by andreas_baumann)
I'm working around this with (though I'm using pcc-cvs 20200914 currently):
strajder commented on 2022-06-25 17:35 (UTC)
Getting SEGV when trying to compile a C program with this pcc, using
edh commented on 2020-09-15 09:23 (UTC)
@Elronnd
Thanks for the hint. Fixed!
Elronnd commented on 2020-09-14 01:35 (UTC)
Needs to be built with CFLAGS=-fcommon.
newbthenewbd commented on 2019-09-25 12:06 (UTC)
The package seems to be affected by this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1551537
The published workaround of using the -D__float128="long double" option makes it successfully compile, albeit not without a warning.
edh commented on 2019-07-10 12:32 (UTC)
Dropped i686 support as a response.
@cbb It was not some random gist! It was a patch by the previous AUR maintainer hosted on GitHub. Unfortunately, he seem to have deleted it.
cbb commented on 2019-07-10 11:36 (UTC)
This package is now broken because the patch file is no longer online. I suspected this would happen when I read the PKGBUILD, even before I tried to install it. Making a package depend on some random Gist is just asking for it...
1 2 3 Next › Last »