From owner-freebsd-current Fri Aug 14 09:22:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18538 for freebsd-current-outgoing; Fri, 14 Aug 1998 09:22:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18533 for ; Fri, 14 Aug 1998 09:22:33 -0700 (PDT) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with SMTP id MAA12846 for ; Fri, 14 Aug 1998 12:21:24 -0400 (EDT) Date: Fri, 14 Aug 1998 12:21:24 -0400 (EDT) From: Brian Feldman To: freebsd-current@FreeBSD.ORG Subject: ELF problems to occur Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The transition from a.out to ELF will not be easy; I see some definite potential hangups: gdb - the gdb for a.out will not recognize ELF binaries, and the gdb for ELF will not recognize the current format of core dumps /usr/{X11R6,local}/lib etc. - what will be the new format? Will there be a /usr/X11R6/lib/{elf,aout} (unlikely) or should all old a.out shlibs be moves to /usr/lib/aout, and /usr/lib/aout shall also take over for /usr/lib/compat?Will I have to recompile all my many libraries for ELF or will objcopy work in all cases? I've had pretty good luck with objcopy, and if it works very well, I'll go ahead and write a shell script to help transition libraries. crunch, Modula-3, ldconfig, lkms/kernel - are these all going to be ready? M3 should already be ELF-compilable, crunch should probably still work, will ldconfig be necessary anymore, or is this just wishful thinking? I don't see how ldconfig is in its present state ready for ELF. And supposedly the ELF kernel is bootable nowadays with a few patches; do lkm's work? Just some nice things to trip us up! Cheers, Brian Feldman green@unixhelp.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message