[Dev] [ARM] Parabola ARM Port

coadde coadde at riseup.net
Mon Dec 22 19:52:29 GMT 2014

Hash: SHA512

> ahoi Kuba
> thank you for trying this!
>> I was trying to compile the stage 2 of gcc
> does this mean that you successfully built and installed the
> following packages?
> armv7l-unknown-linux-gnueabihf-binutils 
> armv7l-unknown-linux-gnueabihf-linux-libre-api-headers 
> armv7l-unknown-linux-gnueabihf-gcc-stage1 
> armv7l-unknown-linux-gnueabihf-glibc-headers-and-startfiles
> I just ask this to make sure you did. Those packages are absolutely
> necessary to be built and installed before trying to build
> armv7l-unknown-linux-gnueabihf-gcc-stage2. In case you installed
> those packages pacman should tell you:
> $ pacman -Q |grep arm armv7l-unknown-linux-gnueabihf-binutils
> 2.24-8 armv7l-unknown-linux-gnueabihf-gcc-stage1 4.9.2-1 
> armv7l-unknown-linux-gnueabihf-glibc-headers-and-startfiles 2.20-4 
> armv7l-unknown-linux-gnueabihf-linux-libre-api-headers
> 3.16.2_gnu-1
>> but got this error: 
>> /home/kzer-za/parabola_workspace/parabola_arm/armv7l-unknown-linux-gnueabihf-gcc-stage2/PKGBUILD:
line 90:
>> /home/kzer-za/parabola_workspace/parabola_arm/armv7l-unknown-linux-gnueabihf-gcc-stage2/src/gcc-4.9.2/configure:
Permission denied
> this is odd. there shouldn't be any special privileges be required.
> you should be able to build any of those packages as any
> unprivileges user. the only command necessary to build any package
> should be: $ makepkg nothing more
> could you provide the output of the following three commands
> please? maybe they reveal some problem due to permissions: $ ls -ld
> /home/kzer-za/parabola_workspace $ ls -ld
> /home/kzer-za/parabola_workspace/parabola_arm $ ls -l
> /home/kzer-za/parabola_workspace/parabola_arm
>> I have tried:
>> - - To change permissions by right-clicking the file and going
>> into properties. (dolphin)
> don't do that. there is no need to change permissions.
>> - - Trying to making the package again. (twice)
> don't do that. when building the package, always start from a clean
> environment, I mean remove any files and directories some previous
> attempt might have been created.
>> - - Removing all files excluding the PKGBUILD and the patch.
> that should be good.
>> I am compiling as root using the --asroot option.
> again, don't. there is no need to do this as root. Actually doing
> things as root is dangerous as long as you are not absolutely sure
> what the commands and scripts do.
>> I extracted the tar file (because it did not happen for some
>> reason) and then I got this error.
> maybe this could be a permission issue again?
> in case you are at IRC #parabola, we could continue tracking down
> the issue there :)
> greets Mono

I've built directly "xtensa-unknown-elf-gcc" without stage1 and stage2
and built "ath9k-htc-firmware[2]" (it depends on
xtensa-unknown-elf-{gcc/binutils} [0][1]) without
xtensa-unknown-elf-linux-libre-api-headers and xtensa-unknown-elf-glibc.
Otherwise, you could use cross-{binutils,gcc} as base to begin arm
cross-compiling, I've put inside PKGBUILD a table with examples about
different architectures to make yourself a new one.

But, i have a question for you: Is necessary to build gcc stage1, gcc
stage2, glibc, linux-libre-api-headers to cross compiling GNU/Linux
arm? In my opinion, it isn't necessary.



More information about the Dev mailing list