Re: [lfs-support] Cannot rebuild GMP-6.1.2

2021-01-23 Thread Pol Vangheluwe 


> Op 22 jan. 2021, om 22:00 heeft Ken Moffat  het 
> volgende geschreven:

> (…)

> My .sig typically changes at the start of a month and mid month, and
> is usually intended to be humorous.  My current .sig is NOT a
> citation or quote.  But perhaps you think that arming bears will
> lead to situations like this Far Side cartoon:
> https://www.pinterest.com/pin/329677635200815374/ (A bear walks into
> a bar)
> 
As several people here pointed out that GMP-6.1.2 cannot be the culprit for the 
exception that occurred during the boot process,
I continued tuning the kernel config and found finally a combination that could 
boot the machine.

Details are not relevant, as this is not a PPC forum, but anyway, thanks to all 
who replied.

I now have LFS-8.1 running on the PowerMac-G3-Server, after transfer form the 
iMac-G3.
The G3-Server is a “difficult” machine, but I eventually tamed that armed bear…

pvg

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Cannot rebuild GMP-6.1.2

2021-01-21 Thread Pol Vangheluwe 


> Op 21 jan. 2021, om 18:32 heeft Ken Moffat  het 
> volgende geschreven:
> 
> On Thu, Jan 21, 2021 at 01:21:15PM +0100, Pol Vangheluwe wrote:
>>  (…)

>> - the CPU is not exactly the same.  The PowerMac has revision: 2.2 
>> (pvr 0008 0202), while the iMac has revision  : 2.2 (pvr 0008 0202)
> 
> I think you've quoted the same data twice ?  When I had a ppc G3
> linux laptop I think that the CPU was described as '750' and that
> was one of the last of the G3s.  But that was a very long time ago
> so I don't think I can help re CPU differences, although both will
> be incredibly slow by modern standards.

oops … I indeed made a copy/paste error.
This is the full cpuinfo for the donor machine (reported by LFS):

pol@iMac-G3:/sources/gmp-6.1.2$ cat /proc/cpuinfo
processor   : 0
cpu : 740/750
clock   : 400.00MHz
revision: 131.0 (pvr 0008 8300)
bogomips: 49.93
timebase: 24967326
platform: PowerMac
model   : PowerMac2,1
machine : PowerMac2,1
motherboard : PowerMac2,1 MacRISC2 MacRISC Power Macintosh
detected as : 66 (iMac FireWire)
pmac flags  : 0014
L2 cache: 512K unified
pmac-generation : NewWorld
Memory  : 1024 MB

and for the recipient machine (reported by Ubuntu):

pol@PowerMac-G3:~$ cat /proc/cpuinfo 
processor   : 0
cpu : 740/750
temperature : 38-40 C (uncalibrated)
clock   : 400.00MHz
revision: 2.2 (pvr 0008 0202)
bogomips: 49.87

total bogomips  : 49.87
timebase: 24935383
platform: PowerMac
model   : PowerMac1,1
machine : PowerMac1,1
motherboard : PowerMac1,1 MacRISC Power Macintosh
detected as : 66 (Blue&White G3)
pmac flags  : 
L2 cache: 1024K unified
pmac-generation : NewWorld
Memory  : 1024 MB

Yes, these are slow machines, compared to what we are used to today.
That’s why I am now considering (as a future project) to cross-compile the 
newest LFS for G3-32bit on a G5-64bit machine (running LFS-10.0)
And it is not only a matter of speed, I am also afraid that it is not possible 
anymore to compile the compiler with only 1GB of RAM.
> 
> The current (5.10.9) kernel docs are in rst format in the kernel's
> Documentation/powerpc directory.  I'm not sure what kernel you are
> running, and the docs used to be in different formats, but I can see
> from cpu_families.rst that there were variants of the 750 (755,
> 750CX, 750CL, 750FX).  I don't recall if the CPU variant got
> specified in the kernel config when I was building on ppc32, but
> looking at cpu_features.rst suggests this gets setup automatically
> in early boot so that one kernel can cover several variations of the
> hardware.

See above for details about the G3-flavours.

> 
> Therefore, for getting a working kernel config I think that you
> really need to look at the help for all of the mac options, and
> remove what is not present and add what is present but not enabled.

I mostly start the kernel configuration with “make pmac32_defconfig".
If this does not boot, then I start tuning from this base configuration.

> (…)

> An alternative for kernel configuration would be to use lspci and
> lsmod in ubuntu to see what is present, and to use that as the
> starting point - build-in devices which are present and in use,
> leave the rest as modules.

Yes, indeed.  Although distributions like Ubuntu compile a broad set of 
mission-critical modules directly in the kernel.
But as they also use INITRAMFS, there could be additional modules loaded that 
this machine needs.
Will have a look in the output of 'lsmod’.

> (…)

> I can recall a few problems in the less-distant past where there
> were problems with include_next in C++.  I'm sure there have been
> more recent reports.  The first relevant item found by duckduckgo
> was apparently from about 3 years ago,
> https://blfs-dev.linuxfromscratch.narkive.com/so2k0krL/math-h-no-such-file-or-directory-from-gcc
>  
> <https://blfs-dev.linuxfromscratch.narkive.com/so2k0krL/math-h-no-such-file-or-directory-from-gcc>
> and there Pierre suggested that some headers might have been
> 'include-fixed' when they should not have been.
> 
> At that time he suggested running
> /usr/libexec/gcc/x86_64-pc-linux-gnu/7.3.0/install-tools/mkheaders
> 
> Obviously your version and triplet will differ, and it's possible
> that LFS had not moved to using /usr/libexec when LFS-8.1 was
> created (I think we used to try to force /usr/lib).
> 
> Before replying, I tried google and found what I was thinking of:
> https://www.mail-archive.com/blfs-support@lists.linuxfromscratch.org/msg07176.html
>  
> <https://www.mail-archive.com/blfs-support@lists.lin

Re: [lfs-support] Cannot rebuild GMP-6.1.2

2021-01-21 Thread Pol Vangheluwe 


> Op 21 jan. 2021, om 17:51 heeft Xi Ruoyao  het 
> volgende geschreven:
> 
(…)

> Well the problem is "facsinating" (I mean, troubling).
> 
> Could you try
> 
>  echo "" | cpp -v
> 
> And check the output?  It should contains lines like
> 
>> #include "..." search starts here:
>> #include <...> search starts here:
>> /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/include
>> /usr/local/include
>> /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/include-fixed
>> /usr/include
> 
> Of course your output shouldn't contain x86_64 :).  Just check if /usr/include
> is there.

This is the outcome on the “donor” machine (running plain LFS, not in chroot 
from Ubuntu):

pol@iMac-G3:/sources/gmp-6.1.2$ echo "" | cpp -v
Ingebouwde specs worden gebruikt.
COLLECT_GCC=cpp
Target: powerpc-unknown-linux-gnu
Configured with: ../configure --prefix=/usr --enable-languages=c,c++ 
--disable-multilib --disable-bootstrap --with-system-zlib
Thread model: posix
gcc versie 7.3.0 (GCC) 
COLLECT_GCC_OPTIONS='-E' '-v'
 /usr/libexec/gcc/powerpc-unknown-linux-gnu/7.3.0/cc1 -E -quiet -v -imultilib . 
-imultiarch powerpc-linux-gnu -D__unix__ -D__gnu_linux__ -D__linux__ -Dunix 
-D__unix -Dlinux -D__linux -Asystem=linux -Asystem=unix -Asystem=posix -
niet-bestaande map "/usr/local/include/powerpc-linux-gnu" wordt genegeerd
niet-bestaande map 
"/usr/lib/gcc/powerpc-unknown-linux-gnu/7.3.0/../../../../powerpc-unknown-linux-gnu/include"
 wordt genegeerd
niet-bestaande map "/usr/include/powerpc-linux-gnu" wordt genegeerd
dubbele map "/usr/include" wordt genegeerd
Zoektocht voor #include "..." begint hier:
Zoektocht voor #include <...> begint hier:
 /usr/include
 /usr/lib/gcc/powerpc-unknown-linux-gnu/7.3.0/include
 /usr/local/include
 /usr/lib/gcc/powerpc-unknown-linux-gnu/7.3.0/include-fixed
Einde van opzoekingslijst.
# 1 ""
# 1 ""
# 1 ""
# 1 "/usr/include/stdc-predef.h" 1 3
# 1 "" 2
# 1 ""
COMPILER_PATH=/usr/libexec/gcc/powerpc-unknown-linux-gnu/7.3.0/:/usr/libexec/gcc/powerpc-unknown-linux-gnu/7.3.0/:/usr/libexec/gcc/powerpc-unknown-linux-gnu/:/usr/lib/gcc/powerpc-unknown-linux-gnu/7.3.0/:/usr/lib/gcc/powerpc-unknown-linux-gnu/
LIBRARY_PATH=/usr/lib/:/usr/lib/gcc/powerpc-unknown-linux-gnu/7.3.0/:/usr/lib/gcc/powerpc-unknown-linux-gnu/7.3.0/../../../:/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-E' '-v'

The lines, you are looking for, are put in bold.
There are some lines (marked in red) that worry me about “unexisting directory 
… ignored” and “double directory … ignored”.

I want to add that I already recompiled several times the kernel with this 
version/configuration of the compiler without any problem…

pvg-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

[lfs-support] Cannot rebuild GMP-6.1.2

2021-01-21 Thread Pol Vangheluwe 
(first some context, my question follows at the end of this mail)
A few weeks  ago, there was a (animated) discussion on one of the mailing lists 
(don’t remember exactly which one)) about howto transfer LFS from one machine 
to another and the use of a package manager.
This threead was not only interesting from a technical viewpoint, but also to 
learn about human behaviour on the Internet.

Anyway, this made me wonder if it would be possible to copy LFS-8.1, built on 
an iMac G3, to a PowerMac-G3-Server.
Although both machines are based on the G3 PowerPC, they are quite different.
- the CPU is not exactly the same.  The PowerMac has revision   : 2.2 (pvr 0008 
0202), while the iMac has revision  : 2.2 (pvr 0008 0202)
- but most of all, the surrounding chipset is different.  The 
PowerMac-G3-Server uses mainly third party chips, while the iMac uses Apple 
chips:

pol@PowerMac-G3:~$ lspci
9f08:00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40)
9f08:00:0d.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 02)
9f08:00:10.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rage 128 GL PCI
9f08:01:00.0 FireWire (IEEE 1394): Texas Instruments PCILynx/PCILynx2 IEEE 1394 
Link Layer Controller (rev 02)
9f08:01:01.0 IDE interface: Silicon Image, Inc. PCI0646 (rev 07)
9f08:01:04.0 SCSI storage controller: Adaptec AHA-2940U2/U2W (rev 01)
9f08:01:05.0 Unassigned class [ff00]: Apple Inc. Paddington Mac I/O
9f08:01:06.0 USB controller: OPTi Inc. 82C861 OHCI USB Host (rev 10)

pol@iMac-G3:~$ lspci
:10:0b.0 Host bridge: Apple Inc. UniNorth PCI
:10:17.0 Unassigned class [ff00]: Apple Inc. KeyLargo Mac I/O (rev 02)
:10:18.0 USB controller: Apple Inc. KeyLargo USB
:10:19.0 USB controller: Apple Inc. KeyLargo USB
0001:20:0b.0 Host bridge: Apple Inc. UniNorth Internal PCI
0001:20:0e.0 FireWire (IEEE 1394): Apple Inc. UniNorth FireWire (rev 01)
0001:20:0f.0 Ethernet controller: Apple Inc. UniNorth GMAC (Sun GEM) (rev 01)
9f08:00:0b.0 Host bridge: Apple Inc. UniNorth AGP
9f08:00:10.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Rage 
128 VR AGP

I started by making a backup of the LFS-partition on the iMac, transferred it 
to the PowerMac and untarred it.
I could chroot in the LFS image on the Powermac to adapt the fstab table.
I updated the yaboot configuration, adding LFS, next to the host system 
(Ubuntu-16.4.7-LTS).
I realised that the /home folder on the donor machine was on a separate 
partition (but not on the recipient machine), so I had to transfer this 
partition as well.
I booted into LFS and got the (meanwhile well-known) message

Kernel panic – not syncing : VFS : Unable to mount root fs on unknown - block 
(0,0)

This means mostly that a driver is missing, needed to access the boot device.  
More specifically, a driver that is not needed on the iMac with its Apple 
chipset.
I recompiled several times the kernel, adding (non-Apple) SCSI drivers (and not 
as a module!).
Finally, it looked like adding the “Future Domain 16xx SCSI/AHA-2920A support” 
was a hit.  The boot process continues, but gets an exception a bit further and 
falls in the monitor.
At this point, I got stuck.  I tried several other kernel configuration 
options, even tried booting with INITRAMFS, but never came beyond the kernel 
exception trap.

Then I thought that rebuilding GMP might help.  The CPUs are not 100% 
identical, so GMP was probably optimised for the iMac-G3, but not for the 
PowerMac-G3.
However I got this configuration error:

checking C++ compiler g++  -m32 -O2 -pedantic -mcpu=750... no, std iostream
checking C++ compiler g++  -g -O2... no, std iostream
configure: error: C++ compiler not available, see config.log for details

and in config.log:

/* This test rejects OSF 5.1 Compaq C++ in its default pre-standard iostream
   mode, since that mode puts cout in the global namespace, not "std".  */
void someoutput (void) { std::cout << 123; }

int main (void) { return 0; }
configure:10650: result: no, std iostream
configure:10521: checking C++ compiler g++  -g -O2
Test compile: 
configure:10535: g++  -g -O2 conftest.cc >&5
configure:10538: $? = 0
configure:10542: ./a.out || ./b.out || ./a.exe || ./a_out.exe || ./conftest
configure:10545: $? = 0
Test compile: namespace
configure:10575: g++  -g -O2 conftest.cc >&5
configure:10578: $? = 0
configure:10582: ./a.out || ./b.out || ./a.exe || ./a_out.exe || ./conftest
configure:10585: $? = 0
Test compile: std iostream
configure:10621: g++  -g -O2 conftest.cc >&5
In file included from /usr/include/c++/7.3.0/ext/string_conversions.h:41:0,
 from /usr/include/c++/7.3.0/bits/basic_string.h:6349,
 from /usr/include/c++/7.3.0/string:52,
 from /usr/include/c++/7.3.0/bits/locale_classes.h:40,
 from /usr/include/c++/7.3.0/bits/ios_base.h:41,
 from /usr/include/c++/7.3.0/ios:42,
 from /usr/include/c++/7.3.0/ostream:38,
 from /u

Re: [lfs-support] regulatory.db

2019-04-10 Thread Pol Vangheluwe 


> 
> I forgot point 4 ;-)
> 
> If you do need the database, please read Xi's (xry211's but the web
> interface shows him as Xi) contributions.
> 
> ĸen
> -- 
>  It is said that there are two great unsolved problems in computer
>  science: naming, cache invalidation, and off-by-one errors.
> -- Ben Bullock
> -- 
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
> 
> Do not top post on this list.
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 
> http://en.wikipedia.org/wiki/Posting_style

I solved it in this way:

https://www.mail-archive.com/blfs-support@lists.linuxfromscratch.org/msg05757.html

pvg
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Giving up on LFS

2019-03-12 Thread Pol Vangheluwe 
Op 10 mrt. 2019, om 20:21 heeft Paul Rogers  het 
volgende geschreven:
> 
>> For those who know how to do that, the result is generally better.  It's 
>> easier today though.  It's not like you need a soldering iron any more.
>> 
>> http://oldcomputers.net/heathkit-h89.html  :)
>> 
>>   -- Bruce
> 
> IMSAI!  Front panel, switches and lights!  Boot by depositing binary code 
> into RAM with the front panel switches a byte at a time.  Totally 1st 
> generation computing.  And I still have it.  ;-)  (Alas :-( , the 
> floating-gate charge has certainly leaked off the 2708's & 2716's by now.)
> 
> I’ve always been very grateful that I was at the right time to have 
> recapitulated essentially the whole history of computing from 1st generation 
> on up, either professionally or personally.
> 
My first one was the “Junior Computer”, inspired by the KIM, a 6502 processor 
with one 2708 and two 2114.  It has a hex keyboard and a hex display.
It dates from 1980 and I’ll try to boot it one of these days.

pvg

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

[lfs-support] Host system requiremens

2018-03-12 Thread Pol Vangheluwe 
The list of host system requirements in development/LFS-BOOK-SVN-20180303 looks 
a bit outdated
when comparing with the requirements in the INSTALL file of glibc-2.27

Package Bookglibc-2.27
=   =   =
gcc 4.7 4.9
binutils2.172.25
bison   2.3 2.7

pvg
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Intel microcode updates adding confusion?

2018-01-15 Thread Pol Vangheluwe 
There is still life besides Intel and AMD:

More about Spectre and the PowerPC (or why you may want to dust that G3 off) 

pvg


> 
> -- 
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
> 
> Do not top post on this list.
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 
> http://en.wikipedia.org/wiki/Posting_style

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

[lfs-support] glibc-2.26 - zic segmentation faults

2018-01-04 Thread Pol Vangheluwe 
On 09/12/17 05:16, Armin K. wrote:
(…)
I’ve only seen this happen if there's a mismatch between chapter 5 and
chapter 6 glibc (ie, reusing the older toolchain).

Armin,
Thank you for the suggestion - I will focus on my efforts on this area...

Cheers,

Brandon
-

I have exactly the same problem on my PowerPC G3 and G4 (but not on my iMac G5):
zic segfaults, just after it has been created with the final build of 
glibc-2.26.

I am building with jhalfs and applied the following patches for G3 and G4 to 
the command files:

--- chapter05/035-gcc-pass1.old 2017-12-31 16:29:23.348133360 +0100
+++ chapter05/035-gcc-pass1 2017-12-31 16:32:34.707549237 +0100
@@ -9,7 +9,7 @@
 mv -v gmp-6.1.2 gmp
 tar -xf ../mpc-1.0.3.tar.gz
 mv -v mpc-1.0.3 mpc
-for file in gcc/config/{linux,i386/linux{,64}}.h
+for file in gcc/config/{linux,i386/linux{,64},rs6000/{linux64,sysv4}}.h
 do
   cp -uv $file{,.orig}
   sed -e 's@/lib\(64\)\?\(32\)\?/ld@/tools&@g’ \

--- chapter05/040-gcc-pass2.old 2017-12-31 16:35:17.203055637 +0100
+++ chapter05/040-gcc-pass2 2017-12-31 16:36:24.442850873 +0100
@@ -5,7 +5,7 @@
 cd $PKGDIR
 cat gcc/limitx.h gcc/glimits.h gcc/limity.h > \
   `dirname $($LFS_TGT-gcc -print-libgcc-file-name)`/include-fixed/limits.h
-for file in gcc/config/{linux,i386/linux{,64}}.h
+for file in gcc/config/{linux,i386/linux{,64},rs6000/{linux64,sysv4}}.h
 do
   cp -uv $file{,.orig}
   sed -e 's@/lib\(64\)\?\(32\)\?/ld@/tools&@g’ \

--- chapter06/076-glibc.old 2017-12-31 16:42:27.017746105 +0100
+++ chapter06/076-glibc 2017-12-31 16:43:31.677548743 +0100
@@ -13,6 +13,9 @@
 ln -sfv ../lib/ld-linux-x86-64.so.2 /lib64
 ln -sfv ../lib/ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3
 ;;
+ppc)GCC_INCDIR=/usr/lib/gcc/powerpc-unknown-linux-gnu/7.2.0/include
+ln -sfv ld.so.1 /lib/ld-lsb-ppc32.so.3
+;;
 esac
 rm -f /usr/include/limits.h
 mkdir -v build

--- chapter06/077-adjusting.old 2017-12-31 17:08:09.417046828 +0100
+++ chapter06/077-adjusting 2017-12-31 17:09:37.100779882 +0100
@@ -3,9 +3,9 @@
 set -e
 
 mv -v /tools/bin/{ld,ld-old}
-mv -v /tools/$(uname -m)-pc-linux-gnu/bin/{ld,ld-old}
+mv -v /tools/powerpc-unknown-linux-gnu/bin/{ld,ld-old}
 mv -v /tools/bin/{ld-new,ld}
-ln -sv /tools/bin/ld /tools/$(uname -m)-pc-linux-gnu/bin/ld
+ln -sv /tools/bin/ld /tools/powerpc-unknown-linux-gnu/bin/ld
 gcc -dumpspecs | sed -e 's@/tools@@g'   \
 -e '/\*startfile_prefix_spec:/{n;s@.*@/usr/lib/ @}' \
 -e ‘/\*cpp:/{n;s@$@ -isystem /usr/include@}' >  \

I applied the same patches on my G5, plus a few more, related to 64-bit code.  
No segfaulting on the G5…

Any suggestion is welcome - I am running out of ideas…

pvg

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] ALFS: glibc-2.26, pass-1 fails

2017-11-11 Thread Pol Vangheluwe 

> Op 9 nov. 2017, om 07:53 heeft DJ Lucas  het volgende 
> geschreven:
> 
>> 
> 
> Nothing obvious, but are you running a sufficiently recent kernel? The malloc 
> call reminds me that they fixed a stack overflow in both glibc and kernel 
> only a few months ago. I know a 3.18.20 kernel was successfully used (on 
> list) not too long ago on x86_64. Also, what is the host? Maybe that will 
> give us a clue, but not many building on PPC.
> 
> --DJ

The host system is LFS-7.7 and the machine is a Power Mac G4 (Mirrored Drive 
Doors 2003).  The kernel version is 3.19.0:

lfs_ppc125 [ ~ ]$ uname -a
Linux ppc125 3.19.0 #9 Tue Aug 9 19:14:38 CEST 2016 ppc GNU/Linux

pvg-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] ALFS: glibc-2.26, pass-1 fails

2017-11-08 Thread Pol Vangheluwe 

> Op 5 nov. 2017, om 17:22 heeft Pol Vangheluwe  het 
> volgende geschreven:
> 
> 
>> Op 3 nov. 2017, om 00:15 heeft DJ Lucas > <mailto:blfs-...@lucasit.com>> het volgende geschreven:
>> (…)
>> I don't build PPC, but that link should be /lib/ld-lsb-ppc32.so.3 for PPC32 
>> or /lib64/ld-lsb-ppc64.so.3 for PPC64.
>> 
>> See:
>> 
>> http://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-PPC32/LSB-Core-PPC32/requirements.html#RLIBRARIES
>>  
>> <http://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-PPC32/LSB-Core-PPC32/requirements.html#RLIBRARIES>
>> 
>> and
>> 
>> http://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-PPC64/LSB-Core-PPC64/requirements.html#RLIBRARIES
>> 
>> —DJ
> 
> I changed the link as suggested by DJ but it didn’t solve the problem.  To be 
> sure that no leftover form the previous build is still contaminating the 
> system,
> I even restarted from zero.
> 
> It is maybe good to know that, already during the build of glibc, the system 
> is spitting out tons of messages “ld.so.1: unhandled signal 11 at …”,
> but without stopping the command script.  The script only stops when 
> executing zic.
> coredumpctl reports hundreds of lines like:
> 
> zo 2017-11-05 12:40:44 CET21343 -775979576 -775979576  11 * 
> /mnt/build_dir/sources/glibc-2.26/build/elf/ld.so
> 
Inspecting a coredump for ld.so delivers this result:

lfs_ppc125 [ /var/lib/systemd/coredump ]$ sudo gdb 
/mnt/build_dir/sources/glibc-2.26/build/elf/ld.so 
"core.ld\x2eso\x2e1.-857252408.6affbfe0e76e4d0095de50f2a05540cb.3453.150988124900"
[sudo] password for lfs_ppc125
GNU gdb (GDB) 7.8
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /mnt/build_dir/sources/glibc-2.26/build/elf/ld.so...done.

warning: core file may not match specified executable file.
[New LWP 3454]
[New LWP 3453]
[New LWP 3458]
[New LWP 3455]
[New LWP 3456]
[New LWP 3457]
[New LWP 3459]

warning: Could not load shared library symbols for 7 libraries, e.g. 
linux-vdso32.so.1.
Use the "info sharedlibrary" command to see the complete listing.
Do you need "set solib-search-path" or "set sysroot"?
Core was generated by `/sources/glibc-2.26/build/elf/ld.so.1 --library-path 
/sources/glibc-2.26/build:'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0fe2ea60 in ?? ()
(gdb) set sysroot /mnt/build_dir
Reading symbols from 
/mnt/build_dir/sources/glibc-2.26/build/dlfcn/libdl.so.2...done.
Loaded symbols for /mnt/build_dir/sources/glibc-2.26/build/dlfcn/libdl.so.2
Reading symbols from 
/mnt/build_dir/sources/glibc-2.26/build/resolv/libresolv.so.2...done.
Loaded symbols for /mnt/build_dir/sources/glibc-2.26/build/resolv/libresolv.so.2
Reading symbols from 
/mnt/build_dir/sources/glibc-2.26/build/nptl/libpthread.so.0...done.
warning: Unable to find libthread_db matching inferior's thread library, thread 
debugging will not be available.
Loaded symbols for /mnt/build_dir/sources/glibc-2.26/build/nptl/libpthread.so.0
Reading symbols from /mnt/build_dir/sources/glibc-2.26/build/libc.so.6...done.
Loaded symbols for /mnt/build_dir/sources/glibc-2.26/build/libc.so.6
Reading symbols from /mnt/build_dir/sources/glibc-2.26/build/elf/ld.so.1...done.
Loaded symbols for /mnt/build_dir/sources/glibc-2.26/build/elf/ld.so.1
Reading symbols from 
/mnt/build_dir/sources/glibc-2.26/build/resolv/libnss_dns.so.2...done.
Loaded symbols for 
/mnt/build_dir/sources/glibc-2.26/build/resolv/libnss_dns.so.2
(gdb) bt
#0  __GI___libc_realloc (oldmem=0xa642db30, bytes=8) at malloc.c:3145
#1  0x0fe0440c in _IO_vfscanf_internal (s=s@entry=0xb7f24420, 
format=format@entry=0x10006230 , argptr=argptr@entry=0xb7f24550, errp=errp@entry=0x0)
at vfscanf.c:1193
#2  0x0fe16134 in _IO_vsscanf (string=0xb7f246fe "code1.example", 
format=0x10006230 , 
args=args@entry=0xb7f24550) at iovsscanf.c:41
#3  0x0fe0ea20 in __sscanf (s=, format=) at 
sscanf.c:32
#4  0x1000163c in ?? ()
#5  0x10002c44 in ?? ()
#6  0x10002dc8 in ?? ()
#7  0x10002354 in ?? ()
#8  0x0ff4febc in start_thread (arg=0xb7f254b0) at pthread_create.c

Re: [lfs-support] ALFS: glibc-2.26, pass-1 fails

2017-11-05 Thread Pol Vangheluwe 

> Op 3 nov. 2017, om 00:15 heeft DJ Lucas  het volgende 
> geschreven:
> (…)
> I don't build PPC, but that link should be /lib/ld-lsb-ppc32.so.3 for PPC32 
> or /lib64/ld-lsb-ppc64.so.3 for PPC64.
> 
> See:
> 
> http://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-PPC32/LSB-Core-PPC32/requirements.html#RLIBRARIES
> 
> and
> 
> http://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-PPC64/LSB-Core-PPC64/requirements.html#RLIBRARIES
> 
> —DJ

I changed the link as suggested by DJ but it didn’t solve the problem.  To be 
sure that no leftover form the previous build is still contaminating the system,
I even restarted from zero.

It is maybe good to know that, already during the build of glibc, the system is 
spitting out tons of messages “ld.so.1: unhandled signal 11 at …”,
but without stopping the command script.  The script only stops when executing 
zic.
coredumpctl reports hundreds of lines like:

zo 2017-11-05 12:40:44 CET21343 -775979576 -775979576  11 * 
/mnt/build_dir/sources/glibc-2.26/build/elf/ld.so

pvg


-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] ALFS: glibc-2.26, pass-1 fails

2017-11-02 Thread Pol Vangheluwe 

> Op 21 okt. 2017, om 20:04 heeft Pol Vangheluwe  
> het volgende geschreven:
> 
> 
>> Op 27 sep. 2017, om 08:25 heeft Pierre Labastie  
>> het volgende geschreven:
>>> 
> (…)
>> 
>> You are right, earlier versions had:
>> 
>> for file in \
>> $(find gcc/config -name linux64.h -o -name linux.h -o -name sysv4.h)
>> do ...
>> 
>> The change occurred between 7.10 and 8.0.
>> 
>> Pierre
> 
> I had to apply the same change for the pass-2 compilation of gcc.

(…)

The next problem occurred with the build of 6.9. Glibc-2.26, where the case 
construct to determine the include directory only targets the ix64 architecture.
I added this section for my PowerPC G4:

case $(uname -m) in
(…)
ppc)GCC_INCDIR=/usr/lib/gcc/powerpc-unknown-linux-gnu/7.2.0/include
ln -sfv ld.so.1 /lib/ld-lsb.so.3
;;
esac

This was based on thr following observations:
- for the include line:

lfs_ppc125 [ ~ ]$ ls -l /tools/lib/gcc
totaal 8
drwxr-xr-x 3 root root 4096 29 okt 03:47 powerpc-unknown-linux-gnu
drwxr-xr-x 3 root root 4096 29 okt 00:42 ppc-lfs-linux-gnu

- for the LSB line (as done in CLFS):

lfs_ppc125 [ ~ ]$ LINKER=$(readelf -l /tools/bin/bash | sed -n 
's@.*interpret.*/tools\(.*\)]$@\1@p')
lfs_ppc125 [ ~ ]$ echo $LINKER
/lib/ld.so.1

I could successfully finish the build of glibc with these additions.
But the jhalfs script fails in the section “Adding Time Zone Data”.  The 
logfile tells:

/jhalfs/lfs-commands/chapter06/076-glibc: line 90: 15079 Segmentation fault 
 (core dumped) zic -L /dev/null -d $ZONEINFO -y “sh yearistype.sh" ${tz}

There is a problem with the freshly compiled ‘zic’ program.  I also get lots of 
segmentation faults when I try to manually complete the glibc section.

Any idea what the problem may be?
This looks anyway OK:

lfs_ppc125 [ /mnt/build_dir/jhalfs/logs ]$ readelf -l $LFS/usr/sbin/zic | grep 
interpreter
  [Requesting program interpreter: /lib/ld.so.1]

pvg-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] ALFS: glibc-2.26, pass-1 fails

2017-10-21 Thread Pol Vangheluwe 

> Op 27 sep. 2017, om 08:25 heeft Pierre Labastie  het 
> volgende geschreven:
>> 
(…)
> 
> You are right, earlier versions had:
> 
> for file in \
> $(find gcc/config -name linux64.h -o -name linux.h -o -name sysv4.h)
> do ...
> 
> The change occurred between 7.10 and 8.0.
> 
> Pierre

I had to apply the same change for the pass-2 compilation of gcc.

@Bruce: I rotated the memory modules, removed and re-inserted the PCi cards, 
moved a power cable away from a fan
and could then progress without any segmentation fault.  So, indeed a kind of 
hardware problem, probably related to temperature.  The fan is now also less 
noisy.

@Ken: I bought this week a second hand iMac G5.  I hink that this was the only 
64-bit PPC product line that Apple sold, before it went to Intel.  My next 
project will be cross-compiling a 64-bit LFS on that machine.

pvg

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] ALFS: glibc-2.26, pass-1 fails

2017-09-26 Thread Pol Vangheluwe 

> Op 23 sep. 2017, om 23:38 heeft Ken Moffat  het 
> volgende geschreven:

> http://clfs.org/view/svn/ppc/cross-tools/gcc-static.html suggests
> you will need to change gcc/config/rs6000/sysv4.h
> 
That indeed solved the problem.  I modified 
$LFS/jhalfs/lfs-commands/chapter05/035-gcc-pass1

(…)
# for file in gcc/config/{linux,i386/linux{,64}}.h
for file in gcc/config/{linux,i386/linux{,64},rs6000/sysv4}.h
(…)

and removed the marker files 036-linux-headers and 035-gcc-pass1 in $LFS/jhalfs 
to restart the build process from 035-gcc-pass1.
The linker problem didn’t pop up anymore after the compilation of glibc.

There is however something strange in the LFS-book:
the “for” construction itself doesn’t look for a sysv4.h file, but the 
explanation just below does mention it.

That makes me think that older releases of the book had a more extended “for” 
construction.
What also could explain why this problem didn’t pop up during my earlier LFS 
builds on PowerPC.

Anyway, thanks for the hint!

pvg-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] ALFS: glibc-2.26, pass-1 fails

2017-09-23 Thread Pol Vangheluwe 

> Op 22 sep. 2017, om 22:27 heeft Pierre Labastie  het 
> volgende geschreven:
> 
> There are a number of options, which are not in the vanilla book 
> (target_alias, --no-create,...). Do you use a customized version of the book? 
> I guess it is necessary for ppc. I wonder what you have for replacing  the 
> instructions on the gcc page starting with "for file in 
> gcc/config/{linux,i386/linux{,64}}.h". I guess there might be files 
> mentioning ppc in gcc/config, which are not touched by the instructions in 
> the vanilla book. I think the issue is there…

I use the standard book.  The “for” construction of section 5.5.1 was indeed 
one of my suspects, but, as I am not at all familiar with the internals of gcc, 
I didn’t explore this deeper.  I now took a look in gcc/config and there are 
indeed a lot of CPU types mentioned (even m68k and pdp11!) but no ppc.  My best 
guess is rs6000.

I remember vaguely that I had the same problem wit LFS-7.2, But I don’t 
remember how I went around it.  The host distribution then was Ubuntu.

> Op 22 sep. 2017, om 21:53 heeft Michael Shell  het 
> volgende geschreven:
> 
> From
> 
> https://techoverflow.net/2013/02/28/how-to-fix-cannot-find-crt1-o-on-ubuntu/
> https://stackoverflow.com/questions/40233088/ld-cannot-find-crt1-o-no-such-file-or-directory
> https://stackoverflow.com/questions/7934642/cross-compile-cannot-find-crt1-o
> 
> Try putting the libary path in $LIBRARY_PATH:
> 
> LIBRARY_PATH=/mnt/build_dir/tools/lib:$LIBRARY_PATH
> export LIBRARY_PATH
> 
> or just for make
> 
> LIBRARY_PATH=/mnt/build_dir/tools/lib make
> 
> also, you can try setting --sysroot= in CFLAGS during the build:
> 
> CFLAGS=“--sysroot=/mnt/build_dir/tools" make

A googled a while before posting this problem but didn’t find anything directly 
related to LFS, so I maybe overlooked some useful hints.
I’ll try your suggestion.

> Op 22 sep. 2017, om 21:37 heeft Bruce Dubbs  het 
> volgende geschreven:
> 
> Programs working and failing randomly really point to HW problems. Depending 
> on the exact model, PPC G4s go back to 1999.
> 
> You should be able to build with 2G RAM+3G swap, so that is probably not the 
> issue.

It is strange: my machine never segfaults, expect when building LFS and 
especially when compiling gcc or glibc in pass-1.  I had the same problem with 
earlier builds.
My G4 is a “Mirrored Drive Doors 2003”.  I like building LFS on an old Apple 
computer; I was a bit shocked when Apple dropped the powerpc for Intel.  I had 
of course to follow and there are now 2 Intel iMacs at home.  Glad that an iMac 
has no sticker “Intel inside” …

>> 
> 
> -- 
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
> 
> Do not top post on this list.
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 
> http://en.wikipedia.org/wiki/Posting_style

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

[lfs-support] ALFS: glibc-2.26, pass-1 fails

2017-09-22 Thread Pol Vangheluwe 
I already built successfully LFS-7.2 on a PowerPC G4 with ALFS.  I am now 
upgrading this machine to LFS-8.1.
The build fails at 037-glibc-2.26 with this error:

(…)
rm -f /mnt/build_dir/sources/glibc-2.26/build/stubs.h
make[2]: Leaving directory '/mnt/build_dir/sources/glibc-2.26'
make[1]: Leaving directory '/mnt/build_dir/sources/glibc-2.26/build'
/mnt/build_dir/tools/bin/../lib/gcc/ppc-lfs-linux-gnu/7.2.0/../../../../ppc-lfs-linux-gnu/bin/ld:
 cannot find crt1.o: No such file or directory
/mnt/build_dir/tools/bin/../lib/gcc/ppc-lfs-linux-gnu/7.2.0/../../../../ppc-lfs-linux-gnu/bin/ld:
 cannot find crti.o: No such file or directory
collect2: error: ld returned 1 exit status

I get the same error when I try to compile the test program.  This is the 
output when using the “-v” option with gcc:

bash-4.3$ $LFS_TGT-gcc -v dummy.c
Using built-in specs.
COLLECT_GCC=ppc-lfs-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/mnt/build_dir/tools/bin/../libexec/gcc/ppc-lfs-linux-gnu/7.2.0/lto-wrapper
Target: ppc-lfs-linux-gnu
Configured with: ../configure --target=ppc-lfs-linux-gnu --prefix=/tools 
--with-glibc-version=2.11 --with-sysroot=/mnt/build_dir --with-newlib 
--without-headers --with-local-prefix=/tools 
--with-native-system-header-dir=/tools/include --disable-nls --disable-shared 
--disable-multilib --disable-decimal-float --disable-threads 
--disable-libatomic --disable-libgomp --disable-libmpx --disable-libquadmath 
--disable-libssp --disable-libvtv --disable-libstdcxx 
target_alias=ppc-lfs-linux-gnu --enable-languages=c,c++,lto --no-create 
--no-recursion
Thread model: single
gcc version 7.2.0 (GCC) 
COLLECT_GCC_OPTIONS='-v'
 /mnt/build_dir/tools/bin/../libexec/gcc/ppc-lfs-linux-gnu/7.2.0/cc1 -quiet -v 
-imultilib . -imultiarch powerpc-linux-gnu -iprefix 
/mnt/build_dir/tools/bin/../lib/gcc/ppc-lfs-linux-gnu/7.2.0/ -D__unix__ 
-D__gnu_linux__ -D__linux__ -Dunix -D__unix -Dlinux -D__linux -Asystem=linux 
-Asystem=unix -Asystem=posix dummy.c -quiet -dumpbase dummy.c -auxbase dummy 
-version -o /tmp/cct5oHWj.s
GNU C11 (GCC) version 7.2.0 (ppc-lfs-linux-gnu)
compiled by GNU C version 5.1.0, GMP version 6.1.2, MPFR version 3.1.5, 
MPC version 1.0.3, isl version none
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
ignoring nonexistent directory 
"/mnt/build_dir/tools/bin/../lib/gcc/ppc-lfs-linux-gnu/7.2.0/../../../../ppc-lfs-linux-gnu/include"
ignoring duplicate directory 
"/mnt/build_dir/tools/bin/../lib/gcc/../../lib/gcc/ppc-lfs-linux-gnu/7.2.0/include"
ignoring nonexistent directory "/mnt/build_dir/tools/include/powerpc-linux-gnu"
ignoring duplicate directory 
"/mnt/build_dir/tools/bin/../lib/gcc/../../lib/gcc/ppc-lfs-linux-gnu/7.2.0/include-fixed"
ignoring nonexistent directory 
"/mnt/build_dir/tools/bin/../lib/gcc/../../lib/gcc/ppc-lfs-linux-gnu/7.2.0/../../../../ppc-lfs-linux-gnu/include"
ignoring nonexistent directory "/mnt/build_dir/tools/include/powerpc-linux-gnu"
ignoring duplicate directory "/mnt/build_dir/tools/include"
#include "..." search starts here:
#include <...> search starts here:
 /mnt/build_dir/tools/bin/../lib/gcc/ppc-lfs-linux-gnu/7.2.0/include
 /mnt/build_dir/tools/bin/../lib/gcc/ppc-lfs-linux-gnu/7.2.0/include-fixed
 /mnt/build_dir/tools/include
End of search list.
GNU C11 (GCC) version 7.2.0 (ppc-lfs-linux-gnu)
compiled by GNU C version 5.1.0, GMP version 6.1.2, MPFR version 3.1.5, 
MPC version 1.0.3, isl version none
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: d9ff4b98096773ae8902d1e921a34434
COLLECT_GCC_OPTIONS='-v'
 
/mnt/build_dir/tools/bin/../lib/gcc/ppc-lfs-linux-gnu/7.2.0/../../../../ppc-lfs-linux-gnu/bin/as
 -v -mppc -many -mbig -o /tmp/ccXUP9Hq.o /tmp/cct5oHWj.s
GNU assembler version 2.29 (ppc-lfs-linux-gnu) using BFD version (GNU Binutils) 
2.29
COMPILER_PATH=/mnt/build_dir/tools/bin/../libexec/gcc/ppc-lfs-linux-gnu/7.2.0/:/mnt/build_dir/tools/bin/../libexec/gcc/:/mnt/build_dir/tools/bin/../lib/gcc/ppc-lfs-linux-gnu/7.2.0/../../../../ppc-lfs-linux-gnu/bin/
LIBRARY_PATH=/mnt/build_dir/tools/bin/../lib/gcc/ppc-lfs-linux-gnu/7.2.0/:/mnt/build_dir/tools/bin/../lib/gcc/:/mnt/build_dir/tools/bin/../lib/gcc/ppc-lfs-linux-gnu/7.2.0/../../../../ppc-lfs-linux-gnu/lib/
COLLECT_GCC_OPTIONS='-v'
 /mnt/build_dir/tools/bin/../libexec/gcc/ppc-lfs-linux-gnu/7.2.0/collect2 
-plugin 
/mnt/build_dir/tools/bin/../libexec/gcc/ppc-lfs-linux-gnu/7.2.0/liblto_plugin.so
 
-plugin-opt=/mnt/build_dir/tools/bin/../libexec/gcc/ppc-lfs-linux-gnu/7.2.0/lto-wrapper
 -plugin-opt=-fresolution=/tmp/cc54qNuw.res -plugin-opt=-pass-through=-lgcc 
-plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc 
--sysroot=/mnt/build_dir --eh-frame-hdr -V -m elf32ppclinux -dynamic-linker 
/lib/ld.so.1 crt1.o crti.o 
/mnt/build_dir/tools/bin/../lib/gcc/ppc-lfs-linux-gnu/7.2.0/crtbegin.o 
-L/mnt/build_dir/tools/bin/../lib/gcc/ppc-lfs-linux-gnu/7.2.0 
-L/mnt/build_dir/tools/bin/../lib/gcc 
-L/mnt/build_dir/tools/bin/../lib/gcc/ppc

Re: [lfs-support] O/T - loading distros *after* lfs

2016-02-11 Thread Pol Vangheluwe 
> Op 5 feb. 2016, om 20:33 heeft Richard Melville 
>  het volgende geschreven:
> 
> On 5 February 2016 at 17:47, Ken Moffat  wrote:
>> On Fri, Feb 05, 2016 at 10:39:33AM +, akhiezer wrote:
>>> 
>>> Don't let 'em (2ndary-os's) fk around with your main os - at least, at
>>> (2ndary-os) install time - don't let them even see it: perhaps - if using
>>> a single machine:

>>> (…)

>>> A second machine, &/or hot-swap/esata/external-dock (esp if bootable via),
>>> can all be useful there.
>>> 
>> 
>> Thanks for those suggestions.  I hope I don't have to fiddle about
>> inside the case once I've got the SSD installed (my physical
>> issues, also the KVM cables are a bit short, PS/2 keyboard cable
>> keeps dislodging when I move the case), and this is comparatively
>> low-end hardware so no hot swap or esata.  I can see I may well be
>> heading for a bootable USB stick.
> 
> Thant's definitely the answer -- I wouldn't use anything else now.  It
> doesn't even need to be mounted, other than for editing.
> 
> Richard
> -- 
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
> 
> Do not top post on this list.
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 
> http://en.wikipedia.org/wiki/Posting_style

I never installed a distro after building LFS, but I did a major upgrade of 
Ubuntu (from LTS12 to LTS14, if I remember well).
I was surpised to see that the upgrade procedure had scanned the whole system 
for other Linuxes and had added
a section in yaboot.conf (I am building on PowerPC) to start up LFS, all with 
the correct path names and device UUIDs.

So, there exist other well-educated distros…

pvg



-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] New Lfs 7.8 system with some boot up errors and a question on network

2015-11-07 Thread Pol Vangheluwe 
> Op 7 nov. 2015, om 00:37 heeft Ken Moffat  het 
> volgende geschreven:
> 
> On Fri, Nov 06, 2015 at 04:16:03PM -0500, David Mehler wrote:
> 
>> This next one goes with the network interface. I'd prefer my
>> interfaces to be named eth0, eth1, etc and to let Linux worry about
>> the driver needed, I like consistent interface names.
>> 
>> [3.930679] e1000 :02:01.0 eno1636: renamed from eth0
>> [3.938555] udevd[2664]: renamed network interface eth0 to eno1636
>> 
>> There was a section in the book on this, which I have done, this is is
>> indicating I missed something. Any ideas welcome.
>> 
> 
> I think you are saying that you have created the ifconfig.eth0 file
> (for a static address) ?  Check also section 7.4 'Managing Devices'
> which has options at 7.4.1.1 and 7.4.1.2.  The first option looks
> easiest, but _if_ you ran the script (7.4.1.2) and it somehow
> created a _different_ MAC address in the rule, then the interface
> will be renamed - that has caught me in the past when I moved a
> copy of an LFS system to a new machine.
> 
> ĸen
> -- 
> Il Porcupino Nil Sodomy Est! (if you will excuse my latatian)
>  aka "The hedgehog song"
> -- 
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
> 
> Do not top post on this list.
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 
> http://en.wikipedia.org/wiki/Posting_style

I also had a problem with the (static) IP configuration file, when I booted for 
the first time my LFS-7.7-systemd system.
What the book says is correct, but it could maybe be expressed a bit more 
clearer:

1. As the Note (Udev may assign … your system) says, the output of “ip link” is 
totally different under LFS from what my host system told me.
The only problem is that I already forgot that Note, when I needed it after the 
first boot, so it took some time to find the solution
I had to rerun “ip link” and update the IP configuration file.

2.  The book suggests that the “Name=eth0” line in the configuration file 
should be copied as such, but that is not the case.  I had to put the “ip link” 
name there, to make the interface work.
If you want to use “eth0” as interface name, then you must give that name to 
the configuration file.
This was finally working for me (interface name = “wired”):

root:/sources# cat > /etc/systemd/network/10-static-wired.network << "EOF"
> [Match]
> Name=enP2p32s15f0
> [Network]
> Address=192.168.1.7/24
> Gateway=192.168.1.1
> DNS=192.168.1.1
> EOF

My suggestion: change the command (for a static config) as follows:

cat > /etc/systemd/network/10-static-.network << “EOF”
[Match]
Name=
[Network]
Address=192.168.0.2/24
Gateway=192.168.0.1
DNS=192.168.0.1
EOF

pvg


-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] yaboot-1.3.17

2015-10-22 Thread Pol Vangheluwe 
> Op 6-okt.-2015, om 22:55 heeft Ken Moffat  het 
> volgende geschreven:
> 
> My last ppc builds were actually on a G5, and everything except the
> kernel (and separate binutils, gcc to build the kernel) was 32-bit.
> I think that was around the LFS-7.4 time, and I had to revert to
> yaboot-1.3.13 to get yaboot to build.  Looks as if I used a couple
> of patches (-fix, and -ofpath_sata), I can forward those to you
> off-list if you like.  The sata patch probably isn't needed unless
> you use the libata kernel driver.
> 
> I admire you for continuing to build on such slow hardware.
> 
> ĸen
> -- 
> Il Porcupino Nil Sodomy Est! (if you will excuse my latatian)
>  aka "The hedgehog song"
> -- 
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
> 
> Do not top post on this list.
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 
> http://en.wikipedia.org/wiki/Posting_style

(don’t know if this is the right forum to continue the discussion)

I could indeed build yaboot-1.3.13 (following the instructions of the CLFS 
book) but I have several problems while building yaboot-1.3.17.
(seems to be the latest version, but already 4 years old)

I found 3 patches for version 17 on trac.  I applied them all and followed 
further the instructions for version 13.
- first attempt fails with:

cc1: alle waarschuwingen worden als fouten behandeld
Makefile:128: recept voor doel 'second/yaboot.o' is mislukt
make: *** [second/yaboot.o] Fout 1

I disable the following lines in the Makefile:
# YBCFLAGS += -Werror -fdiagnostics-show-option
# UCFLAGS += -Werror -fdiagnostics-show-option

- second attempt fails with:

ld: cannot find -lext2fs
Makefile:111: recept voor doel 'yaboot' is mislukt
make: *** [yaboot] Fout 1

I disable the ’static’ directive:
# LFLAGS = -Ttext $(TEXTADDR) -Bstatic -melf32ppclinux

- third attempt fails with:

ld: lib/nonstd.o: undefined reference to symbol 'stdout@@GLIBC_2.0'
/lib/libc.so.6: error adding symbols: DSO missing from command line
Makefile:112: recept voor doel 'yaboot' is mislukt
make: *** [yaboot] Fout 1

I re-enable the ‘static’ directive and recompile E2fsprogs-1.42.12 with static 
libraries

- fourth attempt fails with a lot of errors, ending as
(…)
/usr/lib/libext2fs.a(inline.o): In function `ext2fs_group_of_blk’:
(.text+0x5d4): multiple definition of `ext2fs_group_of_blk'
second/fs_ext2.o:fs_ext2.c:(.text+0xff4): first defined here
/usr/lib/libext2fs.a(inline.o): In function `ext2fs_group_of_ino':
(.text+0x5e0): multiple definition of `ext2fs_group_of_ino'
second/fs_ext2.o:fs_ext2.c:(.text+0x100c): first defined here
/usr/lib/libext2fs.a(unix_io.o): In function `raw_write_blk':
(.text+0x19c): undefined reference to `pwrite64'
/usr/lib/libext2fs.a(unix_io.o): In function `raw_read_blk':
(.text+0x614): undefined reference to `pread64'
Makefile:112: recept voor doel 'yaboot' is mislukt
make: *** [yaboot] Fout 1

I am stuck…

BTW: a PowerMac G4 is not _that_ slow… (only a bit noisy)

pvg


-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] sdx or hdx?

2015-10-08 Thread Pol Vangheluwe 

> Op 6-okt.-2015, om 22:46 heeft Pierre Labastie  het 
> volgende geschreven:
> 
> I am not sure it appplies to MAC, but there are two ways to configure the
> kernel for IDE disks. The old method is:
> < > ATA/ATAPI/MFM/RLL support (DEPRECATED), and I think it gives hdx drives
> The modern method is:
> < > Serial ATA and Parallel ATA drivers (libata), which gives sdx drives.
> 
> look at kernel config: if CONFIG_IDE is set, the old method is used.
> if CONFIG_ATA is set, it is the modern one.
> 
> Pierre
> 
That’s indeed the solution: checked my kernel config and found the “old” method.
I swapped to the modern method and rebuilt de kernel.  The system now looks for 
/dev/sdx devices.

My “old” config was created, following the book’s instruction (Linux From 
Scratch - Version 7.7-systemd, page 228):

“A good starting place for setting up the kernel configuration is to run make 
defconfig. This will set the base
configuration to a good state that takes your current system architecture into 
account.”

BTW: the book says also to check:

Processor type and features --->
[*] Enable seccomp to safely compute untrusted bytecode [CONFIG_SECCOMP]
(…)
Firmware Drivers --->
[*] Export DMI identification via sysfs to userspace [CONFIG_DMIID]

The first one is actually under “Kernel options” in de menuconfig; I couldn’t 
find the second one.

pvg

> -- 
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
> 
> Do not top post on this list.
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 
> http://en.wikipedia.org/wiki/Posting_style

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] sdx or hdx?

2015-10-06 Thread Pol Vangheluwe 

> Op 6-okt.-2015, om 17:14 heeft Douglas R. Reno  het 
> volgende geschreven:
> 
> Hello!
> 
> I am surprised to hear that you managed to get LFS 7.7-systemd on a
> PowerMac G4 (I have heard that it is possible but I haven't really
> heard of much success). Let me know if this link from the CLFS book
> helps:
> 
> http://www.clfs.org/view/CLFS-3.0.0-SYSTEMD/ppc/bootable/yaboot.html
> 
> I have never built on a Mac before, so I cannot offer much help here.
> If the CLFS team lurks around these lists (William Harrington for
> example), they might be able to help us more. I do have a PowerMac G4
> laying around, but I am not sure that I can actually build LFS on it.
> 
> Douglas R. Reno
> -- 
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
> 
> Do not top post on this list.
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 
> http://en.wikipedia.org/wiki/Posting_style

This is my fourth LFS build, all on Apple computers (PPC7200, PPC7500, iMac400 
and now PowerMac G4).
This is my first systemd build, also the first I did with jhalfs.

(jhalfs is doing a great job, but don’t use it if you want to learn something 
about Linux…)

The only problem I have (and I also had with LFS-7.2 on iMac-400) is that I 
cannot build yaboot.
I know the link to CLFS and I followed the instruction I found there to built 
yaboot, but without success so far.
I will address this in a separate mail to the CLFS forum.

I used the ybin program of the host system (Ubuntu) to reconfgure the boot 
loader but I want of course my “own” version of ybin…

But for now: anyone that can shed a light on the naming of disk devices?

pvg


-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

[lfs-support] sdx or hdx?

2015-10-04 Thread Pol Vangheluwe 
I built LFS-7.7 on a PowerMac G4.
My host system was originally Ubuntu-server 8.04.1 (Hardy).
It got 2 major upgrades, first to Ubuntu 10.04.4 LTS (lucid) and then to Ubuntu 
12.04.5 LTS (precise).

My machine has 3 ATA disks:

lfs@ppc125:~$ sudo lsscsi
[0:0:0:0]diskATA  IBM-IC35L090AVV2 V2HK  /dev/sda 
[0:0:1:0]diskATA  Maxtor 6Y160P0   YAR4  /dev/sdb 
[1:0:0:0]diskATA  WDC WD5000AAKB-0 12.0  /dev/sdc 
[2:0:0:0]cd/dvd  HL-DT-ST RW/DVD GCC-4480B 1.03  /dev/sr0 
[2:0:1:0]cd/dvd  PIONEER  DVD-RW  DVR-110D 1.37  /dev/sr1 

The first 2 Ubuntu releases reported the disks as /dev/hdx, but the third one 
suddenly used /dev/sdx.
It took me some time to make my machine again bootable after the third upgrade.

Now I am finishing LFS-7.7-systemd on this machine and guess what: LFS again 
turns to /dev/hdx…
I now have a quite strange (but working) yaboot.conf, with a mix of sdx (for 
Ubuntu) and hdx (for LFS):

lfs@ppc125:~$ cat /etc/yaboot.conf
## yaboot.conf generated by the Ubuntu installer
##
## run: "man yaboot.conf" for details. Do not make changes until you have!!
## see also: /usr/share/doc/yaboot/examples for example configurations.
##
## For a dual-boot menu, add one or more of:
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ

boot=/dev/sda2
device=/pci@f400/ata-6@d/disk@0:
partition=3
root=/dev/sda3
timeout=50
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot
enablecdboot
macosx=/dev/sdc10

image=/boot/vmlinux
label=Linux
read-only
initrd=/boot/initrd.img
append="quiet splash"

image=/boot/vmlinux.old
label=old
read-only
initrd=/boot/initrd.img.old
append="quiet splash"

image=/boot/vmlinux-3.19-lfs-7.7-systemd
label=LFS
device=/pci@f400/ata-6@d/@1
partition=2
root=/dev/hdb2
read-only
initrd=/boot/initrd.img-3.19.0
append=""

Does anyone have an explanation for this?  Possibly a way to come to a more 
consistent configuration?

BTW: I know that the LFS community doesn’t like initrd, but it looks to be the 
only way to boot LFS on an iMac or a PowerMac.
Without it, LFS always hangs after “returning from prom_init…”
Or is there a way to avoid initrd?

pvg

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] GRUB configuration

2015-06-07 Thread Pol Vangheluwe 


> Op 6-jun.-2015, om 23:03 heeft Pierre Labastie  het 
> volgende geschreven:
> 
> (…)

> I think grub detects that the BIOS is PowerMac, and needs its
> own fonts instead of relying on those of the BIOS. You should definitely skip 
> it.
> 
> IIRC, with jhalfs, you need to remove the grub script:
> rm /mnt/build_dir/jhalfs/lfs-commands/chapter06/119-grub
> 
> Then you run make, and tick "[ ] rebuild the Makefile (see help)".
> 
> Pierre

I found an easier way to skip grub: looks like every succesfull build is marked 
with an empty file in /(mnt/build_dir/)jhalfs,  So I did:

root:/jhalfs# touch 119-grub

and the script is now indeed restarting from “120-less”.

pvg
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

[lfs-support] GRUB configuration

2015-06-06 Thread Pol Vangheluwe 
I am building " lfs-branch-systemd” with ALFS on a PowerMac G4.
The configue for “119-grub-2.02~beta2” fails with:

checking for freetype-config... no
configure: error: qemu, powerpc-ieee1275, coreboot and loongson ports needs 
build-time grub-mkfont (need freetype2 library)

adding this didn’t help:

--disable-grub-mkfont

Freetype is a topic of BLFS, so I am hesitating to install it right now 
(dependencies…).
Any suggestion how to solve this?

BTW: I actually don’t need GRUB, because I use yaboot as boot loader on a 
powerMac.  Is there a way to skip the grub build in ALFS?
Or should I ask this question on the ALFS forum?

pvg

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style