Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Building pfSense - Something basic I'm doing wrong?

    Scheduled Pinned Locked Moved Development
    56 Posts 14 Posters 11.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      bhawk6901
      last edited by

      Apply patches goes fine, next i get the error as shwon in attacchment. I made sure to change git.pfmechanics to
      export FREEBSD_REPO_BASE=https://svn0.us-east.freebsd.org/base
      also every time i invoke build iso option, it downloads sources again, any way to skip that?

      Edit: snapshot of pfsensebuild.conf is att

      Capture.PNG
      Capture.PNG_thumb
      Capture2.PNG
      Capture2.PNG_thumb

      1 Reply Last reply Reply Quote 0
      • B
        bhawk6901
        last edited by

        UPDATE: when i apply patches manually it goes fine but when i invoke the buid.sh iso option patches get rejected. Any idea what might be causing that?

        1 Reply Last reply Reply Quote 0
        • bmeeksB
          bmeeks
          last edited by

          @bhawk6901:

          UPDATE: when i apply patches manually it goes fine but when i invoke the buid.sh iso option patches get rejected. Any idea what might be causing that?

          I haven't tried to build a 2.2 ISO in the last couple of months, so I don't know if my setup still works or not.  However, in your screen capture of the error notice that it says "…cloning git@git.pfmechanics.com...".  This means it is trying to use pfmechanics.com to checkout source code.  I'm pretty sure that is an internal-only server at ESF, and thus you can't access it.  Don't know if the script is hard-coded with this value or if it is customizable.

          Bill

          1 Reply Last reply Reply Quote 0
          • H
            heper
            last edited by

            @bmeeks:

            @bhawk6901:

            UPDATE: when i apply patches manually it goes fine but when i invoke the buid.sh iso option patches get rejected. Any idea what might be causing that?

            I haven't tried to build a 2.2 ISO in the last couple of months, so I don't know if my setup still works or not.  However, in your screen capture of the error notice that it says "…cloning git@git.pfmechanics.com...".  This means it is trying to use pfmechanics.com to checkout source code.  I'm pretty sure that is an internal-only server at ESF, and thus you can't access it.  Don't know if the script is hard-coded with this value or if it is customizable.

            Bill

            yes pfmechanics is private…

            see this post for the relevant public git repo's: https://forum.pfsense.org/index.php?topic=76132.msg415051#msg415051

            1 Reply Last reply Reply Quote 0
            • B
              bhawk6901
              last edited by

              there has been progress. Now though when building ports, strongswan, php5 and resultantly others depending on php5 such as php5-pfsensemodule and a number of others as shown in attachment.
              Error with php5 being

              php55-5.5.13 conflicts with installed package(s):
                    php53-5.3.28

              They will not build together.
                    Please remove them first with pkg delete.
              *** Error code 1

              Stop.
              make: stopped in /usr/ports/lang/php55

              any help please?
              EDIT: tried building with make_jobs_unsafe=yes as well as otherwise. This is the log when i build with make_jobs_unsafe=yes

              Capture.PNG
              Capture.PNG_thumb
              php55.txt
              php55-pfSense-module.txt

              1 Reply Last reply Reply Quote 0
              • B
                bhawk6901
                last edited by

                update: php55 errors are gone. uninstalled php53 first
                still stuck on strongswan and libevent errors though

                1 Reply Last reply Reply Quote 0
                • B
                  bhawk6901
                  last edited by

                  went back to building on 8.3, All ports get build except for lighttpd.
                  Error log as shown in attachment

                  I went ahead to make the iso which got built succesfully but the web  configurator page wouldnt load which i assume is due to absence of lighttpd.
                  What's causing the error? Help please

                  Capture.PNG
                  Capture.PNG_thumb

                  1 Reply Last reply Reply Quote 0
                  • bmeeksB
                    bmeeks
                    last edited by

                    @bhawk6901:

                    went back to building on 8.3, All ports get build except for lighttpd.
                    Error log as shown in attachment

                    I went ahead to make the iso which got built succesfully but the web  configurator page wouldnt load which i assume is due to absence of lighttpd.
                    What's causing the error? Help please

                    It's a problem with the pkgconfig tool version. Unfortunately, that's about the extent of my knowledge about this on FreeBSD.  I recall hitting the same error myself in the past.  I think I solved it by manually altering the Makefile, but as soon as you do a refresh from the pfsense-tools repository, your change will be overwritten.  I have not looked, but are there different Git branches for pfsense-tools?  Pulling "master" will of course bring down stuff optimized for FreeBSD 10.  If older versions exist, they may contain pfPorts files compatible with the older FreeBSD 8.3 tools.

                    Bill

                    1 Reply Last reply Reply Quote 0
                    • B
                      bhawk6901
                      last edited by

                      @bmeeks:

                      It's a problem with the pkgconfig tool version. Unfortunately, that's about the extent of my knowledge about this on FreeBSD.  I recall hitting the same error myself in the past.  I think I solved it by manually altering the Makefile, but as soon as you do a refresh from the pfsense-tools repository, your change will be overwritten.
                      Bill

                      Can you please guide me to what change did you make exactly? I studied the Makefile but there was only one metnion of pkgconfig

                      GNU_CONFIGURE= yes
                      USES= gmake libtool pkgconfig tar:bzip2

                      One issue which i faced while building 2.2 via v10 was that whenever it tried to clone pfsense from repository, it would fail. When i checked git repository, i couldnt find RELENG_2_2 branch. Is that why if was failing and reporting that pfSenseGITREPO path doesnt exist?

                      1 Reply Last reply Reply Quote 0
                      • bmeeksB
                        bmeeks
                        last edited by

                        @bhawk6901:

                        @bmeeks:

                        It's a problem with the pkgconfig tool version. Unfortunately, that's about the extent of my knowledge about this on FreeBSD.  I recall hitting the same error myself in the past.  I think I solved it by manually altering the Makefile, but as soon as you do a refresh from the pfsense-tools repository, your change will be overwritten.
                        Bill

                        Can you please guide me to what change did you make exactly? I studied the Makefile but there was only one metnion of pkgconfig

                        GNU_CONFIGURE= yes
                        USES= gmake libtool pkgconfig tar:bzip2

                        One issue which i faced while building 2.2 via v10 was that whenever it tried to clone pfsense from repository, it would fail. When i checked git repository, i couldnt find RELENG_2_2 branch. Is that why if was failing and reporting that pfSenseGITREPO path doesnt exist?

                        I don't remember what I changed.  I just did a lot of Google searching and fiddled around with the USES section in the Makefile (looks like you are already doing that).  I know at one point I also went exploring through /usr/ports/devel and installed some other stuff (but again, sorry I did not keep track of what I did).  I only use my builders to produce PBIs for my supported packages: Snort and Suricata.  I don't build ISOs routinely.  I built one, and only just once.  Actually I think my builder is also currently "broken" for building an ISO.  It works fine for my purpose of building PBIs, though.

                        As for your second question, you are correct there is currently no RELENG_2_2 branch.  If you have not done so already, from your builder and in the tools directory issue this command to see the available remote branches:

                        
git remote show origin

                        Bill

                        1 Reply Last reply Reply Quote 0
                        • C
                          clem68
                          last edited by

                          The master branch of pfsense-tools supports building on FreeBSD 8.3 as well as 10.
                          Ports are not tied to a FreeBSD version, but there should be no problem building them up-to-date (I have done so).

                          Regarding pkgconf, I had a problem related to its obsolescence (it needs to be replaced by pkg-config) and maybe you are facing the same thing. The steps required to deal with this  are described in UPGRADING , for example you can do:

                          portmaster -o devel/pkgconf devel/pkg-config
                          1 Reply Last reply Reply Quote 0
                          • B
                            bhawk6901
                            last edited by

                            @clem68:

                            The master branch of pfsense-tools supports building on FreeBSD 8.3 as well as 10.
                            Ports are not tied to a FreeBSD version, but there should be no problem building them up-to-date (I have done so).

                            Regarding pkgconf, I had a problem related to its obsolescence (it needs to be replaced by pkg-config) and maybe you are facing the same thing. The steps required to deal with this  are described in UPGRADING , for example you can do:

                            portmaster -o devel/pkgconf devel/pkg-config

                            Thanks for the guidance. I'll look into it further :)

                            meanwhile regarding 2.2, which version do i specify to get build 2.2? I performed git remote origin and found these

                            Remote branches:
                                RELENG_1_2 tracked
                                RELENG_2_0 tracked
                                RELENG_2_1 tracked
                                devel      tracked
                                master    tracked
                              Local branch configured for 'git pull':

                            1 Reply Last reply Reply Quote 0
                            • B
                              bhawk6901
                              last edited by

                              @clem68:

                              The master branch of pfsense-tools supports building on FreeBSD 8.3 as well as 10.
                              Ports are not tied to a FreeBSD version, but there should be no problem building them up-to-date (I have done so).

                              Regarding pkgconf, I had a problem related to its obsolescence (it needs to be replaced by pkg-config) and maybe you are facing the same thing. The steps required to deal with this  are described in UPGRADING , for example you can do:

                              portmaster -o devel/pkgconf devel/pkg-config

                              i had pkgconf installed, if im not wrong pkgconf replaced pkg-config.you mean i should revert to old i,e. pkg-config?

                              lighttpd.txt

                              1 Reply Last reply Reply Quote 0
                              • B
                                bhawk6901
                                last edited by

                                messed around with pkg-plist, removed "@" symbols and error changes to

                                Creating bzip'd tar ball in '/usr/ports/www/lighttpd/work/pkg/lighttpd-1.4.35_2.tbz'
                                tar: sample etc/lighttpd/lighttpd.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/modules.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/access_log.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/auth.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/cml.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/cgi.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/compress.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/debug.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/dirlisting.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/evhost.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/expire.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/fastcgi.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/magnet.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/mime.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/mysql_vhost.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/proxy.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/rrdtool.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/scgi.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/secdownload.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/simple_vhost.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/ssi.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/status.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/trigger_b4_dl.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/userdir.conf.sample: Cannot stat: No such file or directory
                                tar: sample etc/lighttpd/conf.d/webdav.conf.sample: Cannot stat: No such file or directory
                                tar: dirrm lib/lighttpd: Cannot stat: No such file or directory
                                tar: dirrmtry etc/lighttpd/vhosts.d: Cannot stat: No such file or directory
                                tar: dirrmtry etc/lighttpd/conf.d: Cannot stat: No such file or directory
                                tar: dirrmtry etc/lighttpd: Cannot stat: No such file or directory
                                tar: Error exit delayed from previous errors.
                                pkg_create: make_dist: tar command failed with code 256
                                *** Error code 1

                                1 Reply Last reply Reply Quote 0
                                • B
                                  bhawk6901
                                  last edited by

                                  making a few changed to pkg-plist in lighttpd made the errors go away
                                  iso was built but it was a livecd iso. is that what was supposed to be built? or are there other isos we can get?
                                  Also when i tried to install from live cd i got the error

                                  dfuife_curses missing

                                  missing. What may have caused that?

                                  1 Reply Last reply Reply Quote 0
                                  • P
                                    PiBa
                                    last edited by

                                    Live iso is the only iso that is needed for a regular installation of pfSense.
                                    However is seems during building the iso the installer is not properly build/included..

                                    Solution is to use another git repository ( git://github.com/Key4ce/bsdinstaller.git ) as written here:
                                    https://forum.pfsense.org/index.php?topic=82845.msg453695#msg453695

                                    Or wait until his pull-request gets applied.: https://github.com/pfsense/bsdinstaller/pull/2

                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post
                                    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.