** HEADS UP ** ELF Branding changes require action on your part.
- Forwarded message from "David E. O'Brien" <[EMAIL PROTECTED]> - Log: Change our ELF binary branding to something more acceptable to the Binutils maintainers. ... Note that a new kernel can still properly load old binaries except for Linux static binaries branded in our old method. - End forwarded message - One statically linked Linux binary that will cause you trouble after you build world is the Linux ``ldconfig''. After your ``make world'' and before you reboot that new kernel, issue: brandelf -t Linux /compat/linux/sbin/ldconfig -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** ELF Branding changes require action on your part.
David O'Brien wrote: > - Forwarded message from "David E. O'Brien" <[EMAIL PROTECTED]> - > Log: > Change our ELF binary branding to something more acceptable to the Binutils > maintainers. > ... > Note that a new kernel can still properly load old binaries except for > Linux static binaries branded in our old method. > - End forwarded message - > > One statically linked Linux binary that will cause you trouble after you > build world is the Linux ``ldconfig''. After your ``make world'' and > before you reboot that new kernel, issue: > > brandelf -t Linux /compat/linux/sbin/ldconfig > Does this mean that we can re-brand any statically linux binary if it fails? -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** ELF Branding changes require action on your part.
On Mon, Apr 17, 2000 at 10:03:25PM -0700, Steve Kargl wrote: > > brandelf -t Linux /compat/linux/sbin/ldconfig > Does this mean that we can re-brand any statically > linux binary if it fails? Yes. Just like the above. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
