Would it be correct to replace x86_64 in your documentation bash scripts
with `uname -m`? Because of course everybody knows ARM is the way
of the future. :)
But seriously, I'm not always sure what to relace. Or maybe you could
put them all on one page? It wouldn't detract from the flow of
On Sun, 15 Jul 2018, Ken Moffat wrote:
On Sat, Jul 14, 2018 at 08:49:19PM -0400, Alan Corey wrote:
Would it be correct to replace x86_64 in your documentation bash scripts
with `uname -m`? Because of course everybody knows ARM is the way of the
future. :)
But seriously, I'm not always sure
On Sun, 15 Jul 2018 22:50:07 +0800
Xi Ruoyao wrote:
> On 2018-07-15 09:17 -0400, Alan Corey wrote:
> > On Sun, 15 Jul 2018, Ken Moffat wrote:
> >
> > > On Sat, Jul 14, 2018 at 08:49:19PM -0400, Alan Corey wrote:
> > > > Would it be correct to
LFS is a work of art, I can't believe it's been around 20 years and
I'd never heard of it. 20 years ago I was downloading Slackware on
floppies and lugging them home from college.
The paths are sort of intricate to a newcomer though. There are the
paths I see, the paths the chroot is going to
On 07/09/2018 12:12 PM, Bruce Dubbs wrote:
On 07/09/2018 10:14 AM, Alan Corey wrote:
Please bear with me, I just turned off digest mode. I'll use filters
and folders to deal with random traffic. I'm on Gmail, mostly use the
web client. I'm still on half a dozen mailing lists but mostly I
Like
aarch64-lfs-linux-gnu-as.1
or did I screw up again?
In /mnt/lfs/tools/bin I have a set of executables with names like
aarch64-lfs-linux-gnu-as and in
/mnt/lfs/tools/aarch64-lfs-linux-gnu/bin there's another set with
normal names. Neither are symlinks to the other.
As the lfs user env
On 07/10/2018 01:33 PM, Ken Moffat wrote:
On Tue, Jul 10, 2018 at 10:53:37AM -0400, Alan Corey wrote:
Like
aarch64-lfs-linux-gnu-as.1
or did I screw up again?
For (pseudo) cross-compiling (i.e. pass 1), that is ok.
In /mnt/lfs/tools/bin I have a set of executables with names like
OK, it fails. And when I do
readelf -l a.out
and look at the output manually the interpreter line is just
[Requesting program interpreter: /lib/ld-linux-aarch64.so.1]
No /tools in there. How does it get there? I configured glib with
the little script
#!/bin/bash
../configure --prefix=/tools
On 07/11/2018 12:59 PM, Bruce Dubbs wrote:
On 07/11/2018 10:28 AM, Alan Corey wrote:
OK, it fails. And when I do
readelf -l a.out
and look at the output manually the interpreter line is just
[Requesting program interpreter: /lib/ld-linux-aarch64.so.1]
No /tools in there. How does it get
gt; lfs-support-ow...@lists.linuxfromscratch.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lfs-support digest..."
>
>
> Today's Topics:
>
>1. Re: Booting LFS with systemd (Michael Shell)
>2.
10 matches
Mail list logo
