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.
Search Criteria
Package Base Details: gdc-git
Package Actions
| 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 (UTC) |
| Last Updated: | 2019-08-23 10:42 (UTC) |
Packages (2)
<deleted-account> commented on 2012-10-28 00:14 (UTC)
debio264 commented on 2012-10-27 23:58 (UTC)
It looks like you need to call setup-gcc.sh insetad of update-gcc.sh.
svenstaro commented on 2012-09-17 15:37 (UTC)
Everything looks good now. Nice.
<deleted-account> commented on 2012-09-15 20:21 (UTC)
Updated now, the problem was the missing pure64 patch that the gcc package uses
(which I find quite disturbing that one needs to patch gcc to have it work correctly
on a normal linux 64-bit system such as Arch).
Also added cloog as a dependency because the extra-x86_64-build script says it is.
svenstaro commented on 2012-09-10 02:41 (UTC)
You can run the command right now. It will make a clean chroot automatically. You do not need a VM.
<deleted-account> commented on 2012-09-09 17:45 (UTC)
When I find the time to setup a new clean Archlinux VM I'll do that,
hopefully that will be in the next few days. If you need a quick fix
right now you could add something like
mkdir -p $pkdir/usr/lib
cp -a $pkgdir/usr/lib64/* $pkgdir/usr/lib/
rm -rf $pkgdir/usr/lib64
right after the
make DESTDIR=$pkgdir install
line.
Maybe put the three lines in an if checking architecture for x86_64
svenstaro commented on 2012-09-09 17:34 (UTC)
Try this.
pacman -S devtools
cd where-the-PKGBUILD-is-in
sudo extra-x86_64-build
This will enable you to reproduce this
<deleted-account> commented on 2012-09-09 17:33 (UTC)
As I said I cannot reproduce that behaviour and as such cannot help debug the problem.
If I find the time I'll set up another clean Arch VM with devtools and see what happens.
As a pacakge fix one could include that after make install one looks whether there is a directory
/usr/lib64 and rename it to /usr/lib (or move all contents if both exist).
Essentially most options for the gdc-git PKGBUILD are straight from gcc's PKGBUILD, so
if it is really an error in the PKGBUILD you could crossreference the two.
Sorry if I'm not much of a help here but without experiencing the problem myself there's not
much I can do.
<deleted-account> commented on 2012-09-09 17:33 (UTC)
As I said I cannot reproduce that behaviour and as such cannot help debug the problem.
If I find the time I'll set up another clean Arch VM with devtools and see what happens.
As a pacakge fix one could include that after make install one looks whether there is a directory
/usr/lib64 and rename it to /usr/lib (or move all contents if both exist).
Essentially most options for the gdc-git PKGBUILD are straight from gcc's PKGBUILD, so
if it is really an error in the PKGBUILD you could crossreference the two.
Sorry if I'm not much of a help here but without experiencing the problem myself there's not
much I can do.
<deleted-account> commented on 2012-09-09 17:32 (UTC)
As I said I cannot reproduce that behaviour and as such cannot help debug the problem
I tried it on three different x86_64 Arch installs,
one VirtualBox VM, one VMWare VM and one native, all three times it worked (outside of a chroot).
As a pacakge fix one could include that after make install one looks whether there is a directory
/usr/lib64 and rename it to /usr/lib (or move all contents if both exist).
Essentially most options for the gdc-git PKGBUILD are straight from gcc's PKGBUILD, so
if it is really an error in the PKGBUILD you could crossreference the two.
Sorry if I'm not much of a help here but without experiencing the problem myself there's not
much I can do.
Pinned Comments