|
osdir.com mailing list archive |
|
Subject: Developer bootstrap errors - msg#00023List: security.firewalls.pfsense.userI'm trying to get started with pfsense development (my goal is to make it an isp-grade access server). I am trying to get the developer cd boot-strapped by so far had no luck with each of the ISO versions I could find (including 1.0release and the latest builds from 02-23-2007). The problem is the same: the initial dev_bootstrap.sh fails with an error on the "enc" device during kernel configuration (I guess there's a patch for the IPSEC shaping), logs attached at the end for clarity. As a work-aroung I try to call cvsup_current (in /home/pftools/.....: with "sh ./cvsup_current") and it runs properly (cvs update and some patches that succeed) until I come to some failed patches. My question is: How do I get pfsense to build properly (i.e. RELENG_6_1) so that I can make my first modifications on a reasonably stable tree before moving to head? Thank you for helping! Paul PS: Here's the attached logs: ------------ Initial dev_bootstrap.sh errors (with clean install): ------------------------- #### Building world for i386 architecture #### >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything #### Building kernel for i386 architecture #### >>> Kernel build for pfSense.6 started on Sat Feb 24 08:59:35 UTC 2007 >>> stage 1: configuring the kernel Something went wrong, check errors! Log saved on /usr/obj.pfSense/home/pfsense/freesbie2/.tmp_buildkernel *** Signal 15 Stop in /home/pfsense/freesbie2. No matching processes were found # tail -n 30 /usr/obj.pfSense/home/pfsense/freesbie2/.tmp_buildkernel -------------------------------------------------------------- >>> Kernel build for pfSense.6 started on Sat Feb 24 08:59:35 UTC 2007 -------------------------------------------------------------- ===> pfSense.6 mkdir -p /usr/obj.pfSense/usr/src/sys -------------------------------------------------------------- >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /usr/src/sys/i386/conf; PATH=/usr/obj.pfSense/usr/src/tmp/legacy/usr/sbin:/usr/obj.pfSense/usr/src/tmp/legacy/usr/bin:/usr/obj.pfSense/usr/src/tmp/legacy/usr/games:/usr/obj.pfSense/usr/src/tmp/usr/sbin:/usr/obj.pfSense/usr/src/tmp/usr/bin:/usr/obj.pfSense/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /usr/obj.pfSense/usr/src/sys/pfSense.6 /home/pfsense/tools/builder_scripts/conf/pfSense.6 config: Error: device "enc" is unknown config: 1 errors *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Thread at a glance:
Previous Message by Date: click to view message previewRe: DST patchSorry but we do not give out firm dates. When it is done is the answer. Either way folks can upgrade to the latest version which features FreeBSD 6.2 from http://snapshots.pfsense.com/FreeBSD6/RELENG_1/updates/ so its a moot point. Scott On 2/23/07, Dmitry Sorokin <dimon@xxxxxxxxxxxxx> wrote: Hi All, Just wandering if new version based on FreeBSD 6.2 will be released before March 11th or a patch of some king will be posted to address this issue. Please check this thread: http://docs.freebsd.org/cgi/getmsg.cgi? fetch=1494952+0+/usr/local/www/db/text/2007/freebsd-questions/20070204.freebsd- questions Best regards, Dmitry Spam detection software, running on the system "intellinet.ca", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Dear Friend, Wonderful download site for your favourite ring tones and hello tunes in English, Hindi and All South Indian Languages…!!! http://simurl.com/rngtns [...] Content analysis details: (9.5 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 DK_SIGNED Domain Keys: message has an unverified signature 1.6 DEAR_FRIEND BODY: Dear Friend? That's not very dear! 0.1 HTML_90_100 BODY: Message is 90% to 100% HTML 0.0 HTML_MESSAGE BODY: HTML included in message 3.5 BAYES_99 BODY: Bayesian spam probability is 99 to 100% [score: 1.0000] 2.3 HTML_TINY_FONT RAW: body contains 1 or 0-point font 0.4 SARE_SPEC_LEO_LINE03a RAW: common Leo body text 0.2 DNS_FROM_RFC_ABUSE RBL: Envelope sender in abuse.rfc-ignorant.org 1.4 DNS_FROM_RFC_WHOIS RBL: Envelope sender in whois.rfc-ignorant.org 0.2 URIBL_GREY Contains an URL listed in the URIBL greylist [URIs: simurl.com] 0.3 PLING_PLING Subject has lots of exclamation marks 0.8 MANY_EXCLAMATIONS Subject has many exclamations -1.5 AWL AWL: From: address is in the auto white-list Next Message by Date: click to view message previewRe: Developer bootstrap errorsI will answer my own question: the problem is that RELENG_6_1 does not (currently) compile. To fix I changed the "freebsd_branch" variable in pfsense_local.sh to RELENG_6_2 that compiled cleanly. Now I have a second problem: Each time I call build_iso.sh the builder script will resync with the pfsense CVS hence loosing any changes that I make. On the wiki there's some info pointing me to define a SKIP_CHECKOUT variable, but update_cvs_depot defined in builder_common.sh which is responsible for taking care of this, only checks for SKIP_RSYNC and always updates from CVS (regardles what it states): update_cvs_depot() { # Update cvs depot. If SKIP_RSYNC is defined, skip the RSYNC update # and prompt if the operator would like to download cvs.tgz from pfsense.com . # If also SKIP_CHECKOUT is defined, don't update the tree at all if [ -z "${SKIP_RSYNC:-}" ]; then rm -rf $BASE_DIR/pfSense rsync -avz ${CVS_USER}@${CVS_IP}:/cvsroot /home/pfsense/ (cd $BASE_DIR && cvs -d /home/pfsense/cvsroot co -r ${PFSENSETAG} pfSense) fixup_libmap else cvsup pfSense-supfile rm -rf pfSense rm -rf $BASE_DIR/pfSense (cd $BASE_DIR && cvs -d /home/pfsense/cvsroot co -r ${PFSENSETAG} pfSense) (cd $BASE_DIR/tools/ && cvs update -d) fixup_libmap fi } Am I looking at the wrong code or is there a different way to not update from CVS during build? Paul. Previous Message by Thread: click to view message previewDST patchHi All, Just wandering if new version based on FreeBSD 6.2 will be released before March 11th or a patch of some king will be posted to address this issue. Please check this thread: http://docs.freebsd.org/cgi/getmsg.cgi? fetch=1494952+0+/usr/local/www/db/text/2007/freebsd-questions/20070204.freebsd- questions Best regards, Dmitry Spam detection software, running on the system "intellinet.ca", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Dear Friend, Wonderful download site for your favourite ring tones and hello tunes in English, Hindi and All South Indian Languages?!!! http://simurl.com/rngtns [...] Content analysis details: (9.5 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 DK_SIGNED Domain Keys: message has an unverified signature 1.6 DEAR_FRIEND BODY: Dear Friend? That's not very dear! 0.1 HTML_90_100 BODY: Message is 90% to 100% HTML 0.0 HTML_MESSAGE BODY: HTML included in message 3.5 BAYES_99 BODY: Bayesian spam probability is 99 to 100% [score: 1.0000] 2.3 HTML_TINY_FONT RAW: body contains 1 or 0-point font 0.4 SARE_SPEC_LEO_LINE03a RAW: common Leo body text 0.2 DNS_FROM_RFC_ABUSE RBL: Envelope sender in abuse.rfc-ignorant.org 1.4 DNS_FROM_RFC_WHOIS RBL: Envelope sender in whois.rfc-ignorant.org 0.2 URIBL_GREY Contains an URL listed in the URIBL greylist [URIs: simurl.com] 0.3 PLING_PLING Subject has lots of exclamation marks 0.8 MANY_EXCLAMATIONS Subject has many exclamations -1.5 AWL AWL: From: address is in the auto white-list Next Message by Thread: click to view message previewRe: Developer bootstrap errorsI will answer my own question: the problem is that RELENG_6_1 does not (currently) compile. To fix I changed the "freebsd_branch" variable in pfsense_local.sh to RELENG_6_2 that compiled cleanly. Now I have a second problem: Each time I call build_iso.sh the builder script will resync with the pfsense CVS hence loosing any changes that I make. On the wiki there's some info pointing me to define a SKIP_CHECKOUT variable, but update_cvs_depot defined in builder_common.sh which is responsible for taking care of this, only checks for SKIP_RSYNC and always updates from CVS (regardles what it states): update_cvs_depot() { # Update cvs depot. If SKIP_RSYNC is defined, skip the RSYNC update # and prompt if the operator would like to download cvs.tgz from pfsense.com . # If also SKIP_CHECKOUT is defined, don't update the tree at all if [ -z "${SKIP_RSYNC:-}" ]; then rm -rf $BASE_DIR/pfSense rsync -avz ${CVS_USER}@${CVS_IP}:/cvsroot /home/pfsense/ (cd $BASE_DIR && cvs -d /home/pfsense/cvsroot co -r ${PFSENSETAG} pfSense) fixup_libmap else cvsup pfSense-supfile rm -rf pfSense rm -rf $BASE_DIR/pfSense (cd $BASE_DIR && cvs -d /home/pfsense/cvsroot co -r ${PFSENSETAG} pfSense) (cd $BASE_DIR/tools/ && cvs update -d) fixup_libmap fi } Am I looking at the wrong code or is there a different way to not update from CVS during build? Paul. Loading Comments...
|
|
