Hello Stu!
Thank you for your review. I will update the port and send it to
ports@ again later.
Please find my answers inline
Thomas
On 6/9/26 01:20, Stuart Henderson wrote:
On 2026/06/09 00:53, Thomas Dettbarn wrote:
+###############################################
+## WARNING: This build requires a lot of RAM ##
+## Please update /etc/login.conf and set ##
+## daemon:datasize=16384M ##
+###############################################
erk. don't suppose it's possible to track down which compilation uses
so much ram and see if a lower optimisation level for that file would
help?
Unfortunately, it is a python script which is eating RAM. :(
BUT...
port builds are normally done with class 'pbuild' which on amd64 has
default ":datasize-cur=12G:" ...
I just ran it again, this time with daemon:datasize=8192M, and it
compiled. So 12G might be okay... I just normally run my builds
as root, since I am lazy....
do you really need the version number in the prjpeppercorn dir?
apart from being a pain because you'll need to touch multiple ports
after an update, there will also be churn in the PLIST files, and
pkg_add will need to remove/reinstall files even if there was no
change to the contents.
The answer here is: Yes, the version number is important for the
build of nextpnr.
There is even a check inside the hungry hungry python script:
prjpeppercorn is less about the applications it installs (which are
also important for FPGA design), but more about the data it installs
along with it.
Which is required for the build of nextpnr, and needs to be in a
highly specific format.
So one port's update requires the other one to be updated as well.
In other words: If ports were a family, those two are married. (And in
a toxic relationship...)
