Date: Wed, 23 Jan 2013 10:19:44 -0800 From: Devin Teske <devin.teske@fisglobal.com> To: Rick Miller <vmiller@hostileadmin.com> Cc: Devin Teske <dteske@freebsd.org>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: building crunchgen fails Message-ID: <662D7C34-8A06-412D-9319-C988D8242156@fisglobal.com> In-Reply-To: <CAHzLAVGK36wvkS%2BD50baBEOrwkaYs1Um00XQLeyfn8qpErv4TQ@mail.gmail.com> References: <CAHzLAVHKXxP6Hb7%2BZxv857X1eJeG3CmghcJzKukH6w_U8cJTnw@mail.gmail.com> <82E7A4A3-B65D-4ECA-BEF4-FD67445AF1B2@fisglobal.com> <CAHzLAVGK36wvkS%2BD50baBEOrwkaYs1Um00XQLeyfn8qpErv4TQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 23, 2013, at 8:44 AM, Rick Miller wrote: > On Wed, Jan 23, 2013 at 11:01 AM, Devin Teske <devin.teske@fisglobal.com>= wrote: >>=20 >> On Jan 23, 2013, at 7:22 AM, Rick Miller wrote: >>=20 >>> 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 https://urldefense.proofpoint.com= /v1/url?u=3Dhttp://pastebin.com/ZwVPQn3h&k=3D%2FbkpAUdJWZuiTILCq%2FFnQg%3D%= 3D%0A&r=3DMrjs6vR4%2Faj2Ns9%2FssHJjg%3D%3D%0A&m=3DHnn4NG9Hyf8%2F%2F0%2FFE6h= jIC649weMNcRXdV4V8oYmXGs%3D%0A&s=3Da3915bb0ab3862b707fc373a12f153257c6a06b1= ee05925c9714f88fc81d783b >>>=20 >>=20 >> According to the Makefile, if RELEASE_CRUNCH is defined, then modeedit.o= object is omitted (causing your undefined references). >>=20 >> I perceive the long-term real solution would be to patch camcontrol.c (a= nd pedantically camcontrol.h) to not use mode_edit()/mode_list() when RELEA= SE_CRUNCH is defined. >>=20 >> However, you should be able to get through your problem by adjusting you= r boot_crunch.conf slightly: >>=20 >> Try https://urldefense.proofpoint.com/v1/url?u=3Dhttp://pastebin.com/Ge6= UCZEZ&k=3D%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=3DMrjs6vR4%2Faj2Ns9%2FssHJj= g%3D%3D%0A&m=3DHnn4NG9Hyf8%2F%2F0%2FFE6hjIC649weMNcRXdV4V8oYmXGs%3D%0A&s=3D= 27ceca7c7f03287568ea4d5c6af082fdf0e1182cdd8b90841429dd7d55752e42 >>=20 >> The difference being: >>=20 >> --- 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 > Thanks, Devin! That worked...which Makefile did you find this in? >=20 sbin/camcontrol/Makefile --=20 Cheers, 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?662D7C34-8A06-412D-9319-C988D8242156>