Just mount /usr/ports with wxallowed.
--
Sent from a phone, apologies for poor formatting.
On 29 January 2022 19:52:17 [email protected] wrote:
Hello, hacker Omar.
If space is a concern, you can just move the pobj directory (by setting
WRKOBJDIR in mk.conf.) For ports like 0ad you still need to have the
partition that holds WRKOBJDIR mounted with wxallowed.
Soo what do you think about /usr/local ? It has wxallowed :/
I think I tried something similar.. or not.. I have poor memory.
Best Regards,
Omar Polo
Thank you for your time,
fossy
anyway, without the actual output is difficult to see what it went
wrong. clean everything, try to fix the permissions (`make
fix-permissions') and attach the build log
I understand. I did read about the fix-permissions in the man page, but
didn't understand where it goes.. probably my fault for not reading 100%
of it.. thank you, I will try that tomorrow.
[email protected] writes:
Okay, so.. I am new to this, but I did read a few man pages.
Everything seems to install well until the build process - it says that
I
cannot run it as root because it would mess up permissions (which is
good
to stop there), but then I cannot even run it as a normal user because
the
directory ports/pobj/locks is owned by root:wheel..
The package in-question is 0ad, which also seems to brake because it
cannot set a few things, on the 7.0 GENERIC.MP#232 amd64 release(?) OS.
I compiled another package just fine..
And this was when the ports directory was on /usr/ports, and with the
above (0AD) port, I got a new ports tree, to the /usr/local/ports
because
I have more storage space on that partition, and also because it has the
"wxallowed" flag for whatever reason it was needed.
0ad needs wxallowed because of its bundled copy of spidermonkey which
needs it :/
not directly linked to your problem, but I'd suggest against moving
PORTSDIR. There are some scripts in infrastructure/bin (portcheck IIRC)
that doesn't handle a custom PORTSDIR (I may be wrong).
If space is a concern, you can just move the pobj directory (by setting
WRKOBJDIR in mk.conf.) For ports like 0ad you still need to have the
partition that holds WRKOBJDIR mounted with wxallowed.
anyway, without the actual output is difficult to see what it went
wrong. clean everything, try to fix the permissions (`make
fix-permissions') and attach the build log
/etc/mk.conf :
PORTSDIR=/usr/local/ports
DISTDIR=/usr/distfiles
PACKAGE_REPOSITORY=/usr/packages
Have a nice day, I hope I helped, even if it's a bit.
Best Regards,
Omar Polo
