From owner-freebsd-hackers Mon Oct 19 12:14:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08560 for freebsd-hackers-outgoing; Mon, 19 Oct 1998 12:14:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08548 for ; Mon, 19 Oct 1998 12:14:13 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id NAA24178; Mon, 19 Oct 1998 13:13:40 -0600 (MDT) Message-Id: <4.1.19981019130712.065ac610@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 19 Oct 1998 13:09:54 -0600 To: Mike Smith From: Brett Glass Subject: Re: Producing non-GPLed tools for FreeBSD Cc: Mike Smith , hackers@FreeBSD.ORG In-Reply-To: <199810191900.MAA00611@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:00 PM 10/19/98 -0700, Mike Smith wrote: >libbfd is the binary file descriptor library; it contains primitives >for reading and writing the various file formats that binutils >supports. as, ld and ar all use it for manipulating their files. Hmm. I could write some code that used it to generate samples, then emulate what it did. Awkward, though. And a shame that I'd have to reinvent the wheel. That's what open source software is supposed to avoid! >ELF objects are documented int the ELF documentation. Will have to look at these docs.... >I suspect that Cygnus may have some documentation on the behaviour of >GCC on the i386. You would have to talk to them about that. Well, John Gilmore, founder of Cygnus, once refused to give me ANY help or information if the product of my work was not to be GPLed, so I'm not optimistic. But I suppose I could try. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message