Package list inconsistency for make dvd on raspberry pi 4 #290
Comments
|
Second error: only the “arm” image works on ARM, “dvd” doesn’t work. As for build errors in FreeBSD ports: it’s just the way it is sometimes. Something is fixed later, something else is broken. |
|
PS: we could set power dns to ignore on aarch64, about geb I’m not sure. It should be useful, but was updated to a new version lately which likely causes this so rather wait this one out? |
|
@fichtner what would the command look like to create an arm image and what would the image be? A raw image I can copy onto a thumb drive/emmc? |
I have not looked into modifying the image yet, but this may be a possibillity, on the other hand, as you can see from my cross compile efforts: a lot more packages seem to be affected. I would like to try to compile the arm image you mentioned next and see how it goes. |
|
It’s in the docs really: „make arm“, DEVICE or ARCH may be required. |
|
I will try it, thanks. |
|
It looks a lot better now, when I use "make arm", this time I get stuck with a command not found error 127, when the arm.sh (https://github.com/opnsense/tools/blob/master/build/arm.sh) script is run. If I understand it right, the command "arm_install_uboot" which is mentioned in line 103 cannot be found. I checked whether there is a freebsd package containing the term uboot, but nothing turned up with "pkg search uboot". The whole error looks like this: Should I open a new ticket for this? |
|
Do you have DEVICE set? If yes set UEFI= (empty value) |
|
It rather looks like DEVICE is not set, which also means source build is busted anyway. |
|
Forget about UEFI note, misinterpreted the code. It’s definitely DEVICE missing. |
|
I made sure, that DEVICE was used and the same error occurs: https://pastebin.com/cPBtvwBR |
|
If you build rpi why not use the RPI(2) config? ARM64 doesn't have arm_install_uboot indeed |
|
RPI2 seems to be the right one (if freebsd support is up for it now in FreeBSD 13) |
|
I added the missing function in 184d300 -- from the technical side this bug can be closed? |
|
I reinstalled freebsd and created a fresh setup with git clone, but it looks like there is a different error now. |
|
No, this line is executed before the line you reported earlier. 🤔 |
Should I create a new ticket for this? |
|
If you know what the issue is supposed to be? Cheers, |
|
I set it all up again and did some tests: |
|
@JohannesNeu ah you are right... likely because arm was added much later than other image types, see |
|
@fichtner I did some more testing and compiled "make dvd" and "make arm" and I get the same error now: make dvd: make arm: I assume the last change fixed the problems "make arm" had and now it is only left with the same problems "make dvd" had anyway :-) icinga2 seems to be another packet that has problems being built on arm and could be blacklisted to get at least one step further? There may be more packages that will show up bit by bit though. |
|
Well, of course it's both problematic for "dvd" and "arm" since the "ports" stage is aborting here which is needed for any build. I disabled icinga, but again for gdb and postfix35 I'm not sure. You can throw both out locally to progress, but postfix also has a plugin that needs to be removed from plugins.conf then... |
|
Can I built a single package in debug mode to find out what is going wrong? Something like "make ports icinga2"? |
|
Sure but to reiterate all of this is documented... any argument given is treated as a package name to be removed and restarts the build which then fails for individual ports rather than doing a batch build. |
|
For reference.... https://github.com/opnsense/tools#advanced-package-builds |
|
I created a bug ticket at Freebsd, the built process mentions devel/gdb so I assume that not only icinga2 may be affected by this, but some of the other ports as well. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264095 |
|
Thanks for reporting upstream. However, I think that we can't do much more here? Can we close this issue and wait and see? I'll be syncing upstream fixes each day for ports tree anyway. |
|
We can close it. If anything new arises, I will open a new ticket. The problem seems to be upstream and it takes time to fix the problem for each package, maybe some blacklisted ports can be removed from the blacklist in the future. |
Hi,
after my last try (#285) I set the whole system up again and ran the compilation another time. The results were different.
I started screen and ran the following command: "make dvd DEVICE=ARM64 | & tee compile.log"
A full log is available, but 161MB big, which is why I will not attach it yet, but can provide it if necessary.
uname -a gives the following output:
and the packages installed have the following versions:
I am seeing this error and do not know how to fix it:
I tried to cross compile in a VM and receive a similar error (https://pastebin.com/1UNK0vzg), but would like to concentrate on the one I see with the raspberry pi.
The only reference I could find so far is this bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235346 but it is from some time ago and states that the issue should have been fixed.
When I try to compile without the "DEVICE=ARM64" I get the following error: https://pastebin.com/7XJBuSRm
I am a little bit stuck here and do not know how to proceed.
Any ideas?
The text was updated successfully, but these errors were encountered: