LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
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-24-2016, 03:00 PM   #76
nobodino
Senior Member
 
Registered: Jul 2010
Location: Near Bordeaux in France
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564

Rep: Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892

the build3_s.list and build3_d.list are not the latest working ones (several errors)
Replace with the enclosed ones.
Attached Files
File Type: txt build3_d.list.txt (829 Bytes, 39 views)
File Type: txt build3_s.list.txt (805 Bytes, 47 views)
 
1 members found this post helpful.
Old 05-24-2016, 11:07 PM   #77
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2, Slackware-from-Scratch
Posts: 241

Original Poster
Rep: Reputation: 45
Nobodino,

You might want to check the last entry to the attached diff file.
I haven't actually tested it yet. Haven't had enough time. Will get
to it in a day or three.

Also attached is the latest version of the LFS ch5 build for Slackware.
Eliminated the programs "dejagnu" and "check". It seems to work here.
Attached Files
File Type: txt sfsinit.diff.txt (4.1 KB, 36 views)
File Type: txt tools.txt (70.7 KB, 39 views)
 
2 members found this post helpful.
Old 05-27-2016, 05:12 PM   #78
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2, Slackware-from-Scratch
Posts: 241

Original Poster
Rep: Reputation: 45
Nobodino,

Question: Are the pre_elflibs and post_elflib routines in sfsbuild1.sh necessary
for building on x86_64? I can't seem to find any reference to them in the source
files, but admit I may have missed something.

If they are needed, then the packages in /home need to be different:
installpkg cxxlibs-6.0.18-x86_64-1.txz vs installpkg cxxlibs-6.0.18-i486-1.txz, etc.

Keep up the good work,

Worsel
 
Old 05-28-2016, 12:56 AM   #79
nobodino
Senior Member
 
Registered: Jul 2010
Location: Near Bordeaux in France
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564

Rep: Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892
you're right, I forgot to manage the case of x86_64 for pre_elf and post_elf.
For the time being, I'm trying to solve the new dep. for ghostscript which are not stabilized.
 
Old 05-30-2016, 01:15 PM   #80
nobodino
Senior Member
 
Registered: Jul 2010
Location: Near Bordeaux in France
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564

Rep: Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892
A new update:
- pre_elflibs and post_elflibs are ok for x86_64 now
- gcc can now be built completely
- builds without any hiccup.
Attached Files
File Type: txt sfsbuild1.sh.txt (66.5 KB, 35 views)
File Type: txt sfsinit.sh.txt (94.3 KB, 34 views)
 
Old 05-31-2016, 01:36 PM   #81
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2, Slackware-from-Scratch
Posts: 241

Original Poster
Rep: Reputation: 45
Nobodino,

In sfsbuild1.sh, under "# BUILD package treatment", shouldn't the xfce entry be
"cd /slacksrc/$SRCDIR/$PACKNAME && chmod +x xfce-build-all.sh && ./xfce-build-all.sh" instead of
"cd /slacksrc/$SRCDIR/$DIRNAME && chmod +x xfce-build-all.sh && ./xfce-build-all.sh"?

Haven't run it that far yet. It builds build1_s.list stuff just fine, except I still have the
problem of "/tools/bin/{perl,sh,bash}" being hard coded into some of the programs, forcing me to
recompile them after deleting the tools directory. Well, I'll find the answer eventually.
 
Old 05-31-2016, 02:04 PM   #82
nobodino
Senior Member
 
Registered: Jul 2010
Location: Near Bordeaux in France
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564

Rep: Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892
for xfce: $PACKNAME=$DIRNAME

for the rest? No answer for now:
- could you describe what's wrong exactly?
- which programs are involved?

Last edited by nobodino; 06-01-2016 at 12:37 AM. Reason: questions
 
Old 06-01-2016, 08:06 PM   #83
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2, Slackware-from-Scratch
Posts: 241

Original Poster
Rep: Reputation: 45
Ran the latest sfsinit.sh and sfsbuild1.sh.

Added a new gcc.SlackBuild. A patch to create it is attached. It differs from the old
SlackBuild in that it is complete in itself. Give it an argument and it only compiles
c, c++, and fortran. Run without an argument and it tries to compile everything.

Aside from my usual problems (see next reply), the following things went wrong:

1) The llvm patch seems wrong. It leaves us compiling llvm with gcc twice, instead of
compiling with clang the second time. Attached is a copy of the original patch.

2) Xfce looks for the build script in xfce/xfce. Removed the extra xfce.

A patch for these is attached.
Attached Files
File Type: txt gccSB.patch.txt (34.3 KB, 38 views)
File Type: txt llvmSB.patch.txt (1.4 KB, 33 views)
File Type: txt sfsbuild1.patch.txt (1.3 KB, 36 views)
 
Old 06-01-2016, 08:17 PM   #84
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2, Slackware-from-Scratch
Posts: 241

Original Poster
Rep: Reputation: 45
The problems I've been having are mostly related to references to /tools/bin are
hardcoded into the files after build1_s.list is run.

In addition, on the last build, find would not work. No matter what I looked for
it returned "File not found." When I recompiled it I also had to recompile bash,
can't remember why. Memo to self: Keep better notes.

After the compile, if I go to /usr/bin and 'grep "tools/bin", this is what I get:

Quote:
root:/usr/bin# grep "tools/bin" *
grep: X11: Is a directory
aclocal:#!/tools/bin/perl -w
aclocal:eval 'case $# in 0) exec /tools/bin/perl -S "$0";; *) exec /tools/bin/perl -S "$0" "$@";; esac'
aclocal-1.15:#!/tools/bin/perl -w
aclocal-1.15:eval 'case $# in 0) exec /tools/bin/perl -S "$0";; *) exec /tools/bin/perl -S "$0" "$@";; esac'
afmtodit:#! /tools/bin/perl -w
autoheader:#! /tools/bin/perl
autoheader:eval 'case $# in 0) exec /tools/bin/perl -S "$0";; *) exec /tools/bin/perl -S "$0" "$@";; esac'
autom4te:#! /tools/bin/perl -w
autom4te:eval 'case $# in 0) exec /tools/bin/perl -S "$0";; *) exec /tools/bin/perl -S "$0" "$@";; esac'
autom4te:my $m4 = $ENV{"M4"} || '/tools/bin/m4';
automake:#!/tools/bin/perl -w
automake:eval 'case $# in 0) exec /tools/bin/perl -S "$0";; *) exec /tools/bin/perl -S "$0" "$@";; esac'
automake-1.15:#!/tools/bin/perl -w
automake-1.15:eval 'case $# in 0) exec /tools/bin/perl -S "$0";; *) exec /tools/bin/perl -S "$0" "$@";; esac'
autoreconf:#! /tools/bin/perl -w
autoreconf:eval 'case $# in 0) exec /tools/bin/perl -S "$0";; *) exec /tools/bin/perl -S "$0" "$@";; esac'
autoscan:#! /tools/bin/perl -w
autoscan:eval 'case $# in 0) exec /tools/bin/perl -S "$0";; *) exec /tools/bin/perl -S "$0" "$@";; esac'
autoupdate:#! /tools/bin/perl -w
autoupdate:eval 'case $# in 0) exec /tools/bin/perl -S "$0";; *) exec /tools/bin/perl -S "$0" "$@";; esac'
autoupdate:my $m4 = $ENV{"M4"} || '/tools/bin/m4';
Binary file bison matches
c_rehash:#!/tools/bin/perl
Binary file flex matches
Binary file flex++ matches
grog:#! /tools/bin/perl
gropdf:#!/tools/bin/perl -w
ifnames:#! /tools/bin/perl -w
ifnames:eval 'case $# in 0) exec /tools/bin/perl -S "$0";; *) exec /tools/bin/perl -S "$0" "$@";; esac'
Binary file lex matches
libtool:SED="/tools/bin/sed"
libtool:GREP="/tools/bin/grep"
libtool:EGREP="/tools/bin/grep -E"
libtool:FGREP="/tools/bin/grep -F"
libtool:NM="/tools/bin/nm -B"
libtool:lt_truncate_bin="/tools/bin/dd bs=4096 count=1"
libtool:LD="/tools/bin/ld -m elf_x86_64"
libtool:LD="/tools/bin/ld -m elf_x86_64"
libtool:LD="/tools/bin/ld -m elf_x86_64"
libtool:LD="/tools/bin/ld -m elf_x86_64"
libtoolize:: ${EGREP="/tools/bin/grep -E"}
libtoolize:: ${FGREP="/tools/bin/grep -F"}
libtoolize:: ${GREP="/tools/bin/grep"}
libtoolize:: ${SED="/tools/bin/sed"}
makeinfo:#! /tools/bin/perl
mmroff:#! /tools/bin/perl
mtrace:#! /tools/bin/perl
mtrace:eval "exec /tools/bin/perl -S $0 $@"
pdfmom:#!/tools/bin/perl -w
pod2texi:#! /tools/bin/perl
texi2any:#! /tools/bin/perl
grep: x86_64-slackware-linux-gcj: No such file or directory
grep: x86_64-slackware-linux-gcjh: No such file or directory
zgrep:grep='${GREP-'\''/tools/bin/grep'\''}'
These can be corrected by recompiling the following programs:
Quote:
d libtool
a gzip
a bzip2
d bison
d flex
d autoconf
d automake
a grep
ap groff
ap texinfo
n openssl
ap man-pages
l glibc
Since you don't seem to be having this problem, I assume it is coming from
the ch5 build, but I can't seem to find anything wrong there.

Any ideas would be appreciated.
 
Old 06-02-2016, 01:18 AM   #85
nobodino
Senior Member
 
Registered: Jul 2010
Location: Near Bordeaux in France
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564

Rep: Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892
The messages with grep "tools/bin *" are the same here. I'll look into it.
Don't bother with chapter 5.

1/ llvm builds fine , on the second pass, it's "build1" which is used (so llvm.SlackBuild.old)
 
Old 06-03-2016, 11:14 AM   #86
nobodino
Senior Member
 
Registered: Jul 2010
Location: Near Bordeaux in France
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564

Rep: Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892
Here is something solving your problems with (grep 'tools/bin' *) not empty.
Not the smartest manner, but it works.
The remaining message should go with the gcc-all build.
Attached Files
File Type: txt sfsinit.sh.txt (94.8 KB, 38 views)
File Type: txt sfsbuild1.sh.txt (67.0 KB, 30 views)
 
Old 06-05-2016, 01:31 AM   #87
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2, Slackware-from-Scratch
Posts: 241

Original Poster
Rep: Reputation: 45
Quote:
Not the smartest manner, but it works.
I'll keep looking for a more elegant solution.
However, it is possible there is none.

Just finished running sfsbuild1_s.list. Everything
looks good right now.

Thanks.

Last edited by worsel; 06-05-2016 at 01:31 AM. Reason: Spelling
 
Old 06-05-2016, 04:08 AM   #88
nobodino
Senior Member
 
Registered: Jul 2010
Location: Near Bordeaux in France
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564

Rep: Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892Reputation: 892
gcc_build and gcc_build64 have to be modified due to your new gccSB.patch.
See the enclosed file.
Attached Files
File Type: txt sfsbuild1.txt (67.1 KB, 34 views)
 
Old 06-09-2016, 12:31 AM   #89
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2, Slackware-from-Scratch
Posts: 241

Original Poster
Rep: Reputation: 45
Okay, just finished building xfce using the latest sfsbuild1.sh & sfsinit.sh

Had to rebuild findutils and bash again. Findutils to continue after build1_s.list,
because it gave error messages instead of finding files. Bash worked all the way
until building gcc-all, then the program couldn't find gnat.

Must apologize again. The last gcc.SlackBuild patch I sent was the wrong one. The correct one
is attached, along with diff files for sfsbuild1 & sfsinit. As usual, ignore pathnames.
Attached Files
File Type: txt gccSB.patch.txt (40.6 KB, 34 views)
File Type: txt sfsbuild1.patch.txt (2.4 KB, 43 views)
File Type: txt sfsinit.patch.txt (82.9 KB, 30 views)
 
Old 06-09-2016, 01:41 AM   #90
hendrickxm
Member
 
Registered: Feb 2014
Posts: 344

Rep: Reputation: Disabled
I am following this thread with a lot of interest.
I read through most scripts and I wonder why some packages are installed/build. It seems to me a few are not needed.
Some examples: rpm and rp2tgz might be usefull but I don't think these are needed to build other packages.
bin (probably needed)
help2man (probably for docs/man)
slacktrack (needed for linuxdoc-tools which is needed for docs)
tetex and tetex-doc and ed (probably to build some docs)
mc and thus slang/slang1 (I do not need mc)
some internationalization and libs like dmapi, libidn
mm
svgalib
lvm2 for a desktop install?
ncftp and lftp
dhcp and dhcpcd

Probably a few more and they could probably be removed if you do not install all docs and thus edit a lot of slackbuilds.
libpthread-stubs can be removed if you add a sed
Code:
sed -i "s/pthread-stubs//" configure &&
to some configure files.
 
  


Reply



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 09:44 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
Open Source Consulting | Domain Registration