Search Criteria
Package Details: msp430-elf-gcc-stage1 13.1.0-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/msp430-elf-gcc-stage1.git (read-only, click to copy) |
|---|---|
| Package Base: | msp430-elf-gcc-stage1 |
| Description: | The GNU Compiler Collection bootstrap for the msp430-elf target. |
| Upstream URL: | http://gcc.gnu.org |
| Licenses: | GPL, LGPL |
| Submitter: | vonPalitroque |
| Maintainer: | vonPalitroque |
| Last Packager: | vonPalitroque |
| Votes: | 7 |
| Popularity: | 0.000000 |
| First Submitted: | 2015-09-19 18:09 (UTC) |
| Last Updated: | 2023-07-25 00:33 (UTC) |
Dependencies (4)
- elfutils (elfutils-gitAUR)
- libmpc (libmpc-gitAUR)
- msp430-elf-binutilsAUR (msp430-elf-gcc-binAUR)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compatAUR)
Latest Comments
vonPalitroque commented on 2021-10-04 18:39 (UTC)
Greetings jpartain,
So it does; unfortunate. It looks like there is some migration going on around those parts [1]. I need to figure out where to pull ISL from once the dust settles. The good news is that ISL is not strictly required to build gcc [2]. Modify the PKGBUILD to exclude the usage of isl:
eliminate isl from the source array;
in the prepare() function, get rid of the line that makes the symlink;
in the build() function, get rid of the line that says --with-isl.
This will build gcc without ISL. You will lose on some optimization passes though. The same thing should be done for the msp430-elf-gcc PKGBUILD if you need to install that one as well.
Cheers,
Orlando.
[1] https://gitlab.inria.fr/siteadmin/doc/-/wikis/Forge-to-Gitlab-migration-FAQ [2] https://gcc.gnu.org/install/prerequisites.html
jpartain commented on 2021-10-04 18:06 (UTC)
http://isl.gforge.inria.fr/isl-0.24.tar.xz seems to be down.
vonPalitroque commented on 2019-03-23 19:17 (UTC)
Gretings gmueller,
I went ahead and removed the NOEXTRACT check from this PKGBUILD and the msp430-elf-gcc PKGBUILD. I can not find documentation on that variable, but it looks like some AUR wrappers have issues with it. Looking at makepkg, NOEXTRACT is set when makepkg is run with the --noextract option. I can not replicate the behavior with packer-aur, but that is no reason to break other people's AUR management system. Chances are if you are using some AUR management system, you are not passing any funny flags to makepkg. Not sure how yay works though.
Cheers, Orlando.
gmueller commented on 2019-03-23 17:02 (UTC)
Okay, found the problem. You check for NOEXTRACT, but this may be set even if config was not run before (using yay). So, better check for existing Makefiles? Thanks
gmueller commented on 2019-03-23 16:54 (UTC)
Hi!
The build is failing with "no rule to make all-gcc", any ideas?
vonPalitroque commented on 2018-08-27 15:59 (UTC)
Greetings zashi,
I was unfortunately unable to replicate your issue. I am not sure what is causing it. I have however updated the PKGBUILD to add the --with-system-zlib to the configure script. This flag is present in core/gcc anyway, and the full msp430-elf compiler is built with this flag anyway.
I have also added core/zlib to the list of dependencies to this package and msp430-elf-gcc as well.
Cheers,
Orlando.
sparques commented on 2018-08-27 15:30 (UTC)
This package failed to build for me. I saw no error in the output, though. I went into the source directory and manually ran 'make gcc-all' and got an error about compiling zlib. I added the --with-system-zlib argument to configure and was able to build the package.
Not sure if this is a problem specific to me or an upstreme issue--I just built this package on another system not too long ago (like 2 weeks) without issue.
Just adding this in case someone runs into the same issue.