From owner-freebsd-questions Sat May 20 17:07:56 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA12732 for questions-outgoing; Sat, 20 May 1995 17:07:56 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA12725 for ; Sat, 20 May 1995 17:07:55 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA07788; Sat, 20 May 95 18:01:16 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9505210001.AA07788@cs.weber.edu> Subject: Re: linking kernel... *** signal 11 To: brian@mediacity.com (Brian Litzinger) Date: Sat, 20 May 95 18:01:16 MDT Cc: brian@mediacity.com, freebsd-questions@FreeBSD.org In-Reply-To: from "Brian Litzinger" at May 20, 95 03:15:22 pm X-Mailer: ELM [version 2.4dev PL52] Sender: questions-owner@FreeBSD.org Precedence: bulk > > I'm building a kernel with a device driver from a third party company. > > > Building everything without the third party driver produces a usable kernel. > > > Build everything with the third party driver and during the link > > I get (with ld -t): > > One part of the third party driver is in object format. That module > is what is blowing up the linker. I've forwarded the information > to the third party driver developer. I'm betting object module changes. Try enforcing short name support by putting it in an an archive and ranlibbing it with a short symbol name. This may mean you need to take external references and change them for the shorter name. Other than that, I think you could only win by contacting the author. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.