I am whining for a few days to compile NanoBSD image. The same configurations works with FreeBSD 8, but it fails. My configurations are: freeserver.conf is at http://pastebin.com/q8YauEcd FREESERVER is at http://pastebin.com/4YC1Xu11 Build log is at https://docs.google.com/open?id=0B5PA_hdlux-AN012OW5MSnVSNEMwM0NpTGw4UmwwUQ I posted them to the postbin and the google doc because they are too large to attach here. Since the problem was not solved even after posting to the forum ( http://forums.freebsd.org/showthread.php?t=30331), I am posting to this mailing list to get the inputs from FreeBSD gurus. Any hints will be appreciated! Thanks! /zenny
Thanks, Dewayne. On Mon, Mar 12, 2012 at 11:22 PM, Dewayne Geraghty < dewayne.geraghty@heuristicsystems.com.au> wrote:> Zenny, > > Would you add WITHOUT_CLANG= to your alix.conf (src.conf) and remove -j 6 > from your make command; and retry. I suspect that your build logs may not > be attributing the failure to the correct area of the build; and with the > large number of things turned off in your alix.conf that there may be a > clang dependency that is disabled during the build. >Tried with WITHOUT_CLANG=true in the configuration and remove -j 6, too, but again it fails with: wpa.o: In function `wpa_sm_rx_eapol':> > wpa.c:(.text+0x2d2e): undefined reference to `rc4_skip' > > wpa.c:(.text+0x31c8): undefined reference to `rc4_skip' > > wpa_supplicant.o: In function `wpa_supplicant_init': > > wpa_supplicant.c:(.text+0x1f83): undefined reference to `eap_register_meth > > *** Error code 1 > > >> Stop in /usr/src/usr.sbin/wpa/wpa_supplicant. > > *** Error code 1 > > >> Stop in /usr/src/usr.sbin/wpa. > > *** Error code 1 > > >> Stop in /usr/src/usr.sbin. > > *** Error code 1 > > >> Stop in /usr/src. > > *** Error code 1 > > >> Stop in /usr/src. > > *** Error code 1 > > >> Stop in /usr/src. > >> > If you achieve a successful build, you're welcome to include this reply in > your mail-list post. > Regards, Dewayne. > >
On 3/13/12, Dewayne Geraghty <dewayne.geraghty@heuristicsystems.com.au> wrote:> Thinks aren't looking good. I've had this problem a few years ago when > first using nanobsd. I was chasing the problem until in the end I removed > all exclusions from the build, and then added exclusions (WITHOUT_...) > until something broke, which revealed the problem. This could take awhile. > > To my casual eye, the issue seems to be related to the RC4 algorithm which > might point to a problem with openssl. I don't have access to any freebsd > machines for the next two days (I'm in transit). At a guess you might need > to either: > A) enable the RC4 algorithm in the openssl build, though I think its on by > default or > B) review the src.conf file for anything with WPA_SUPPLICANT* and add that > to your "WITHOUT_" list; at least until you've gotten one complete build > under your belt.Thanks for your input. Yep, that seemed working with a few things that I did: 1) removed all source and ports and csup/portsnap them 2) In the src.conf file, I figured out that disabling WPA_SUPPLICANT (#WITHOUT_WPA_SUPPLICANT=true") is preventing the build world. 3) In the kernel file, I have to change from COMPAT_IA32 to COMPAT_FREEBSD32 (the former is obsoleted in FreeBSD9-RELEASE) to complete the build kernel. BTW, I am just wondering where and how to specify any kernel patches to be applied to a nanobsd image? Could not figure out any documentation.> > It's tricky business getting the build the way that you'd like it, but once > achieved, you'll be knowledgeable with your result. > > Things to note: WITHOUT_ENCRYPTION have undocumented side-effects like not > building geli, nor libarchive - don't use this knob; and WITHOUT_OBJC will > cause problems that took me lot of time to identify.Thank you for the pointers.> > Good luck. > > Kind regards, Dewayne. > > > >