LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 06-22-2016, 07:35 PM   #31
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,142

Rep: Reputation: 158Reputation: 158

Quote:
Originally Posted by OldHolborn View Post
Some of the questions being asked look like apprentice sandwich maker level questions being asked of a top chef, maybe some of those questions are best directed at google...
Very good analogy.
 
Old 06-22-2016, 09:36 PM   #32
enine
Senior Member
 
Registered: Nov 2003
Distribution: Slackware 14.2, SlackwareArm-current
Posts: 1,217
Blog Entries: 4

Rep: Reputation: 183Reputation: 183
Was more of a thinking out loud than asking and stopping to figure out what for dinner.
I realize now since I'm on a RPi I used their kernel so I don't have the config or the headers or anything.
 
Old 06-22-2016, 10:06 PM   #33
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,142

Rep: Reputation: 158Reputation: 158
Quote:
Originally Posted by enine View Post
Was more of a thinking out loud than asking and stopping to figure out what for dinner.
I realize now since I'm on a RPi I used their kernel so I don't have the config or the headers or anything.
I wonder if it's easier to rebuild glibc, and then slowly rebuild everything to hard float? At least some of the DE and WM along with some of the applications. I'm going to start doing that tomorrow and see how it goes.
 
Old 06-22-2016, 10:17 PM   #34
enine
Senior Member
 
Registered: Nov 2003
Distribution: Slackware 14.2, SlackwareArm-current
Posts: 1,217
Blog Entries: 4

Rep: Reputation: 183Reputation: 183
Thats what I was thinking. But for the glibc rebuild I'm going to have to pull more bits from the rasbain image I got the install from.

I'm running the minirootfs rather than the full install on both my Pi3's as I did that before the fatdog full installer was available. So when i just upgraded the 2 to the second 3 I rebuilt the 2 with the minirootfs as well. Just have the other 2 and the 1 to go now. This gives me <100 packages. Going back to see how to set up my own Slackpkg repo and I'll use the latest minirootfs as the source then as packages in it get upgraded in the full I'll built that package hardfloat and move into my minirootfs repo.
Mine are all "servers" so no DE or desktop apps.

Thats the plan anyway, after I get some sleep it might not make any sense
 
Old 06-22-2016, 10:20 PM   #35
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,142

Rep: Reputation: 158Reputation: 158
Quote:
Originally Posted by enine View Post
Thats what I was thinking. But for the glibc rebuild I'm going to have to pull more bits from the rasbain image I got the install from.

I'm running the minirootfs rather than the full install on both my Pi3's as I did that before the fatdog full installer was available. So when i just upgraded the 2 to the second 3 I rebuilt the 2 with the minirootfs as well. Just have the other 2 and the 1 to go now. This gives me <100 packages. Going back to see how to set up my own Slackpkg repo and I'll use the latest minirootfs as the source then as packages in it get upgraded in the full I'll built that package hardfloat and move into my minirootfs repo.
Mine are all "servers" so no DE or desktop apps.

Thats the plan anyway, after I get some sleep it might not make any sense
Sounds like a great plan. My experience with messing with minirootfs is zero. I have to start somewhere, right? I'll be doing some reading tomorrow. Headed to bed also now.
 
Old 06-23-2016, 03:07 AM   #36
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 854

Original Poster
Rep: Reputation: 642Reputation: 642Reputation: 642Reputation: 642Reputation: 642Reputation: 642
Quote:
Originally Posted by enine View Post
Code:
Extracting Linux Kernel headers into /root/tmp/build-glibc
tar: /root/slackwarearm-current/source/l/glibc/../../d/kernel-headers/sources/kernel-headers-4.4.8.tar.xz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
  glibc-2.23-arm-3.txz.build.log:  3.361:1,  2.380 bits/byte, 70.25% saved, 2773 in, 825 out.
OIC, 4.4.13 is in current-now, what is telling it to look for 4.4.8 slackkit?
It's not 4.4.8 slackkit, it's 4.4.8 of the Kernel headers. I'd had a cleaning session and must have become over zealous and wiped the older versions of the headers out. You can change glibc.SlackBuild to use 4.4.13 headers instead, which is now what I've done in the source tree.
 
Old 06-23-2016, 06:18 AM   #37
enine
Senior Member
 
Registered: Nov 2003
Distribution: Slackware 14.2, SlackwareArm-current
Posts: 1,217
Blog Entries: 4

Rep: Reputation: 183Reputation: 183
Quote:
Originally Posted by drmozes View Post
It's not 4.4.8 slackkit, it's 4.4.8 of the Kernel headers. I'd had a cleaning session and must have become over zealous and wiped the older versions of the headers out. You can change glibc.SlackBuild to use 4.4.13 headers instead, which is now what I've done in the source tree.
That was supposed to be written "what is telling it to look for 4.4.8, slackkit" I was meaning is slackkit where the version is specified or was it glibc. I found my issue though right after that. Since I'm running just the minitrootfs and on a Pi I don't have the header sources which was easy enough to add but I also don't have it in usr/lib since I'm not using the slackware compiled kernel but using rasbains's inserted into the minirootfs.

So I need to pull rasbians config and compile the kernel to get the headers made again
http://docs.slackware.com/howtos:sla...kernelbuilding

Anyone running a Pi from the fatdog installer, can you check and see if you have the headers, i.e. did fatdog compile a kernel or did they just stick rasbain's in their installer. I'm at work and don't have ssh open to my home at the moment to check.

and for the record I'm not asking the top chef apprentice level questions (such as how to compile a kernel though I admit its been a long time since I've done so out of slack^D^D^D^D^Dlazyness) . I'm trying to document my thought process so others can follow if they are interested. Perhaps I should move my (probably incoherent) ramblings to another thread or LQ blog and leave this as a thank you thread for those who have supported arm so far.

Last edited by enine; 06-23-2016 at 06:26 AM.
 
Old 06-23-2016, 07:01 AM   #38
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 854

Original Poster
Rep: Reputation: 642Reputation: 642Reputation: 642Reputation: 642Reputation: 642Reputation: 642
Quote:
Originally Posted by enine View Post
That was supposed to be written "what is telling it to look for 4.4.8, slackkit" I was meaning is slackkit where the version is specified or was it glibc. I found my issue though right after that. Since I'm running just the minitrootfs and on a Pi I don't have the header sources which was easy enough to add but I also don't have it in usr/lib since I'm not using the slackware compiled kernel but using rasbains's inserted into the minirootfs.

So I need to pull rasbians config and compile the kernel to get the headers made again
If you look at glibc.SlackBuild and look at the error you pasted in, you'll see that it's not using the system headers, it's set up to extract the archived headers (from a previous kernel build by me) from the source/d/kernel-headers/sources directory and use those instead. This is different from x86 because of a legacy reason (before ARM was mainstream there was the master kernel.org and RMK's (the ARM kernel maintainer)'s tree, and some packages needed more recent headers than RMK's kernel had -- yet I needed RMK's kernel for the ARM system support, and so I had a mixture of headers from different Kernel versions (which is a "bad thing")-- it's just the way it was back then for the distributions)). This also means it's easier to boot strap since I just drop an archive of headers in place, and it'll use those rather than the system ones -- less to figure out next time around (as is the case now).

Last edited by drmozes; 06-23-2016 at 07:04 AM.
 
Old 06-23-2016, 09:26 AM   #39
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,142

Rep: Reputation: 158Reputation: 158
I'm in the process of rebuilding glibc now. As for rebuilding other packages with hard float, should I be using the following cflags?
Code:
CFLAGS = -O2 -mfloat-abi=hard -march=native -mtune=native
Perhaps it's time to open a new thread about this.
 
Old 06-23-2016, 11:18 AM   #40
enine
Senior Member
 
Registered: Nov 2003
Distribution: Slackware 14.2, SlackwareArm-current
Posts: 1,217
Blog Entries: 4

Rep: Reputation: 183Reputation: 183
Quote:
Originally Posted by drmozes View Post
If you look at glibc.SlackBuild and look at the error you pasted in, you'll see that it's not using the system headers, it's set up to extract the archived headers (from a previous kernel build by me) from the source/d/kernel-headers/sources directory and use those instead. This is different from x86 because of a legacy reason (before ARM was mainstream there was the master kernel.org and RMK's (the ARM kernel maintainer)'s tree, and some packages needed more recent headers than RMK's kernel had -- yet I needed RMK's kernel for the ARM system support, and so I had a mixture of headers from different Kernel versions (which is a "bad thing")-- it's just the way it was back then for the distributions)). This also means it's easier to boot strap since I just drop an archive of headers in place, and it'll use those rather than the system ones -- less to figure out next time around (as is the case now).
Ok, lack of sleep due to last nights storm I'm being a little slow.

In the official SlackwareARM kernel source and kernel headers packages which headers do I get the source/d or system. I thought originally it was just missing the source/d headers so all I have to do is install the packages and they would be there. But then I started thinking you probably compiled the official kernel differently otherwise I could just boot off an unmodified minirootfs so I need to grab raspbain's config anyway.

I bet if I boot up the other Pi2 with the full (fatdog) install the "missing" headers will be there, I'm probably just missing stuff from the full that not in the minirootfs. (must stop posting from work where I can't see my Pi's, Or get a display for the zero sitting in my backpack )

saw the other thread now about recompiling glibc, since I'm running mine as servers then the hard/soft issue doesn't really matter to me. So I can just make my own repo and if/when 14.2 support ends just manually build packages myself as necessary.

Last edited by enine; 06-23-2016 at 06:28 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware ARM (current) epic mistake: the current Android kernels are kicked out! Darth Vader Slackware 16 08-25-2013 04:36 PM
Slackware Release End-Of-Life Policy mrtwice Slackware 15 05-16-2008 04:19 AM
LXer: openMosix Project End of Life Announcement LXer Syndicated Linux News 1 07-16-2007 04:33 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 09:50 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration