[SOLVED] interesting issue while building the base package (15.7.25)

[iosense]

I update my packages to the latest version ( 15.7.22 to 15.7.25 ) and I need to rebuild the base and the kernel package but I'm getting an error as follows, creating a base package:

Code Select Expand


===> usr.bin/tftp (depend)
===> usr.bin/time (depend)
===> usr.bin/tip (depend)
===> usr.bin/tip/tip (depend)
===> usr.bin/top (depend)
Making top.local.h from /vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.local.H
rm -f .depend
CC='cc ' mkdep -f .depend -a    -DHAVE_GETOPT -DHAVE_STRERROR -DORDER -I/vagrant/opnsense/src/usr.bin/top -I/vagrant/opnsense/src/usr.bin/top/../../contrib/top -I. -DNDEBUG -std=gnu99   /vagrant/opnsense/src/usr.bin/top/../../contrib/top/commands.c /vagrant/opnsense/src/usr.bin/top/../../contrib/top/display.c /vagrant/opnsense/src/usr.bin/top/machine.c /vagrant/opnsense/src/usr.bin/top/../../contrib/top/screen.c /vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.c /vagrant/opnsense/src/usr.bin/top/../../contrib/top/username.c /vagrant/opnsense/src/usr.bin/top/../../contrib/top/utils.c /vagrant/opnsense/src/usr.bin/top/../../contrib/top/version.c
In file included from /vagrant/opnsense/src/usr.bin/top/../../contrib/top/display.c:40:
/vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.local.h:66:5: error: invalid token at start of a preprocessor expression
#if RANDOM_PW == 0
    ^
/vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.local.h:65:19: note: expanded from macro 'RANDOM_PW'
#define RANDOM_PW       %random%
                        ^
1 error generated.
In file included from /vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.c:49:
/vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.local.h:66:5: error: invalid token at start of a preprocessor expression
#if RANDOM_PW == 0
    ^
/vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.local.h:65:19: note: expanded from macro 'RANDOM_PW'
#define RANDOM_PW       %random%
                        ^
/vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.c:183:5: error: invalid token at start of a preprocessor expression
#if Default_TOPN == Infinity
    ^
/vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.local.h:46:22: note: expanded from macro 'Default_TOPN'
#define Default_TOPN    %topn%
                        ^
/vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.c:457:5: error: invalid token at start of a preprocessor expression
#if Default_TOPN == Infinity
    ^
/vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.local.h:46:22: note: expanded from macro 'Default_TOPN'
#define Default_TOPN    %topn%
                        ^
/vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.c:550:5: error: invalid token at start of a preprocessor expression
#if Default_TOPN == Infinity
    ^
/vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.local.h:46:22: note: expanded from macro 'Default_TOPN'
#define Default_TOPN    %topn%
                        ^
4 errors generated.
In file included from /vagrant/opnsense/src/usr.bin/top/../../contrib/top/username.c:38:
/vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.local.h:66:5: error: invalid token at start of a preprocessor expression
#if RANDOM_PW == 0
    ^
/vagrant/opnsense/src/usr.bin/top/../../contrib/top/top.local.h:65:19: note: expanded from macro 'RANDOM_PW'
#define RANDOM_PW       %random%
                        ^
1 error generated.
mkdep: compile failed
*** [.depend] Error code 1

make[4]: stopped in /vagrant/opnsense/src/usr.bin/top
1 error

make[4]: stopped in /vagrant/opnsense/src/usr.bin/top
*** [depend_subdir_top] Error code 2

make[3]: stopped in /vagrant/opnsense/src/usr.bin
1 error

make[3]: stopped in /vagrant/opnsense/src/usr.bin
*** [usr.bin.depend__D] Error code 2

make[2]: stopped in /vagrant/opnsense/src
1 error

make[2]: stopped in /vagrant/opnsense/src
*** [_depend] Error code 2

make[1]: stopped in /vagrant/opnsense/src
1 error

make[1]: stopped in /vagrant/opnsense/src
*** [buildworld] Error code 2

make: stopped in /vagrant/opnsense/src
1 error

make: stopped in /vagrant/opnsense/src
*** Error code 2

Stop.
make: stopped in /vagrant/opnsense/tools


What could be missing?

[franco]

Did you update the tools.git as well?
Did you clean the source build dir and rebuilt from scratch?

# cd /usr/tools
# make clean-src

[packet loss]

So far I've seen a few users attempt to build OPNsense using vagrant with poor results. Usually spending too much time setting up a build environment. Seems to me that it would be much easier to just install FreeBSD 10.2 into a virtual machine.

[iosense]

Hi Franco,

Yes, All git repositories are updated according to the latest version. I cleaned everything and tried to rebuild. but no luck :(

I have no problem in v15.7.22, I do not understand why it happened.

Code Select Expand


| Folders | Commit     | Tags / Branches                 |
|---------|------------|---------------------------------|
| src/    | 3b29c333de | tag: 15.7.25 origin/stable/15.7 |
| ports/  | c4125f1109 | origin/master                   |
| tools/  | de44675921 | origin/master                   |


So far I've seen a few users attempt to build OPNsense using vagrant with poor results. Usually spending too much time setting up a build environment. Seems to me that it would be much easier to just install FreeBSD 10.2 into a virtual machine.

Hey azdps,

vagrant is actually doing a good job in this regard, In the beginning, I encountered little issues but now I guess I'm used to, it started to come easier to develop in this way.

[franco]

It looks like contrib/top/Configure does not run properly, why is beyond me. I don't see this in a normal system at all. It doesn't look related to the code updates as well. Was there any update to the host or vagrind or some other modification on top of our code that we're missing?

Can you check your full base build log for:

"Building top.local.h..." or "Configuration for top, version 3.5" or "This package is not complete." and see what happens after it?

[iosense]

I think you're right about that, the problem itself vagrant, anyway now I began to work on VirtualBox with FreeBSD 10.1 and I have successfully compiled the everything ( make everything )

but now I have a booting problem! Installation is completed with success but when I start the device again I get a screen that looks like the following and the device restarts after 10 seconds continuously... Do I need a custom setting for SSD's? Disk: Solid State Drive SATADOM-SH TYP (16.0GB)

Code Select Expand


F1 OPNsense
F6 PXE
Boot: F1



Disk and partitions info as follows:

Code Select Expand


# gpart show ada0
=>  63  31277169  ada0  MBR (15G)
    63  31277169     1  freebsd [active]  (15G)


[franco]

This is after install booting from a physical device? If so, what kind of device is this?

[iosense]

yes physical device, This device is a kind of network board with Intel Atom N2600 CPU. Also the OPNsense nano is running smoothly via USB, network board device meets the requirements. I think that the problems associated with Solid State Drive SATADOM-SH.

[franco]

Some ideas for BIOS: turning of UEFI boot and/or switch AHCI to IDE

[iosense]

There is no setting to turn UEFI boot off on BIOS, This is not a comprehensive bios.
I tried the SATA controller as IDE but it did not work out. After these setting did I need to install the system again?

Can I check what the the problems in recovery mode to mount the /dev/ada0 via USB?

[franco]

I don't think there's a problem with the drive or the installation. The next boot loader stage is not working for some reason. Do you have any bootloader modifications? Try to confirm that it boots fine on a normal desktop PC with the SSD attached to verify it's not the installation but the board/BIOS itself.

[iosense]

Hey Franco, thank you for your help.

No, I don't have any bootloader modifications and my OPNsense custom build iso working properly with VirtualBox.

I tried a few different systems to understand what the problem is on Network Board device and I installed the pfSense-memstick-2.2.6-RELEASE-i386 with SATA controller as AHCI and the same problem was also here, a system was starting again in 10 seconds.

So I've set the SATA controller as IDE and installed the pfSense again. Well I managed to boot, pfSense worked properly.

I tried the same thing for my OPNsense custom build but I could not install successfully :( Installation was stuck on 59%

Code Select Expand


/usr/local/bin/cpdup -vvv -I -o /usr/local /mnt/usr/local


screenshot: https://db.tt/NEzoA4WU

What should I do next?

[iosense]

OK, I think I found out what the problem is about.
the installation is not completed when I change the Keymap and Video Font settings during installation, but no problems with default settings.

see: https://db.tt/hgEyKWlM

[franco]

Sorry, mate, too much 16.1 release engineering going on at the moment. This is annoying for sure. I'll look at this, tracking via:

https://github.com/opnsense/ports/issues/18

[franco]

Hi Ali, I can't reproduce this on 16.1.8. I will close...