LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-04-2016, 01:18 AM   #61
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2
Posts: 176

Original Poster
Rep: Reputation: 34

Nobodino,

Disregard the patch for sfsinit.sh that I sent on 4-30. I was, apparently, not careful enough when
cleaning up after trouble-shooting and got an erroneous result.

The reasons it wouldn't boot was because "make oldconfig" went through without a hitch, instead of asking
if I wanted various things. This meant that the local version value was "" instead of "-smp". The kernel
couldn't find the modules.

Lines 35-42 in the attached file are what I did to correct it. Don't know why the configure process didn't
work right the first time, but the configure files are different for 32 and 64 bit.

Worsel
Attached Files
File Type: txt kernel.SlackBuild.txt (2.6 KB, 18 views)

Last edited by worsel; 05-04-2016 at 01:20 AM. Reason: Attachment not attached.
 
Old 05-04-2016, 01:29 AM   #62
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint, Niresh (MacOS)...
Posts: 313

Rep: Reputation: 223Reputation: 223Reputation: 223
Worsel:

could you test these new versions:
- change $LFS to $SFS as in your scripts
- just adapt to your $PATH
- remove all personal settings
- created the kernel.SlackBuild64 for x86_64
- builds cleanly on x86
- nota : 2 tools directories : tools and tools_64

nota2: I'll adapt sfsinit.sh with your new patch for kernel.SlackBuild, and see if works ok.
Attached Files
File Type: txt sfsinit.sh.txt (96.9 KB, 19 views)
File Type: txt sfsbuild1.sh.txt (22.9 KB, 19 views)

Last edited by nobodino; 05-04-2016 at 01:38 AM. Reason: your previous answer
 
Old 05-04-2016, 11:48 PM   #63
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2
Posts: 176

Original Poster
Rep: Reputation: 34
Nobodino,

Have you been having any trouble with autoconf, automake, m4, and libtool?

When I finish your previous script, these still refer to /tools/bin, which has been
deleted. When I recompile them, they work properly. I have been unable to
find a reason for this behavior. It could be in your script or in the ch5 build,
or something off in my computer. That really narrows it down

Worsel
 
Old 05-05-2016, 01:04 AM   #64
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint, Niresh (MacOS)...
Posts: 313

Rep: Reputation: 223Reputation: 223Reputation: 223
make a short build list which stops after gettext building, and build "at hand" the first culprit "libtool" and compare its building with the script with only libtool, and progress until you find or not the culprit?
 
Old 05-05-2016, 03:04 AM   #65
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint, Niresh (MacOS)...
Posts: 313

Rep: Reputation: 223Reputation: 223Reputation: 223
this time this kernel.SlackBuild works on both environment x86 and x86_64 (just tested this morning), and even in non chroot environment:test it outside $SFS to see the result.
Attached Files
File Type: txt kernel.SlackBuild.txt (3.0 KB, 20 views)
 
Old 05-08-2016, 01:48 AM   #66
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2
Posts: 176

Original Poster
Rep: Reputation: 34
Nobodino,

Your latest sfsinit.sh and sfsbuild1.sh seem to work as advertised. I didn't try the
dlackware part. Except for the problem outlined below, everything seemed to be ok.

Still having trouble with autoconf, etc. Most of the ones giving me trouble (perhaps all of them)
are scripts. Instead of the first line in the script being "#! /bin/whatever" it is "#! /tools/bin/whatever".
Doesn't matter if it's a perl, python, or sh script.

It doesn't show up until I try to compile X. The only way I can cure it is to run sfsbuild1.sh, the rebuild the
offending packages.

Guess I'll work on it tomorrow. It's almost midnight here and I need my beauty sleep.

Worsel

Last edited by worsel; 05-08-2016 at 01:49 AM. Reason: spelling error
 
Old 05-09-2016, 01:24 AM   #67
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2
Posts: 176

Original Poster
Rep: Reputation: 34
Nobodino,

I did notice one thing on your scripts. The kernel build place the modules in /lib/modules but also
puts a duplicate directory in /lib. I couldn't see where your script was the cause, so maybe the
problem is in the SlackBuild.

I've narrowed down my problem. Don't know why yet, but I know what is affected. The following packages
are built with "/lib/tools/bin/whatever" built in:

Quote:
d libtool
d bison
d flex
d autoconf
d automake
a grep
ap groff
a gzip
ap texinfo
n openssl
ap man-pages
l glibc
I can cure them by deleting the tools directory and recompiling the packages
in the order shown. Since we're using nearly identical scripts, (My last build
was with your latest using slackware-current dated 2016-05-05), I'm curious as
to why you aren't having the same problem. By the way, it doesn't show up
until one tries to build X.

Worsel

Last edited by worsel; 05-09-2016 at 01:25 AM. Reason: spelling error
 
Old 05-10-2016, 01:00 AM   #68
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint, Niresh (MacOS)...
Posts: 313

Rep: Reputation: 223Reputation: 223Reputation: 223
Could you test the building of x86_64 with this build1_s.list.

If your LFS is too new (gzip >1.6, makepkg doesn't like very much: weird messages, same thing for findutils if >4.4.2).

To build a x86_64 system, I had to modify slightly the order of packages, and to build twice some packages to be able to boot.
Concerning the kernel, I've not solved the problem for the time being, but I've two ideas to solve it.
Attached Files
File Type: txt build1_s.list.txt (1.7 KB, 20 views)

Last edited by nobodino; 05-10-2016 at 01:39 AM. Reason: typo
 
Old 05-11-2016, 12:39 AM   #69
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2
Posts: 176

Original Poster
Rep: Reputation: 34
Your latest build1_s.list built ok, or, maybe better stated, ran to completion.

Actually, glibc built this time without "/tools/bin/" imbedded in xtrace, but
now find (from findutils) and binutils had to be recompiled at the beginning of
the list from my last sending.

I haven't tried compiling X yet. Will try it tomorrow.
 
Old 05-14-2016, 05:41 PM   #70
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2
Posts: 176

Original Poster
Rep: Reputation: 34
Was able to build X all the way through xfce in Nobodino's lists.
The base system was built by Nobodino's sfsbuild1.sh on a 64 bit system.
The sources where slackware64-current, synced 20160505.

Some problems encountered:

1. Had to move xtrans up before xpby and libFS in the build list

2. libva-intel-driver needs "--without-wayland" added to the configure
parameters. Haven't made a patch for this yet.

3. p2c was not changed to p2c-1.22 in Nobodino's script.

4. Tix failed to build. Complained it couldn't find /usr/include/tclInt.h
which was there in plain sight.

5. The rcsSB patch failed to apply, even though it was in Nobodino's script.
Haven't looked into this one yet.

6. A full gcc build (ada, c, c++, fortran, go, java, lto, objc) failed.
The #@$%& thing worked last time I tried it.

Anyway, both blackbox and xfce seemed to work normally. Going to take a
few days off of this now. Got things to do. You know : balance the checkbook,
play with the grandkids, woo the girlfriend, etc.
 
1 members found this post helpful.
Old 05-16-2016, 01:46 AM   #71
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint, Niresh (MacOS)...
Posts: 313

Rep: Reputation: 223Reputation: 223Reputation: 223
a new update to the scripts for building "slackware from scratch", the four configurations have been tested on x86/x86_64 with slackware/dlackware, they build and boot correctly.
The kernels are now real packages.
Everything about kernels (headers, modules and kernel) has been moved from sfsinit.sh to sfsbuild1.sh, it's cleaner.
Worsel: concerning the rcs patch, a typo changed the "rcs" in "rsc", that's why it didn't work I looked forward a long time before I found it.

Now I can go on for the second part, build x11/xfce...
Attached Files
File Type: txt sfsinit.sh.txt (87.2 KB, 18 views)
File Type: txt sfsbuild1.sh.txt (28.4 KB, 16 views)
 
1 members found this post helpful.
Old 05-17-2016, 02:56 PM   #72
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint, Niresh (MacOS)...
Posts: 313

Rep: Reputation: 223Reputation: 223Reputation: 223
sfsinit updated with the patch for libva-intel-driver.
Attached Files
File Type: txt sfsinit.txt (88.5 KB, 14 views)
 
Old 05-18-2016, 05:27 AM   #73
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint, Niresh (MacOS)...
Posts: 313

Rep: Reputation: 223Reputation: 223Reputation: 223
by changing the destination of "others" directory, it got wiped before being used.
This version has the new patch, and "others" is usable for building x11.
Attached Files
File Type: txt sfsinit.txt (88.8 KB, 15 views)
 
Old 05-19-2016, 01:08 AM   #74
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint, Niresh (MacOS)...
Posts: 313

Rep: Reputation: 223Reputation: 223Reputation: 223
Worsel: one step forward

Your problems 1/, 2/, 4/ and 5/ should be solved with this.
It builds up to blackbox with the build2_s.list. Only tested on x86 and slackware, not for dlackware.
Don't forget to exit chroot environment and run ./chroot1.sh to have plain $PATH before building x11.

You can delete /tools directory before building X11, it' not necessary anymore.

error: in chroot1.sh: change the first line to '#!/bin/sh' and not '#!/bin.sh'
Attached Files
File Type: txt chroot1.sh.txt (132 Bytes, 23 views)
File Type: txt build2_s.list.txt (579 Bytes, 23 views)
File Type: txt sfsbuild1.sh.txt (62.5 KB, 15 views)
File Type: txt sfsinit.txt (91.4 KB, 16 views)

Last edited by nobodino; 05-20-2016 at 01:26 AM. Reason: small error in chroot1.sh
 
Old 05-24-2016, 01:35 AM   #75
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint, Niresh (MacOS)...
Posts: 313

Rep: Reputation: 223Reputation: 223Reputation: 223
new updates:
- builds up to xfce on slackware and dlackware and both architectures x86 and x86_64.

To be tested by someone else.
Attached Files
File Type: txt sfsbuild1.sh.txt (64.5 KB, 20 views)
File Type: txt sfsinit.sh.txt (94.8 KB, 15 views)
File Type: txt chroot1.sh.txt (132 Bytes, 16 views)
 
1 members found this post helpful.
  


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
[SOLVED] /usr/bin/X11/X11/....... 10 X11 subsets & counting walter74 Linux - General 2 06-07-2015 12:36 AM
How do I get the /etc/X11/X file rebuilt from scratch rickh Debian 4 05-07-2006 11:06 PM
ali aladdin v agp stinks :scratch: :scratch: :scratch: Mr Marmmalade Linux - Hardware 1 07-08-2003 05:11 AM

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

All times are GMT -5. The time now is 08:34 PM.

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