https://bugs.kde.org/show_bug.cgi?id=429103
--- Comment #14 from Mark Christensen <mark.christen...@primus.ca> --- (In reply to Cristofoto from comment #13) > I can't do it, there are still errors, > surely the method is not the right one, or the organization of folders and > files, I'm missing a real step by step and I don't have the necessary > knowledge, I think I'll leave the hand to someone who knows how to do it. > > Je n'y arrive pas, il y a encore des erreurs, > surement la méthode n'est pas la bonne, ou l'organisation des dossiers et > fichiers, il me manque un vrai pas à pas et je n'ai pas les connaissances > nécessaires, je pense laisser la main à quelqu'un qui sait faire. > > >> copy from terminal screen > >> > ******* > gawk has the following notes: > readline support has been removed from gawk. If you need to run gawk > interactively, install rlwrap: > > sudo port install rlwrap > > and run gawk using rlwrap: > > rlwrap gawk ... > grep has the following notes: > This port previously installed itself without a g* prefix, thus > overshadowing system binaries such as grep, fgrep, and egrep. The port is > now changed so that it does install with a g* prefix, like other GNU ports. > This means that you'll now find GNU grep at /opt/digikam/bin/ggrep. If you > dislike typing ggrep, you can create a shell alias or you can add > /opt/digikam/libexec/gnubin to your PATH, wherein non-g* prefixed symlinks > are installed. In other words, /opt/digikam/libexec/gnubin contains GNU > binaries without any prefix to the file names, so you can type grep and get > GNU grep just as before. > libidn has the following notes: > Please be aware that GNU libidn2 is the successor of GNU libidn. It comes > with IDNA 2008 > and TR46 implementations and also provides a compatibility layer for GNU > libidn. > libpsl has the following notes: > libpsl API documentation is provided by the port 'libpsl-docs'. > lzma has the following notes: > The LZMA SDK program is installed as "lzma_alone", to avoid conflict with > LZMA Utils > py38-pygments has the following notes: > To make the Python 3.8 version of Pygments the one that is run when you > execute the commands without a version suffix, e.g. 'pygmentize', run: > > port select --set pygments py38-pygments > python27 has the following notes: > To make this the default Python or Python 2 (i.e., the version run by the > 'python' or 'python2' commands), run one or both of: > > sudo port select --set python python27 > sudo port select --set python2 python27 > python38 has the following notes: > To make this the default Python or Python 3 (i.e., the version run by the > 'python' or 'python3' commands), run one or both of: > > sudo port select --set python python38 > sudo port select --set python3 python38 > FAILED COMMAND: port install ld64 +ld64_xcode subversion cmake libpng jpeg > tiff boost eigen3 gettext libusb libgphoto2 jasper lcms2 expat libxml2 > libxslt libical lensfun bison x265 ffmpeg qt5-qtbase qt5-qtdeclarative > qt5-qtmacextras qt5-qtquickcontrols qt5-qtxmlpatterns qt5-qtsvg qt5-qttools > qt5-qttranslations qt5-qtimageformats qt5-sqlite-plugin qt5-mysql-plugin > wget +ssl ImageMagick Since Cristofoto is unable to continue, I would like to try and help. I have a MacBook Pro 2019 with VMware Fusion so my first steps was to create a new VM running macOS Catalina 10.15.7 with the current Xcode and follow the steps in https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/macports/README to make sure I am able to get a running application, then I would create a VM running Big Sur and try the same steps to build the application. Since I am new to developing on mac/linux/windows I have run into some confusion and problems following the steps in the README under 10.15.7. I am currently stuck on a problem building qt5-qtwebengine in script 01-build-macports-sh it is saying "Exeception: No 11.0+ SDK found". My question now is should I open a new bug related to trying to recompile under 10.15.7? -- You are receiving this mail because: You are watching all bug changes.
