Package Details: cross-mipsel-linux-gnu-gcc 10.1.0-1

Git Clone URL: (read-only, click to copy)
Package Base: cross-mipsel-linux-gnu-gcc
Description: The GNU Compiler Collection for the MIPS architecture
Upstream URL:
Keywords: gcc
Licenses: GPL, LGPL, FDL
Submitter: kyak
Maintainer: HarryChen
Last Packager: HarryChen
Votes: 7
Popularity: 0.000005
First Submitted: 2015-08-11 15:05
Last Updated: 2020-05-10 15:15

Required by (9)

Sources (1)

Latest Comments

1 2 Next › Last »

amlamarra commented on 2020-06-01 19:17

@HarryChen What's the solution to this?

HarryChen commented on 2019-12-25 03:06

@Distag @Severus Yeah the problem exists, for this version gcc is built without any libc. Actually the triplet should be mipsel-none-elf but not mipsel-linux-gnu. The package is wrongly named before I adopted this package, so I decided to keep it as-is. Sorry for the inconvenience.

Distag commented on 2019-08-11 13:00

/usr/lib/cross-mipsel-linux-gnu/lib/gcc/mipsel-linux-gnu/9.1.0/../../../../mipsel-linux-gnu/bin/ld: cannot find crt1.o: No such file or directory

/usr/lib/cross-mipsel-linux-gnu/lib/gcc/mipsel-linux-gnu/9.1.0/../../../../mipsel-linux-gnu/bin/ld: cannot find crti.o: No such file or directory

/usr/lib/cross-mipsel-linux-gnu/lib/gcc/mipsel-linux-gnu/9.1.0/../../../../mipsel-linux-gnu/bin/ld: cannot find crtbeginT.o: No such file or directory

/usr/lib/cross-mipsel-linux-gnu/lib/gcc/mipsel-linux-gnu/9.1.0/../../../../mipsel-linux-gnu/bin/ld: cannot find -lgcc

/usr/lib/cross-mipsel-linux-gnu/lib/gcc/mipsel-linux-gnu/9.1.0/../../../../mipsel-linux-gnu/bin/ld: cannot find -lc

collect2: error: ld returned 1 exit status

Severus commented on 2019-07-29 08:01

After install this package, I cannot build hello file. Because it cannot search the lib headers.

codeworkx commented on 2017-11-12 12:45


kyak commented on 2017-07-30 16:06

Not using these anymore, hence disowning.

jakebailey commented on 2016-05-20 07:22

Unfortunately, GCC 6's new default standard breaks this package, as the fix was only backported to GCC 5, and not 4.9 (though this package uses the 4.9.2 tarball anyway).

I guess I'm glad I kept a copy of my built packages. :(

jakebailey commented on 2016-05-20 06:40

I'm not sure that's a good line of reasoning, given that the official gcc package in the core repo tracks with the latest GCC release, and seperate packages are created in the AUR for each of the older releases just as @paulburton suggested. If your build depends on an older release, you should have to pin your version just like those who have the same version dependency problems on other architectures. What this package is doing now isn't very consistent.

kyak commented on 2016-04-21 15:28

Well.. Feel free to create the cross-mipsel-linux-gnu-gcc-latest or something, because GCC 6 is out now.
Good luck with your projects jumping from one gcc release series to another.

paulburton commented on 2016-04-21 07:58

@kyak it would seem more appropriate to me for this package (which has no version in its name) to be the latest gcc, and if you still want the 4.9 series create a package with that version number in its name (cross-mipsel-linux-gnu-gcc49 or something). Just like the main gcc package is always the latest gcc.