Package Details: pcc 1.1.0-1

Git Clone URL: (read-only, click to copy)
Package Base: pcc
Description: A Portable C Compiler
Upstream URL:
Keywords: compiler lightweight portable
Licenses: custom:BSD
Submitter: andreas_baumann
Maintainer: edh
Last Packager: edh
Votes: 20
Popularity: 0.31
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 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):

  echo 'int main(){exit(0);}' > hello.c
  pcc -g -Wl,-emain -D__float128="long double" -o hello hello.c
  gdb --args ./hello

strajder commented on 2022-06-25 17:35 (UTC)

Getting SEGV when trying to compile a C program with this pcc, using

$ echo 'int main(){}' > hello.c
$ pcc -D__float128="long double" -o hello hello.c
$ gdb --args ./hello


Program received signal SIGSEGV, Segmentation fault.
0x0000000000417d40 in __do_global_ctors_aux ()
(gdb) bt
#0  0x0000000000417d40 in __do_global_ctors_aux ()
#1  0x000000000040201b in _init ()
#2  0x00007fffffffe660 in ?? ()
#3  0x00007ffff7ddb371 in __libc_start_main () from /usr/lib/
#4  0x0000000000402405 in _start () at ../sysdeps/x86_64/start.S:115

edh commented on 2020-09-15 09:23 (UTC)


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:

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...

edh commented on 2017-07-02 12:31 (UTC)

@andreas_baumann I added your patch to the package. Thanks for working on this.

andreas_baumann commented on 2017-07-02 11:56 (UTC) (edited on 2017-07-02 11:57 (UTC) by andreas_baumann)

@edh: very good point you are making here about maintainance on AUR. :-) So I added a patch here: Note: the CVS/current version is already fixed (differently). This patch is only a backport for the 1.1.0 release of pcc.

edh commented on 2017-07-02 11:05 (UTC) (edited on 2017-07-02 11:05 (UTC) by edh)

@andreas_baumann Since you are already in contact with the developer, I would recommend you to send the patch to him. There would be no patching required at all if it would be merged. Btw. it would not make sense to split the AUR by architecture. Hence maintainers may or may not keep support for old architectures in the AUR depending on their workload.