Building pfSense - Something basic I'm doing wrong?

kpa

I got the RELENG_2_2 build working to a point where it can fetch the repositories and apply patches but it failed later on building one of the pfPorts (I think that where it failed but lack of proper status messages left me unsure). Expect a better report and bug reports when I have more time to dig deeper. The build system definitely needs some improvements to be usable for outsiders, it's quite difficult to understand even for me who happens to have quite a bit of experience with FreeBSD's build systems and building everything from source in general.

kpa

Ok I'm back again trying to build RELENG_2_2 for i386. The build started fine but errors in sysutils/squashfs-tools port. The log shows this:


cc -O2 -pipe -fno-strict-aliasing -std=gnu89  -I. -I/usr/local/include -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DFNM_EXTMATCH
=0 -D_GNU_SOURCE -DCOMP_DEFAULT=\"gzip\" -Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DLZO_SUPPORT  i386 -c -o mksquashfs.o mksquashfs.c
cc -O2 -pipe -fno-strict-aliasing -std=gnu89  -I. -I/usr/local/include -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DFNM_EXTMATCH
=0 -D_GNU_SOURCE -DCOMP_DEFAULT=\"gzip\" -Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DLZO_SUPPORT  i386 -c -o read_fs.o read_fs.c
cc: cc -O2 -pipe -fno-strict-aliasing -std=gnu89  -I. -I/usr/local/include -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DFNM_EXTM
ATCH=0 -D_GNU_SOURCE -DCOMP_DEFAULT=\"gzip\" -Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DLZO_SUPPORT  i386 -c -o sort.o sort.c
error: no such file or directory: 'i386'
cc: error: no such file or directory: 'i386'
cc -O2 -pipe -fno-strict-aliasing -std=gnu89  -I. -I/usr/local/include -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DFNM_EXTMATCH
=0 -D_GNU_SOURCE -DCOMP_DEFAULT=\"gzip\" -Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DLZO_SUPPORT  i386 -c -o swap.o swap.c
gmake[2]: *** [mksquashfs.o] Error 1
gmake[2]: *** Waiting for unfinished jobs....
gmake[2]: *** [read_fs.o] Error 1
cc: error: no such file or directory: 'i386'
cc: error: no such file or directory: 'i386'
gmake[2]: *** [sort.o] Error 1
gmake[2]: *** [swap.o] Error 1
gmake[2]: Leaving directory `/usr/ports/sysutils/squashfs-tools/work/squashfs4.2/squashfs-tools'
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/sysutils/squashfs-tools
*** Error code 1

Stop.
make: stopped in /usr/ports/sysutils/pcbsd-utils
Done!

The build continued though after the error with the buildworld part so I didn't stop it yet.

I'm using the most upto date ports tree from the official FreeBSD SVN repository, do I need to use a specific version of the ports tree?

My build host is:


FreeBSD freebsd10.rdnzl.info 10.0-STABLE FreeBSD 10.0-STABLE #2 r266005: Wed May 14 16:42:13 EEST 2014     kimmo@freebsd10.rdnzl.info:/usr/obj/usr/src/sys/VT  i386

(The VT kernel is just GENERIC kernel with the newcons console included so ignore that)

kpa

I was able to work around the error in my previous post by installing sysutils/pcbsd-utils manually before firing up the build.sh again. However this time the buildworld stopped with an error:


--- sbin.depend__D ---
/usr/pfSensesrc/src/sbin/pfctl/pfctl_qstats.c:41:10: fatal error: 'altq/altq_fairq.h' file not found
#include <altq altq_fairq.h="">^
1 error generated.</altq>

This is bad, very bad. The buildworld that is done with /usr/pfSensesrc sources is not finding its own include files (altq/altq_fairq.h is a pfSense addition and not present on vanilla FreeBSD 10). I am definitely not going to do a manual copy of the missing includes to /usr/include on the build host because that kind of manual step shouldn't be needed when the whole intention of the scripts is to automate the build process.

Here's a suggestion to all of you who are working on the tools repo. Every once in a while do a complete wipe of the build host and reinstall it from scratch using the latest FreeBSD stable/10 snapshot. Re-fetch all the repositories and redo all the configurations. This would reveal any problems that are caused by extra files that exist on the build host and are not present in a clean state when an outsider tries to repeat the build process starting from scratch.

Edit: Redmine ticket opened, https://redmine.pfsense.org/issues/3668.

eri--

Replied on redmine.

kpa

Fair enough. I'll summarize quickly what I have learned so far:

There is no documentation available for using the tools repo so one has trough trial and error and asking around gather the necessary information on how to use it. In my case the missing piece of information was that pfPorts needs to built first before anything else. Building of pfPorts is not done automatically if you just fire up the build script as```
build.sh iso


You need an ultra-clean FreeBSD installation on the build host because the tools want to build everything its way and anything non-standard in terms of configuration trips it very easily.

Building pfSense will "contaminate" your build host with pfSense speficic modifications. This is something I absolutely don't want and I'm now moving to using a jail as the build host.

More to follow later.

none

Hail,

jporter helped me to get the sources, but I can't find a post I had before that would walk through the steps to compile pfsense. I found the kernel dir (my main project), but can't figure out the what is the definitive script to config and build.

I tried the build.sh –configure get me issues:

%./build.sh --configure

You must first run ./set_version.sh !
See http://devwiki.pfsense.org/DevelopersBootStrapAndDevIso for more information.

You can also run ./menu.sh which will assist with the available options

is there a new version of http://devwiki.pfsense.org/DevelopersBootStrapAndDevIso ?

thanks,

none

ps: if I should open new thread, please say. As this is on the subject, I figured here as a right place.

Guest

@kpa:

Fair enough. I'll summarize quickly what I have learned so far:

There is no documentation available for using the tools repo so one has trough trial and error and asking around gather the necessary information on how to use it. In my case the missing piece of information was that pfPorts needs to built first before anything else. Building of pfPorts is not done automatically if you just fire up the build script as```
build.sh iso
You need an ultra-clean FreeBSD installation on the build host because the tools want to build everything its way and anything non-standard in terms of configuration trips it very easily.

Building pfSense will "contaminate" your build host with pfSense speficic modifications. This is something I absolutely don't want and I'm now moving to using a jail as the build host.

More to follow later.

Yes.. We maintain dedicated builders for this reason and more.

There is 10 years of history to deal with in changing things.

bhawk6901

I am trying to build on 8.3. when i run cd /usr/ports/textproc/expat2 && make depends install; i get error as shown in attchment. i have tried 3 different installations for i386 as well as amd64. Plz help on what im doing wrong

Capture.PNG_thumb

bmeeks

@bhawk6901:

I am trying to build on 8.3. when i run cd /usr/ports/textproc/expat2 && make depends install; i get error as shown in attchment. i have tried 3 different installations for i386 as well as amd64. Plz help on what im doing wrong

You have hit the problem with the FreeBSD 8.3 release not being compatible with the newer FreeBSD ports tree. Changing out the make utility as someone described in a previous post may help. You can also try this tip I was given and which worked for me:

Ports tree doesn’t support FreeBSD 8.3 anymore, you need to use the stable branch of ports tree called “2014Q2” instead of head. You can get it using:

svn co http://svn.freebsd.org/ports/branches/2014Q2 /usr/ports

This branch won’t have latest version of all ports, it only gets security updates, but the core files (/usr/ports/Mk/*) are still complaint with 8.3.

So to do the above on your builder, first delete the entire existing ports tree with –


rm -rf /usr/ports

– then run this command:


svn co http://svn.freebsd.org/ports/branches/2014Q2 /usr/ports

DO NOT perform a normal ports update in the future or you will break the builder again. My suggestion would be to abandon building FreeBSD 8.3-based pfSense and use 2.2 instead since it uses the current FreeBSD 10-STABLE.

Bill

bhawk6901

@bmeeks:

@bhawk6901:

I am trying to build on 8.3. when i run cd /usr/ports/textproc/expat2 && make depends install; i get error as shown in attchment. i have tried 3 different installations for i386 as well as amd64. Plz help on what im doing wrong

You have hit the problem with the FreeBSD 8.3 release not being compatible with the newer FreeBSD ports tree. Changing out the make utility as someone described in a previous post may help. You can also try this tip I was given and which worked for me:

Ports tree doesn’t support FreeBSD 8.3 anymore, you need to use the stable branch of ports tree called “2014Q2” instead of head. You can get it using:

svn co http://svn.freebsd.org/ports/branches/2014Q2 /usr/ports

This branch won’t have latest version of all ports, it only gets security updates, but the core files (/usr/ports/Mk/*) are still complaint with 8.3.

So to do the above on your builder, first delete the entire existing ports tree with –
rm -rf /usr/ports
– then run this command:
svn co http://svn.freebsd.org/ports/branches/2014Q2 /usr/ports
DO NOT perform a normal ports update in the future or you will break the builder again. My suggestion would be to abandon building FreeBSD 8.3-based pfSense and use 2.2 instead since it uses the current FreeBSD 10-STABLE.

Bill

Thanks for your reply. I shifted to freebsd10 before you replied. When i apply patches, it fails saying /usr/pfSensesrc/src does not exist.
Kindly guide me further

bmeeks

@bhawk6901:

Thanks for your reply. I shifted to freebsd10 before you replied. When i apply patches, it fails saying /usr/pfSensesrc/src does not exist.
Kindly guide me further

Well, it's been a long time since I set up my builder virtual machine, but I seem to remember having to manually create several directories along the way as I hit various bumps. As you have seen, the documentation is either missing and/or not updated in some cases. Try manually creating the directory /usr/pfSensesrc using:


mkdir -p /usr/pfSensesrc

Then try the apply patches step again. There may well be several directories you will need to manually create as the scripts seem to expect some to exist already, while others it will create if they are missing.

Bill

bhawk6901

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_thumb

Capture2.PNG_thumb

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?

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

heper

@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

bhawk6901

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_thumb
php55.txt
php55-pfSense-module.txt

bhawk6901

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

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

Capture.PNG_thumb

bmeeks

@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

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?