building crunchgen fails

[Devin Teske]

On Jan 23, 2013, at 8:44 AM, Rick Miller wrote:

> On Wed, Jan 23, 2013 at 11:01 AM, Devin Teske <devin.teske at fisglobal.com> wrote:
>> 
>> On Jan 23, 2013, at 7:22 AM, Rick Miller wrote:
>> 
>>> Hi All,
>>> 
>>> When executing crunchgen -o boot_crunch.conf && make -f boot_crunch.mk
>>> I get the following error:
>>> 
>>> 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
>>> 
>>> Stop in /tmp/crunchtmp.
>>> 
>>> 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...
>>> 
>>> The boot_crunch.conf can be viewed at https://urldefense.proofpoint.com/v1/url?u=http://pastebin.com/ZwVPQn3h&k=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=Mrjs6vR4%2Faj2Ns9%2FssHJjg%3D%3D%0A&m=Hnn4NG9Hyf8%2F%2F0%2FFE6hjIC649weMNcRXdV4V8oYmXGs%3D%0A&s=a3915bb0ab3862b707fc373a12f153257c6a06b1ee05925c9714f88fc81d783b
>>> 
>> 
>> According to the Makefile, if RELEASE_CRUNCH is defined, then modeedit.o object 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 boot_crunch.conf slightly:
>> 
>> Try https://urldefense.proofpoint.com/v1/url?u=http://pastebin.com/Ge6UCZEZ&k=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=Mrjs6vR4%2Faj2Ns9%2FssHJjg%3D%3D%0A&m=Hnn4NG9Hyf8%2F%2F0%2FFE6hjIC649weMNcRXdV4V8oYmXGs%3D%0A&s=27ceca7c7f03287568ea4d5c6af082fdf0e1182cdd8b90841429dd7d55752e42
>> 
>> 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 @@
>> 
>> srcdirs /usr/src/sbin
>> progs camcontrol
>> +special camcontrol objs camcontrol.o modeedit.o util.o
>> progs dhclient
>> progs fsck_ffs
>> progs ifconfig
> 
> Thanks, Devin!  That worked...which Makefile did you find this in?
> 

sbin/camcontrol/Makefile
-- 
Cheers,
Devin

_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.