New error running build_update.sh



  • I'm not (<- what, how tired was I??) ;) getting this error in the Developer Edition:

    install -o root -g wheel -m 444 com_err.3.gz  /usr/local/pfsense-fs/usr/share/man/man3^M
    install: com_err.3.gz: No such file or directory^M
    *** Error code 71^M
    1 error^M
    *** Error code 2^M
    1 error^M
    *** Error code 2^M
    1 error^M
    *** Error code 2^M
    1 error^M
    *** Error code 2^M
    1 error^M
    *** Error code 2^M
    1 error^M
    

    (This was in /home/pfsense/freesbie2/.tmp_installworld as a result of running build_update.sh)

    Any ideas how to fix this? The original cvsup_current runs fine and builds the iso without errors.

    TIA



  • from a shell:
    rm -rf /usr/obj*

    Restart build with cvsup_sync.sh



  • Thanks once again!! I'll give it a try!! :D



  • I couldn't find cvsup_sync.sh

    Here's what I have in the cvs vein:

    # find /home/pfsense/ -type f -iname "cvs*"
    /home/pfsense/cvsroot/tools/builder_scripts/cvsup_current,v
    /home/pfsense/cvsroot/tools/cvs,v
    /home/pfsense/cvsroot/tools/cvs_sync.sh,v
    /home/pfsense/cvsroot/pfSense/usr/local/sbin/Attic/cvs,v
    /home/pfsense/cvsroot/pfSense/usr/local/sbin/cvs_sync.sh,v
    /home/pfsense/cvsroot/CVSROOT/cvswrappers
    /home/pfsense/cvsroot/CVSROOT/cvswrappers,v
    /home/pfsense/cvsroot/CVSROOT/cvs_acls.pl
    /home/pfsense/cvsroot/CVSROOT/cvs_acls.pl,v
    /home/pfsense/tools/cvs
    /home/pfsense/tools/cvs_sync.sh
    /home/pfsense/tools/builder_scripts/cvsup_current
    /home/pfsense/pfSense/usr/local/sbin/cvs_sync.sh
    

    Assuming it's just semantics I'm currently running /home/pfsense/pfSense/usr/local/sbin/cvs_sync.sh

    (The one in the tools directory wasn't executable, so not wanting to mess things up I just ran the one that was…)

    Is this the correct script or is my install missing that cvsup_sync.sh file?



  • cvs_sync.sh



  • Cool, thanks!!

    I ran it, I still got errors trying to build the image, but I'll see if I can sort them out. I haven't had time to look over the logs.


Locked