From owner-freebsd-questions@FreeBSD.ORG Wed Jan 23 16:01:27 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7BFEDD50; Wed, 23 Jan 2013 16:01:27 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 4301CD14; Wed, 23 Jan 2013 16:01:26 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id r0NG10jq019432 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 23 Jan 2013 10:01:18 -0600 Received: from [10.0.0.102] (10.14.152.7) by smtp.fisglobal.com (10.132.206.31) with Microsoft SMTP Server (TLS) id 14.2.309.2; Wed, 23 Jan 2013 10:01:14 -0600 Subject: Re: building crunchgen fails MIME-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset="us-ascii" From: Devin Teske In-Reply-To: Date: Wed, 23 Jan 2013 08:01:12 -0800 Content-Transfer-Encoding: quoted-printable Message-ID: <82E7A4A3-B65D-4ECA-BEF4-FD67445AF1B2@fisglobal.com> References: To: Rick Miller X-Mailer: Apple Mail (2.1283) X-Originating-IP: [10.14.152.7] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8327, 1.0.431, 0.0.0000 definitions=2013-01-23_05:2013-01-23,2013-01-23,1970-01-01 signatures=0 Cc: Devin Teske , FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2013 16:01:27 -0000 On Jan 23, 2013, at 7:22 AM, Rick Miller wrote: > Hi All, >=20 > When executing crunchgen -o boot_crunch.conf && make -f boot_crunch.mk > I get the following error: >=20 > cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo > ls.lo test.lo cat.lo df.lo sleep.lo camcontrol.lo dhclient.lo > fsck_ffs.lo ifconfig.lo mount_nfs.lo newfs.lo route.lo rtsol.lo > tunefs.lo kenv.lo sysctl.lo mdmfs.lo dmesg.lo fdisk.lo bsdlabel.lo > uname.lo cpio.lo find.lo minigzip.lo sed.lo awk.lo fetch.lo arp.lo > sysinstall.lo usbconfig.lo grep.lo -lcam -lsbuf -lutil -ll -ledit > -lfetch -lmd -lcrypt -lftpio -lz -lnetgraph -ldialog -lncurses -ldisk > -lufs -ldevinfo -lkvm -lgeom -lbsdxml -larchive -lbz2 -lusb -lgnuregex > -llzma -lssl -lcrypto -ljail -lm > camcontrol.lo(.text+0x730b): In function `main': > : undefined reference to `mode_edit' > camcontrol.lo(.text+0x73fa): In function `main': > : undefined reference to `mode_list' > *** Error code 1 >=20 > Stop in /tmp/crunchtmp. >=20 > I understand that there may need to be some shuffling of the libraries > in the boot_crunch.conf, but I've done that to no avail. Wondering if > anyone else may be able to shed some light on this... >=20 > The boot_crunch.conf can be viewed at http://pastebin.com/ZwVPQn3h >=20 According to the Makefile, if RELEASE_CRUNCH is defined, then modeedit.o ob= ject is omitted (causing your undefined references). I perceive the long-term real solution would be to patch camcontrol.c (and = pedantically camcontrol.h) to not use mode_edit()/mode_list() when RELEASE_= CRUNCH is defined. However, you should be able to get through your problem by adjusting your b= oot_crunch.conf slightly: Try http://pastebin.com/Ge6UCZEZ The difference being: --- boot_crunch.conf.orig 2013-01-03 16:29:20.000000000 -0800 +++ boot_crunch.conf 2013-01-03 16:29:13.000000000 -0800 @@ -17,6 +17,7 @@ =20 srcdirs /usr/src/sbin progs camcontrol +special camcontrol objs camcontrol.o modeedit.o util.o progs dhclient progs fsck_ffs progs ifconfig --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.