i know it's an old machine and there are some trouble to overcome but should it be possible to try and invest time into make machine below (Apple Intel MacPro early 2008) making running lfs native? Before it had troubles with Ubuntu and refit ending up with only booting OS-X. I am sure i can make the version_check complete for this machine, any (sensible) input is welcome

RoLoR

The hardware specs look decent enough for the time . . .certainly better than what I bought as a laptop then. Mind you, I did buy bankrupt stock.

LFS would go, I am sure. Troubles are
1. Getting a host system to compile chapter 5 from. You may have to go to a distro for a base system to compile LFS from. Slackware 13.0 (dating from 2009) sounds about right and is still up for download on my local mirror anyhow
There's several cd isos, and a dvd iso depending on your reader. There's also a 64-bit version, but no multilib, unless they're still on Alien Bob's stuff.

2. Getting drivers for Apple peripherals may be torture.

You could do worse than running with slackware. Keep away from kde & gnome. Xfce, or something low cholesterol. My 2008 laptop took Mint-19.0 without only a few hitches, and Slackware 14.1 with basically no hitches. Some old firmware was dropped from the kernel along the way, and that caused the problems. There's a lot of backward compatibility in Linux. If you look in the 'arch' directory of a kernel source, you'll find kernel support for very underpowered and lame cpus beside yours, things that never got out of the 1980s or 1990s with any style and certainly aren't at today's races with Intel/AMD.

Okay doing a stupid thing and ran version_check.sh on the bash shell on the mac.. it got xcode installed to make that even possible. Lot of work left to get it working further...
sharing the output of chapter 2.2 of the bookafter a few bottles and waiting for updating xcode got the current state of machine already a lot closer to start building lfs
i'll explain the blocks i put together to get this later. (the bottles have to wear off again) i'm sure for example i added binutils but isn't showing up yet

You're trying to get the MacOS to build LFS? Brave.

Red Hat distros can't build LFS There is a lot of Unix stuff underlying MacOS.

Be confident in your toolchain (kernel & headers, glibc, GCC) before proceeding. Try chapter 5 & report back You usually know if you can build GCC in chapter 6 and pass tests. That's a big one.

Today taking a shortcut on the mac with gparted i created the following
Of course i can start building of LFS on the just installed linux but that is not fun.
Still have trouble on boot manager.
regarding the drivers i can tell the USB-EFI-boot (by shortcut with holding option-key during post) that WiFi is already functioning and so are the wired-network-connections

For you, building with llvm and not gcc, the 'make test' stage of builds is critical. gcc has a make test stage in ch 5 & ch.6 and don't proceed if they're not good.

Looks like your shell is original Bourne! The LFS scripts include some specific bashisms and won't work correctly with a different shell. For example, they don't work with dash.

I notice too that your awk is real awk. LFS requires gawk.

You will have fun trying, but I am dubious about your chances of success.

Maybe you should try CLFS. This allows you to use a PC to create a toolkit that will run on a different architecture. Then you transfer it over and use it for the final build.

A little explaining I’ve to make what I’m doing to get the gnu software working inside MacOS. Believe me it’s a bit dirty but trying to clean the mess during progressing of reaching goal.
The machine was used to learn Ruby, there where Mac ports installed which I disabled.
With Ruby I went to Homebrew
From there I could get all gnu packages needed to go with even gcc-8.2.0 which is ugly enough still ignored.

I’m doubting to first refresh the MacOS (El Capitan) or find the reason why several packages are ignored.
This mac is temporarily pushed aside for a even older G5 which is in need of help to get it through 2018.

Still any intel is welcome. Thanks so far for the feedback

I ran a 2009 macbook for a while. It's a fight to get any linux on it. In my own experience, most of the Live CDs I tried failed to even boot! I was never able to get any linux installed. Macs (at least then) had a kludgy mix of UEFI (not bios) with an MBR partition table. This tends to break boot-loaders. I would not even consider attempting LFS on such a machine unless I had already installed an easier linux on that machine. Something like an ubuntu or a slackware.

p.s. Despite running a BLFS system, I'm not an expert, so I could well be wrong. If you do get it to work, most excellent and please post how you did it.

The information I have around partition-styles in Apple is easy:

GPT used on every intel Mac for making a bootable system
APT used on PowerPC macs (and before Motorola 68K) for making a bootable system (older used blessing of a bootable folder)
MBR used on intel macs for creating bootcamp solutions regarding booting Windows on intel macs

BIOS never exist on a Apple machine all Intels are using EFI but indeed in a very different way then the way used on other PCs.

Above is the theory Apple is telling and indeed there is a messed up version in reality seen on the intel Apple machines.
The investigation on how to let the open firmware boot any Linux is still wide open.
For me refit and refind didn’t worked like they promised on the web

From what I see of disk partitions, you have an installed ubuntu. Am I correct?

In post #1, you asked usTo summarize, we said 'with great difficulties' or 'NO.'
You also saidSo you have your answer. Mark this solved, go away and have 'fun' as it refuses to do what you want it to. You will hone your expertise on the differences between gnu and MacOS. One of the biggest might be that MacOS is not copyleft or GPL. And when that pukes, just try it with your installed ubuntu before posting.

Above remark just hurt me. @business_kid if you don’t like my thread or where i’m going ignore it please. I never would want to hurt you in any way. Nor would I ever want a war or flame as it’s called on a forum.

I’m trying a rather not out of the box thing, possibly even impossible.

I’m indeed trying to get an environment in macOS where I can make a LFS. macOS doesn’t even know anything of an ext partition. Not without use of commercial software. That was the main thing to go to in this case Ubuntu-live so with gparted I could create a ext partition and do a shadow install of Ubuntu for just in case.

It’s not solved yet,
- still have trouble on boot manager.

In other words if I put grub on the macOS drive it will be detected and removed by macOS as soon as it boots back into that.
Same will happen to refit or refind. Of course the installed Ubuntu would boot as long as you don’t want dual-boot.
In my case I told the install of Ubuntu to install grub on the /dev/sdd in stead of the macOS drive.

Well, I'm sorry if it hurt you. It was never my intention to cause offense, just to inject some reality.

When you have failed in building LFS more than once, you become aware of the TINY things that can ruin the integrity of a build, and then looking at the large obstacles blocking your path, there is a real negative feeling about this that comes from nearly every respondent.

IT heads know it's possible, and will see some of the obstacles, but will go about it. They wouldn't ask. Half the obstacles might be unseen, but they'd solve them when they got there. With Ubuntu installed, they wouldn't bother with MacOS. You're really writing another LFS book. Document the process. The LFS guys would love you for that. But you may have to patch things, or change patches. Are you up for that?

You should be able to get gnu stuff working inside MacOS by making a /gnu directory in /, building your gnu environment there so you could even run 'chroot /gnu' and find /gnu/bin/bash, but you may consider that cheating. I would use the Ubuntu build, but you want to use MacOS. So try it. If you retire in defeat, you've learned loads.

And I will unsubscribe from this thread as you suggest. You've talked around it enough; we haven't dissuaded you. So go for it.

It strikes me burning a cdrom or dvd might get you round the boot loader thing. If you confined MacOS to booting off a cdrom, it wouldn't see anything else :-D.

I still think CLFS is the way to go. Here's a link to the architectures you can build for. At least browse it and then decide if this would be cheating.

First @business_kid: I must have read it to much in my own emotion, I forgive and will continue.
—— start normal stuff ——

You guys really rock.

Today I went on research for why lubuntu would made an easy dual boot with macOS. They use there yaboot. This is sufficient for the Mac G5 PowerPC that came in between. (l and return for Linux, c for CD-ROM, x for Mac OS X (10.5.8 latest ppc) )
Further I looked into SuSe tumbleweed ppc64 disk, where the PowerPC could be booted by open firmware (command+option+O+F holding during post till screen say release) with grub.
Hazel you pointed me sure to a good direction to go for reading. I never had read the CLFS but sure looks like there’s a lot of what I’m searching of to get a multi boot going on the intel based Mac. I’m gonna read that stuff.

For the trouble of boot management I see 2 promising solutions that will most likely hold more then other stuff on the web.

RoLoR