-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing iRedmail on FreeBSD 14 #260
Comments
Grab FreeBSD kernel source first, then install again. |
I'm sorry, but how do I do that? If a practical step is given, I would really love it. Thanks. |
Hello, I still got this error after figuring out how to grab the kernel source
|
I had exactly the same issue and decided to reinstall and select the system source tree "src" during the selection of which system components to install. The install script worked after that. |
I don't really understand. Could you assist me with the commands you used and in what directory |
In the iRedMail Installation Tutorial for FreeBSD there is a warning that "iRedMail is designed to be deployed on a FRESH server system, which means your server does NOT have mail related components installed". That being said, it was my fault to assume that a minimal installation of FreeBSD would do. On my first try I did not include the system source tree "src" during the selection which components to install (2.5.3 Selecting Components to Install: https://docs.freebsd.org/en/books/handbook/bsdinstall/#using-bsdinstall). However I completely reinstalled FreeBSD with the optional system component "System source tree" which includes the source code for FreeBSD and is required for the iRedMail installer to be able to build everything. Hope this makes it clearer. Good luck! |
Installing packages via ports tree didn't need FreeBSD source tree before, but not sure which package port requires |
I haven't been able to install the iRedMail server (1.7.1) to my FreeBSD system.
It always ends up giving me this error
at the tail end of the message.
I haven't been able to fix
The text was updated successfully, but these errors were encountered: