Some important ports don't build on LBSD right out-of-the-box, due to them having oudated config.guess (in the case of autoconf, etc) or other issues related to the system having the name "LibertyBSD" rather than "OpenBSD."
Some important ports don't build on LBSD right out-of-the-box, due to them having oudated config.guess (in the case of autoconf, etc) or other issues related to the system having the name "LibertyBSD" rather than "OpenBSD."
due to them having oudated config.guess (in the case of autoconf, etc)
Hmm, is the OpenBSD community aware of this?
Would have thought they would try to remove outdated software
Just wanted to add a thanks to my comment. This is an awesome project. :)
> due to them having oudated config.guess (in the case of autoconf, etc)
Hmm, is the OpenBSD community aware of this?
Would have thought they would try to remove outdated software
_______________________
Just wanted to add a thanks to my comment. This is an awesome project. :)
This has been fixed, 100%. LibertyBSD uses “openbsd” as the system name for these purposes, though aesthetically it's still presented as “LibertyBSD” to the user.
This has been fixed, 100%. LibertyBSD uses “openbsd” as the system name for these purposes, though aesthetically it's still presented as “LibertyBSD” to the user.
Some important ports don't build on LBSD right out-of-the-box, due to them having oudated config.guess (in the case of autoconf, etc) or other issues related to the system having the name "LibertyBSD" rather than "OpenBSD."
Has there been any changes on this error since 2 months? If there's something I can test, let me know.
Hmm, is the OpenBSD community aware of this? Would have thought they would try to remove outdated software
Just wanted to add a thanks to my comment. This is an awesome project. :)
This has been fixed, 100%. LibertyBSD uses “openbsd” as the system name for these purposes, though aesthetically it's still presented as “LibertyBSD” to the user.