OK…I’ve seemingly overcome the Big Sur 11.1 crashes with p5.30-libapreq2 installation by installing MacPorts.
Unfortunately, to install p5.30-libapreq2 requires installing mod_perl2 variant +perl5_30. But building the latter fails! See: https://trac.macports.org/ticket/62169 <https://trac.macports.org/ticket/62169> (That sinking feeling from getting deeper and deeper toward an abyss!) > On 27 Jan2021, at 5:05 PM, Ryan Schmidt <ryandes...@macports.org> wrote: > > > On Jan 27, 2021, at 15:55, Murray Eisenberg wrote: >> >> Ahh…that helps greatly, thank you! >> >> I notice that most, or even all, of the commands given it the “2.2.3 Git >> install” directions at https://guide.macports.org/#installing.macports.git >> require that I use “sudo”, even though I’m on an admin account. For example, >> I had to do: >> >> sudo mkdir -p /iopt/mports >> >> and >> >> sudo ./configure —enable-readline >> sudo make >> >> whereas the only commands listed in those directions indicate the need for >> sudo only in “sudo make install”. >> >> Am I doing something wrong? > > On my system, /opt is a directory owned by root. Perhaps it is the same on > your system. As such, yes, you need sudo to be able to create a file or > directory inside it. > > You could set the ownership of the directory that you create to yourself so > that you can then perform further operations inside that directory as your > user without sudo. > > sudo mkdir /opt/mports > sudo chown yourusername /opt/mports > cd /opt/mports > ... > > You should not configure and make any software as root or with sudo. Use your > own user account. Only use sudo to make install. > > As the guide says, "For this example, /opt/mports will be used, but you can > put the source anywhere." For example, you could create a directory inside > your home directory, which would already be owned by you. --- Murray Eisenberg murrayeisenb...@gmail.com 503 King Farm Blvd #101 Rockville, MD 20850-6667 Mobile (413)-427-5334
