Date: Mon, 18 Dec 2000 23:27:07 -0800 From: David O'Brien <obrien@FreeBSD.ORG> To: Stephen McKay <mckay@thehub.com.au> Cc: current@freebsd.org Subject: Re: Is compatibility for old aout binaries broken? Message-ID: <20001218232706.A90914@hub.freebsd.org> In-Reply-To: <200012190508.eBJ58Po10495@dungeon.home>; from mckay@thehub.com.au on Tue, Dec 19, 2000 at 03:08:25PM %2B1000 References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001217135431.C9721@cae88-102-101.sc.rr.com> <200012180641.eBI6fH607564@dungeon.home> <20001218014656.A17483@cae88-102-101.sc.rr.com> <200012181500.eBIF0S612182@dungeon.home> <20001218100315.A67679@dragon.nuxi.com> <200012190508.eBJ58Po10495@dungeon.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 19, 2000 at 03:08:25PM +1000, Stephen McKay wrote: > Our current problem is that an older ld.so has somehow been made part > of compat22. I'm now attempting to determine whether the ld.so on > the 3.2 CD contains the fix in rev 1.57 of rtld-aout/rtld.c, and if > so I'll just commit it in the compat22 directory. Please delay committing -- since it is UUENCODED, it is a bit repo bloat if we don't get it right. It doesn't seem right to put 3.x bits into the compat22 dist. By definition they are the wrong bits. My internet connection is down for the past day, and I only have limited connectivity right now. But I would like to look into this before anything is committed. - -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001218232706.A90914>