Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I believe that I have compiled MAME in the past, but for whatever reason, it doesn't want to build any more. Normally, I can troubleshoot the errors, but this one is not giving me much to work with. I'm posting it here in the hopes that it may make sense to someone else. I've dug around Google and have come up empty handed.
I believe that I have compiled MAME in the past, but for whatever reason, it doesn't want to build any more. Normally, I can troubleshoot the errors, but this one is not giving me much to work with. I'm posting it here in the hopes that it may make sense to someone else. I've dug around Google and have come up empty handed.
If you built it on -current with gcc 7 before, then an update to gcc might have broken it.
We're several revisions behind the Debian patch set that gets applied to our gcc package, since the newest one broke the cross compiler and I was hoping someone else would fix it ;-)
I've just patched it myself and next week I will push out the new gcc package after rebuilding the latest -current batch with it. I don't know if it'll help though!
If you built it on -current with gcc 7 before, then an update to gcc might have broken it.
We're several revisions behind the Debian patch set that gets applied to our gcc package, since the newest one broke the cross compiler and I was hoping someone else would fix it ;-)
I've just patched it myself and next week I will push out the new gcc package after rebuilding the latest -current batch with it. I don't know if it'll help though!
I appreciate you looking into this. I'll take a stab at it again after you publish those. On a side note, what do you use to build the slackware arm packages? Are you using a cluster of raspberry pi boards?
On a side note, what do you use to build the slackware arm packages? Are you using a cluster of raspberry pi boards?
They're mostly built on one machine (an Orange Pi H3), which uses distcc to three x86_64 machines with the cross toolchain. Each batch of updates has (most of the time) each package built three times to try and resolve any inter dependencies between packages within a batch, therefore building any packages on separate machines is impractical unless they are atomic (like the Kernel - but even that's not always the case).
The build system is automated, so I just set it off and check the result afterwards (or during, if I happen to be around and curious).
For example, the last batch completed building already:
Code:
root@stokely:~# cat /tmp/r2b/status-current
First build began on..................: Fri Nov 3 09:14:07 GMT 2017
Time spent building since first build : 425 minutes / 7 hours / 0 days
Most recent package began building on : Fri Nov 3 16:19:37 GMT 2017
Success count...: 5 (83%) [ recently: n/openssl , l/gegl , l/expat , ap/mariadb , ap/cups ]
Build pass......: 3 of 3
Current activity:-
Building package a/sysvinit-scripts [ 6 of 6 ]
*** Complete.
They're mostly built on one machine (an Orange Pi H3), which uses distcc to three x86_64 machines with the cross toolchain. Each batch of updates has (most of the time) each package built three times to try and resolve any inter dependencies between packages within a batch, therefore building any packages on separate machines is impractical unless they are atomic (like the Kernel - but even that's not always the case).
The build system is automated, so I just set it off and check the result afterwards (or during, if I happen to be around and curious).
For example, the last batch completed building already:
Code:
root@stokely:~# cat /tmp/r2b/status-current
First build began on..................: Fri Nov 3 09:14:07 GMT 2017
Time spent building since first build : 425 minutes / 7 hours / 0 days
Most recent package began building on : Fri Nov 3 16:19:37 GMT 2017
Success count...: 5 (83%) [ recently: n/openssl , l/gegl , l/expat , ap/mariadb , ap/cups ]
Build pass......: 3 of 3
Current activity:-
Building package a/sysvinit-scripts [ 6 of 6 ]
*** Complete.
Oh man, that's awesome. Did you follow a specific tutorial by any chance? I've been wanting to build a raspberry pi cluster, but have very little experience in setting up cross-compiling.
Oh man, that's awesome. Did you follow a specific tutorial by any chance? I've been wanting to build a raspberry pi cluster, but have very little experience in setting up cross-compiling.
The build system I created myself. Setting up a cross toolchain was the result of lots of research and experimentation.
I just found this on Amazon. I should be able to use the fatdog's sarpi image, correct?
The SARPI image is for Raspberry Pi.
The Orange Pi is supported officially by Slackware ARM, but version 2 has not been tested - only v1.
The 2GB RAM would be good though - perhaps I'll look at v2 at some point, if the Kernel support is there.
The SARPI image is for Raspberry Pi.
The Orange Pi is supported officially by Slackware ARM, but version 2 has not been tested - only v1.
The 2GB RAM would be good though - perhaps I'll look at v2 at some point, if the Kernel support is there.
I can give it a try. I'm going to purchase one this weekend. So, I can just create an install iso like I would for the x86* series?
In the link that I posted, I see a review from back in April of this year saying that the board was supported by Slackware. Once I get it, I'll report back. Thank you for taking time to explain things. I'm not as savvy when it comes to ARM devices.
In the link that I posted, I see a review from back in April of this year saying that the board was supported by Slackware. Once I get it, I'll report back. Thank you for taking time to explain things. I'm not as savvy when it comes to ARM devices.
OK well hopefully whoever said that has tested it, but just has not contributed back anything. There will be changes required to the installation settings since it's a newer revision of the board.
Presumably the DTB would be sun8i-h3-orangepi-plus2e
Other than that, you might be lucky -- it may work!
OK well hopefully whoever said that has tested it, but just has not contributed back anything. There will be changes required to the installation settings since it's a newer revision of the board.
Presumably the DTB would be sun8i-h3-orangepi-plus2e
Other than that, you might be lucky -- it may work!
Hmm...that may make it a no go for me then. I don't have nearly as much time as I used to for tinkering around. Have you had experience with ODROID?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
