I'm really getting to a point where I can see all of glibc building on x86_64-gnu in not-so-distant future (several hacking sessions away from now)
Of course "building" and "working" are different things...
I'm really getting to a point where I can see all of glibc building on x86_64-gnu in not-so-distant future (several hacking sessions away from now)
Of course "building" and "working" are different things...
$ readelf -h ~/dev/crosshurd64/src/glibc/build/elf/ld.so | head
ELF Header:
Magic: 7f 45 4c 46 02 01 01 03 00 00 00 00 00 00 00 00
Class: ELF64
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - GNU
ABI Version: 0
Type: DYN (Shared object file)
Machine: Advanced Micro Devices X86-64
Version: 0x1
? ld.so builds!! ?
COMEFROM sleep;
In fact, I wonder how far we could get without trampoline/intr-msg/signal stuff really working. Signals are not expected to work in early userspace, and none of the kernel calls we'd want to make (task and memory manipulation, opening and writing to Mach console, etc) are interruptible anyway.
trampoline.c compiles! ?
Ok, now I will
goto sleep;
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.