Package Base Details: gdc-git

Git Clone URL: https://aur.archlinux.org/gdc-git.git (read-only, click to copy)
Submitter: demizer
Maintainer: FFY00 (kozzi)
Last Packager: kozzi
Votes: 17
Popularity: 0.000000
First Submitted: 2012-03-23 03:09
Last Updated: 2019-08-23 10:42

Packages (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »

Anonymous comment on 2012-11-04 04:06

These files should be removed during packaging via the following lines at the bottom
of the package-function:

rm -rf $pkgdir/usr/bin/{gcc,gcov,cpp,$CHOST-gcc,$CHOST-gcc-$_gccver,c++,g++,$CHOST-c++,$CHOST-g++}
rm -rf $pkgdir/usr/bin/{gcc-ar,gcc-nm,gcc-ranlib,$CHOST-gcc-ar,$CHOST-gcc-nm,$CHOST-gcc-ranlib}

What exactly did you do?

Anonymous comment on 2012-11-04 04:02

These files should be removed during packaging via the following lines at the bottom
of the package-function:

rm -rf $pkgdir/usr/bin/{gcc,gcov,cpp,$CHOST-gcc,$CHOST-gcc-$_gccver,c++,g++,$CHOST-c++,$CHOST-g++}
rm -rf $pkgdir/usr/bin/{gcc-ar,gcc-nm,gcc-ranlib,$CHOST-gcc-ar,$CHOST-gcc-nm,$CHOST-gcc-ranlib}

What exactly did you do?

cleger commented on 2012-11-04 03:56

File conflicts with gcc-multilib:

loading packages...
resolving dependencies...
looking for inter-conflicts...

Targets (1): gdc-git-20121104-1

Total Installed Size: 90.08 MiB

Proceed with installation? [Y/n] y
(1/1) checking package integrity [################################################################] 100%
(1/1) loading package files [################################################################] 100%
(1/1) checking for file conflicts [################################################################] 100%
error: failed to commit transaction (conflicting files)
gdc-git: /usr/bin/x86_64-unknown-linux-gnu-c++ exists in filesystem
gdc-git: /usr/bin/x86_64-unknown-linux-gnu-g++ exists in filesystem
gdc-git: /usr/bin/x86_64-unknown-linux-gnu-gcc exists in filesystem
gdc-git: /usr/bin/x86_64-unknown-linux-gnu-gcc-ar exists in filesystem
gdc-git: /usr/bin/x86_64-unknown-linux-gnu-gcc-nm exists in filesystem
gdc-git: /usr/bin/x86_64-unknown-linux-gnu-gcc-ranlib exists in filesystem
Errors occurred, no packages were upgraded.

cleger commented on 2012-11-04 03:54

File conflicts with gcc-multilib:

loading packages...
resolving dependencies...
looking for inter-conflicts...

Targets (1): gdc-git-20121104-1

Total Installed Size: 90.08 MiB

Proceed with installation? [Y/n] y
(1/1) checking package integrity [################################################################] 100%
(1/1) loading package files [################################################################] 100%
(1/1) checking for file conflicts [################################################################] 100%
error: failed to commit transaction (conflicting files)
gdc-git: /usr/bin/x86_64-unknown-linux-gnu-c++ exists in filesystem
gdc-git: /usr/bin/x86_64-unknown-linux-gnu-g++ exists in filesystem
gdc-git: /usr/bin/x86_64-unknown-linux-gnu-gcc exists in filesystem
gdc-git: /usr/bin/x86_64-unknown-linux-gnu-gcc-ar exists in filesystem
gdc-git: /usr/bin/x86_64-unknown-linux-gnu-gcc-nm exists in filesystem
gdc-git: /usr/bin/x86_64-unknown-linux-gnu-gcc-ranlib exists in filesystem
Errors occurred, no packages were upgraded.

Anonymous comment on 2012-10-31 11:51

The source code migrated from bitbucket to github a long time ago, but issues were
still to be reported at bitbucket, there was no wiki on gdcproject.org, etc., so
the project home was still more bitbucket than github (even though the code was at github);
recently they moved these other things over as well, but I did not want to change the url
yet in case they change there minds again. But since it was more or less requested: url changed
to github.

Anonymous comment on 2012-10-31 08:09

shouldn't the web address be: https://github.com/D-Programming-GDC/GDC
the project has migrated from bitbucket to github

Anonymous comment on 2012-10-29 13:22

The -j3 shouldn't have been there, forgot to remove it after testing (it's gone now).

debio264 commented on 2012-10-28 04:44

Also, could you run make with ${MAKEFLAGS} instead of blindly using -j3? Building GDC on low memory systems (in my case an ARM system) will fail with -j3 because the C++ compiler will run out of memory.

Anonymous comment on 2012-10-28 00:14

Thanks, seems like they merged the two scripts (setup-gcc.sh which was in root/gcc/d and update-gcc.sh which was in root/)
and named the new one setup-gcc.sh
Fixed now.

debio264 commented on 2012-10-27 23:58

It looks like you need to call setup-gcc.sh insetad of update-gcc.sh.