Slackware - ARM This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
11-04-2017, 04:51 PM
|
#16
|
Senior Member
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,278
Original Poster
|
Cubieboard is even faster, but a little bit more expensive. I'll have to find some time to tinker around.
Looking at this one.
|
|
|
11-06-2017, 01:19 PM
|
#17
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,710
|
Quote:
Originally Posted by stormtracknole
Have you had experience with ODROID?
|
No - everything I have is what's documented as officially supported, apart from the Chromebook which I took the soldering iron to and didn't yet manage to unlock.
I think someone else has with the ODROID though - I'm sure that I have seen it mentioned on this forum.
|
|
|
11-07-2017, 06:57 AM
|
#18
|
Senior Member
Registered: Dec 2003
Location: Paris
Distribution: Slackware forever.
Posts: 2,538
Rep: 
|
Have an Odroid XU-4.
I'm not fond of it, setting up a rootfs is a pain as you need to copy data on empty space at the start of the SD/MMC. The ventirad is also a joke as the CPU hangs your system when overheating. Needs to be changed if you want to use the really powerful processor.
That said, you can compile and use a mainstream kernel, which is a good thing.
That's why you should stay away from boards with allwinner chips.
|
|
|
11-07-2017, 09:50 AM
|
#19
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,710
|
Quote:
Originally Posted by Linux.tar.gz
Have an Odroid XU-4.
I'm not fond of it, setting up a rootfs is a pain as you need to copy data on empty space at the start of the SD/MMC. The ventirad is also a joke as the CPU hangs your system when overheating. Needs to be changed if you want to use the really powerful processor.
That said, you can compile and use a mainstream kernel, which is a good thing.
That's why you should stay away from boards with allwinner chips.
|
The Orange Pi, Banana Pi both have Allwinner CPUs. The way that the system is configured is up to the manufacturer.
|
|
|
11-07-2017, 10:05 AM
|
#20
|
Senior Member
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,278
Original Poster
|
I thought I read somewhere that the company that develops the Allwinner CPUs is in violation of the GPL?
|
|
|
11-07-2017, 10:25 AM
|
#21
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,710
|
Quote:
Originally Posted by stormtracknole
I thought I read somewhere that the company that develops the Allwinner CPUs is in violation of the GPL?
|
That rings a bell, but I don't see how it'd have anything to do with the hardware. It's probably some Kernel modules that were modified and released in binary form only, or something like that.
Regarding gcc -- I'm rebuilding gcc without any of the Debian patches: One of the issues with including so many patches is that you cannot submit bug reports to GCC upstream, but if it still breaks without the patches applied, you can submit a bug report safe in the knowledge that it's the original source (with just one patch that's included with x86 Slackware).
As it turns out, I didn't rebuild libtool when I changed the toolchain target name, which caused all gcc builds to fail. Took me a while to figure out that it was libtool!
Last edited by drmozes; 11-07-2017 at 10:58 AM.
|
|
|
11-10-2017, 08:37 PM
|
#22
|
Senior Member
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,278
Original Poster
|
I upgraded gcc to the latest version of -current. I tried building mame again, and I finally cleared the previous error. However, I was getting a different set of errors and the build would fail at different points. It was never consistent. This lead me to believe that I might have been running out of swap space. So, went ahead and added another Gigabyte of swap and that finally allowed me to build it. Thank you so much for your help drmozes!!
|
|
|
11-11-2017, 02:26 AM
|
#23
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,710
|
Quote:
Originally Posted by stormtracknole
I upgraded gcc to the latest version of -current. I tried building mame again, and I finally cleared the previous error. However, I was getting a different set of errors and the build would fail at different points. It was never consistent. This lead me to believe that I might have been running out of swap space. So, went ahead and added another Gigabyte of swap and that finally allowed me to build it. Thank you so much for your help drmozes!!
|
Good to hear! The "killed" part of the log normally means it was killed by the memory manager (I didn't notice that first time) -- checking dmesg would confirm that.
|
|
|
11-13-2017, 07:25 AM
|
#24
|
Senior Member
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,278
Original Poster
|
Quote:
Originally Posted by drmozes
Good to hear! The "killed" part of the log normally means it was killed by the memory manager (I didn't notice that first time) -- checking dmesg would confirm that.
|
Hmmm...very possible and I should have thought of that earlier. Anyhow, removing your Debian patches did not break anything here at least. So, that's good.
If anyone is interested, I can post my mame package along with the source if anyone is interested.
|
|
|
All times are GMT -5. The time now is 01:04 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|