Build fails - ERROR Building libtool



  • Thanks wagonza. I try to keep my build servers up-to-date. This is why I would like for the build scripts to rebuild ports. Right now, it looks like if the port is already installed, it skips building it. I would like to keep it so that if /tmp/pgPorts_forced_build_required is still there to have it rebuild all the ports in the list with at least the BATCH and FORCE_PKG_REGISTER options set so that the ports and the installed files are updated. Let me know if that is just not realistic.



  • No problem. Do a ./update_git_repos.sh and rebuild it should be working now.
    Ill look at the /tmp/pfPorts_forced_build_required bit and see - it still needs a lot of tuning.



  • Thanks wagonza … I will let you know the outcome.



  • Unfortunately the error issue persists.

    
    >>> Building gogoc(gogoc-1.2)...Done.
    >>> Ports with failures:        4
    >>> Building libart_lgpl(libart_lgpl-2.3.21,1)...ERROR!
    >>> Building freetype2(freetype2-2.4.2)...ERROR!
    >>> Building olsrd(olsrd-0.5.6.r7)...ERROR!
    >>> Building ioncube(ioncube-4.0.12)...ERROR!
    >>> Building athstats...main.c: In function 'getfmt':
    main.c:73: warning: implicit declaration of function 'strcasecmp'
    Done!
    >>> Building tools/crytpo...Done!
    ==> End of pfPorts...
    
    


  • and these are mine.

    
    >>> Building ipfw-classifyd(ipfw-classifyd-0.1)...ERROR!
    >>> File not found ipfw-classifyd				/usr/ports/net/ipfw-classifyd				/usr/local/sbin/ipfw-classifyd - /usr/local/sbin/ipfw-classifyd
    >>> Building mpd5(mpd-5.6)...ERROR!
    >>> File not found mpd5						/usr/ports/net/mpd5							/usr/local/sbin/mpd5 - /usr/local/sbin/mpd5
    >>> Building olsrd(olsrd-0.5.6.r7)...ERROR!
    >>> File not found olsrd						/usr/ports/net/olsrd						/usr/local/sbin/olsrd - /usr/local/sbin/olsrd
    >>> Building php52-pfSense-module(php52-pfSense-module-0.1)...ERROR!
    >>> File not found php52-pfSense-module		/usr/ports/devel/php52-pfSense-module		/usr/local/lib/php/20060613/pfSense.so - /usr/local/lib/php/20060613/pfSense.so
    >>> Building ioncube(ioncube-4.0.12)...ERROR!
    >>> File not found ioncube 					/usr/ports/devel/ioncube					/usr/local/lib/php/20060613/ioncube/ioncube_loader.so - /usr/local/lib/php/20060613/ioncube/ioncube_loader.so
    
    


  • Did you update your ports tree prior to all of this?



  • Yes … I run a script that does that ...

    
    #!/bin/sh
    
    rm -rf /tmp/*
    portsnap fetch extract
    csup -h cvsup17.freebsd.org /usr/share/examples/cvsup/standard-supfile
    cd /home/pfsense/tools/builder_scripts
    ./clean_build.sh
    ./update_git_repos.sh
    rm -rf /home/pfsense/installer
    /cvsup_bsdinstaller ; ./rebuild_bsdinstaller.sh
    ./set_version.sh RELENG_2_1 cvsup17.freebsd.org email email
    cd /home/pfsense/tools/pfPorts/php5; make -DBATCH -DFORCE_PKG_REGISTER -DNOPORTDOCS clean all install clean
    cd /home/pfsense/tools/pfPorts/php5-pfSense-module/; make -DBATCH -DFORCE_PKG_REGISTER -DNOPORTDOCS all install clean
    cd /usr/ports/devel/readline/; make -DBATCH -DFORCE_PKG_REGISTER -DNOPORTDOCS all install clean
    cd /usr/ports/curl; make -DBATCH -DFORCE_PKG_REGISTER -DNOPORTDOCS all install clean
    cd /home/pfsense/tools/builder_scripts
    ./build_iso.sh
    ./build_updates.sh
    
    


  • I do the same basic thing for 2.0.1 builds as well.



  • Down to 2 errors on the 2.0.1 builds. I will probably try the 2.1 builds tonight.

    >>> Ports with failures:        2
    >>> Building olsrd(olsrd-0.5.6.r7)...ERROR!
    >>> Building ioncube(ioncube-4.0.12)...ERROR!
    >>> Building athstats...main.c: In function 'getfmt':
    main.c:73: warning: implicit declaration of function 'strcasecmp'
    Done!
    >>> Building tools/crytpo...Done!
    ==> End of pfPorts...
    

    It still skips when it should not.



  • I meant 'portsnap fetch update' for the ports tree.

    Those two errors are expected. OLSRD will be moved and dont worry about ioncube.



  • I will try that out on some 2.1 builds tonight, or is this only for the 2.0 series?



  • That is for both.



  • @wagonza:

    I meant 'portsnap fetch update' for the ports tree.

    Those two errors are expected. OLSRD will be moved and dont worry about ioncube.

    Hi again. Like you said,  these ports are failed. Even so I build an iso image and it works correctly now. But I'm worried about if it crashes.



  • Mine also errors, but continues the build. I have run on them and everything seems just fine.



  • @podilarius:

    Mine also errors, but continues the build. I have run on them and everything seems just fine.

    They still fail at me. What about you?



  • I have not run a build in a few days, and since snapshots are behind (May 2nd is the latest), there is probably a problem.
    Please post the exact error you are getting. This will help the developers fix the error.


  • Rebel Alliance Developer Netgate

    There was no problem with the build process in general. Snapshots were only off because the ova build was grabbing a conflicting port to one that was already on the builders. All fixed up now.

    olsrd is going to be moved out of base and back to a package, so don't worry too much about that (few people, if any, need/use it anyhow), and ioncube isn't necessary yet.



  • Has anyone attempted a build with 9.0 ???
    Wanting to try the Mellanox support with IPoIB

    Thanks


  • Rebel Alliance Developer Netgate

    Yes, there are even patches in there for 9, and it "mostly" works but there were many problems… random freezes, lots of things in the OS that we needed to code around (check redmine, there's a whole tree of 'em), formats of various things changed that need to be adjusted for.

    So it might function, if you're lucky, but don't expect a miracle.

    If it actually worked properly, we'd be using it.



  • @jimp:

    Yes, there are even patches in there for 9, and it "mostly" works but there were many problems… random freezes, lots of things in the OS that we needed to code around (check redmine, there's a whole tree of 'em), formats of various things changed that need to be adjusted for.

    So it might function, if you're lucky, but don't expect a miracle.

    If it actually worked properly, we'd be using it.

    Thanks for the heads up…
    I tried to register on redmine and had no luck.

    I still would be interested on running it buggy or not at least it would generate logs that can be used for patches


Log in to reply