Re: compilers on Lion

> As Chris mentioned, ports use a compiler of their choosing, not of > yours. Yeah, it takes time to let this paradigm change sink in. :-) > In fact, it takes the unusual and not-recommended step of completely > discarding MacPorts base's list of preferred compilers and > substituting its own

Re: TeXLive distribution and macports

> If I understand what you are asking correctly, you are asking how to > setup a port that does nothing other than depend on other ports, so > installing it drags in all the dependencies, in one go? No, I want the opposite. For example, I want to create a replacement for `texlive-basic' that

TeXLive distribution and macports

My computer for daily use is an openSuSE GNU/Linux box; for TeX processing, however, I'm directly using tlmgr.[*] Regardless of this I don't have any dependency issues with `zypper', openSuSE's package manager, since I'm using the nifty `texlive-dummy-opensuse' package,

Re: TeXLive distribution and macports

>> Ah, I assumed too much knowledge, sorry. TeXLive itself comes with >> binaries for MacOS (both legacy platforms, i.e., 10.6-10.10, and >> recent versions, i.e., 10.10-10.13). By simply prepending the path >> to those binaries to PATH, the `texlive-*' ports from MacPorts >> would be

compilers on Lion

Folks, macports newbie here :-) I'm running a Lion box and I'm running macports from git, which works just fine. I've followed the advice on LibcxxOnOlderSystems and did cxx_stdlib libc++ buildfromsourcealways. Attached you can see the list of software that I've

Re: TeXLive distribution and macports

Hello Mojca! > Warmly welcome to another addictive distraction (aka. MacPorts :), So true... > it's nice to see you here as well. Thanks – it's time to meet again sometimes in the nearer future :-) >> Ports that are ok with using MacTeX instead will have declared >> their dependencies in

Re: compilers on Lion

>>> There _is_ indeed a way for gcc to build against libc++, as you >>> pointed out in a subsequent email, and one of our contributors >>> (Rene) went to the trouble of patching gcc to allow it to accept >>> the "-stdlib=libc++" flag to make this easy. But in the end, he >>> could not get any

Re: compilers on Lion

* Where can I get a concise and up-to-date description of portfiles? `portfiles.7' seems to be heavily out of date... >>> >>> What would you like to know? >> >> A list of all available variables/keywords, with a description. > > Yup, that's supposed to be what's in the guide and the

Re: compilers on Lion

> If you try to avoid the troubles of installing a zillion compilers > for the sake of installing poppler, what about switching to a super > lightweight pplib (currently available only inside LuaTeX sources)? > :) :) :) I'm already using Emacs, I won't become an apostate :-) > You can manually

extractpdfmark build failure on 10.6

Folks, please have a look at this build log https://build.macports.org/builders/ports-10.6_x86_64_legacy-builder/builds/83428 It fails with /usr/bin/ranlib: object: libextractpdfmark-poppler-core.a(libextractpdfmark_poppler_core_a-pagemode.o) malformed object (unknown load

Re: extractpdfmark build failure on 10.6

> something like this from another port earlier today should do, until > this issue finally gets fixed in the compiler run deps. > > Thanks! Werner

Re: extractpdfmark build failure on 10.6

>> something like this from another port earlier today should do, until >> this issue finally gets fixed in the compiler run deps. >> >> >

Re: `port install' from github tarball fails

>> I have to use `sync' anyway since I'm running MacPorts directly >> from the git repositories. > If you mean you've compiled a newer version of macports from the > macports-base git repository, then it's true that selfupdate won't > update it, though it won't do any harm either; it'll still

Re: `port install' from github tarball fails

> Don't be put off too much by this. It takes only about 10 minutes > to fix, if you care to. I use it on every machine < 10.9 routinely. > [...] Thanks, Mojca and Ken! Configuring with ./configure ac_cv_have_decl_rl_username_completion_function=yes \ --enable-readline \

Re: strange error code 71

>> Exit code: 71 >> Error: Failed to configure grep: configure failure: command >> execution failed > > [...] open a ticket and attach your full build log Done. https://trac.macports.org/ticket/57814 Werner

strange error code 71

[d3b59876b6dde9a4a26135a9c6b59320080eb23f] While doing sudo port -v install grep I get sandbox-exec: sh: No such file or directory Command failed: \ cd "/opt/local/var/macports/build/_opt_macports_macports-ports_sysutils_grep/grep/work/grep-3.3" \ ./configure

problem with reactivating ports

[macports running from git] Folks, I wanted to compile a project under MacPorts, and at the same time I wanted to protocol what MacPorts packages must be installed in advance before starting compilation. My glorious idea was to say port echo active > macports.active sudo port

Re: problem with reactivating ports

Hello Mojca, thanks for replying! >> port echo active > macports.active >> sudo port deactivate `cat macports.active` >> >> to deactivate all MacPorts packages. I tried with the `-y' flag in >> advance, just to be sure... > > I understand the first command, but a much better way for the

Re: problem with reactivating ports

Hello Ryan! > Do you need those old inactive versions? If not, you could > uninstall the inactive ports before beginning the exercise. Is there a safe command to uninstall all inactive ports in one rush? >> Irrespective of the problems I wonder whether it is a valid >> approach to deactivate

Re: git stash problem with `port sync'

> Mostly likely because the global settings are under your home area, > whilst the checkout below is not. [...] > MacPorts automatically switches to the user owning the top-level > ports tree directory to run the 'git pull'. [...] Thanks for the tips. It now works again. Werner

git stash problem with `port sync'

Folks, after doing various network hacks, calling `port -d sync' now fails. ---> Updating the ports tree Synchronizing local ports tree from file:///opt/macports/macports-ports DEBUG: /opt/local/bin/git pull --rebase --autostash DEBUG: system -W /opt/macports/macports-ports:

Re: libuv fails to build on 10.8.5

> I do appreciate your time and fully understand that this is not your > concern but would be still thankful if anyone could advice on how to > configure MacPorts to use the recent ssl. Try this for bootstrapping: https://try.gitea.io/donbright/lm Werner

mpkg package variants

Folks, I wonder how package variants are handled while creating `mpkg' bundles. As an example, consider the output of port rdeps lilypond-devel +mactex Looking at it you can see ... ossp-uuid perl5.26 ... and ... llvm-3.4 perl5 perl5.28 ... The created

Re: mpkg package variants

>> I wonder how package variants are handled while creating `mpkg' >> bundles. As an example, consider the output of >> >> port rdeps lilypond-devel +mactex >> >> Looking at it you can see >> >> ... >> ossp-uuid >> perl5.26 >> ... >> >> and >> >> ... >> llvm-3.4 >> perl5 >>

Re: problem with perl's `PAR' module

>> Perl lib version (5.26.3) doesn't match executable >> 'perl' version (5.26.1) at >> /opt/local/lib/perl5/5.26/darwin-thread-multi-2level/Config.pm line 62. >> Compilation failed in require at >> /opt/local/lib/perl5/site_perl/5.26/PAR.pm line 7. >> >> > It could be a Perl port

problem with perl's `PAR' module

Folks, I've installed perl's `PAR` module, needed for TeXLive's (self-compiled) `biber` binary, with sudo cpan-5.26 install PAR on my up-to-date Lion box (using MacPorts from git). However, executing `biber --help` fails with Perl lib version (5.26.3) doesn't match executable

package version and variant info in `main.log`

I've noticed that in `main.log` files there is no information what version and variants have been requested – for example, ImageMagick @6.9.9-40_7+x11 Wouldn't it make sense to make `port` add this information to the very top of `main.log`? This would also help identify various `make.log`

libunwind-headers issue

On Mac Lion, installing a fresh MacPorts from scratch, then calling port -N mpkg lilypond-devel +mactex +perl5_28 +python37 always causes a (harmless) abort. The reason is that `libunwind-headers' gets installed as part of the dependencies rather early, but one of the very last steps is

Re: package version and variant info in `main.log`

>> I've noticed that in `main.log` files there is no information what >> version and variants have been requested – for example, >> >> ImageMagick @6.9.9-40_7+x11 >> >> Wouldn't it make sense to make `port` add this information to the >> very top of `main.log`? This would also help identify

Re: package version and variant info in `main.log`

I've noticed that in `main.log` files there is no information what version and variants have been requested – for example, ImageMagick @6.9.9-40_7+x11 Wouldn't it make sense to make `port` add this information to the very top of `main.log`? This would also

Re: problem with perl's `PAR' module

Ryan, thanks for your help. > If you really want to use perl 5.26, then verify that [...] All of this is exactly as you describe. Since the `biber' program from TeXLive 2018 works I suspect a problem with the new binary from TeXLive 2019, which I will report upstream. Werner

Re: linking problems

> Probably the problem is that you have specified CXX=clang-mp-9.0 -- > that's a C compiler. You want the C++ compiler here: > CXX=clang++-mp-9.0 Doh. That's it. I was blind. Fortunately I did first ask here before investing hours into delving this non-issue. Thanks a lot! Werner

linking problems

On my Mac Lion box running an up-to-date MacPorts, for experimentation reasons I try to build the current git version of lilypond directly from the repository – this is, I use the MacPorts infrastructure for compilation with a recent clang version, but without any adaptations of lilypond's source

Re: dmgbuild ports disappeared

> I looked for "dmgbuild" in all mailing list, tracker and github > commit messages and found only: What about https://pypi.org/project/dmgbuild/ Doesn't it work to install with pip (or pip2/pip3)? Werner

Re: mpkg package variants

>> Let me reformulate my question: Does the way how I have installed >> MacPorts packages on my computer influence how `port mpkg' works >> for a given package? Given that `port mpkg' rebuilds all packages, >> I would expect no. Instead, I would expect some control file (or a >> special

Re: mpkg package variants

>>> I believe you can just specify the variants that you want (for the >>> port and all of its dependencies) at the command line when you run >>> `port mpkg`, can't you? As in: >>> >>> sudo port mpkg lilypond-devel +mactex +perl5_28 >> >> This seems to work, thanks! Maybe it's worth to

Re: 'LANG=' produces German output

[CCing Bruno Haible] >> on my Lion box, calling >> >> LANG= bison ... >> >> I suddenly get *German* output! Ditto for other programs like >> 'info', 'ggrep', etc., that come with '.po' files. Is this normal? >> Is this a new gettext feature? > > I would suppose that without a valid locale

Re: 'LANG=' produces German output

on my Lion box, calling LANG= bison ... I suddenly get *German* output! [...] >> >> It's seems to be a new feature of gettext 0.21, which comes with >> improved MacOS support. In the NEWS file I read > > Then you should not be seeing this problem with MacPorts since

Re: 'LANG=' produces German output

Hello Bruno, thanks for your detailed answer. >> I'm not sure whether I like this feature. At least on the command >> line, I consider it surprising. > > There is the opposite expectation: "I have set that I want the > programs to talk to me in German. Why do I need to specify it a >

'LANG=' produces German output

[macports-ports 83eb0fba14b88745b29c0efa5d29aa73ee69c04b from 2020-02-12] Folks, on my Lion box, calling LANG= bison ... I suddenly get *German* output! Ditto for other programs like 'info', 'ggrep', etc., that come with '.po' files. Is this normal? Is this a new gettext feature?

after `sync -d`, installed versions are too new

Folks, I'm running MacPorts directly from the git repository, using macOS 10.7.5. Today, I've done my usual incantation git fetch upstream && git merge upstream/master && git push port -d sync Calling port outdated gives the expected output: The following installed ports are

Re: after `sync -d`, installed versions are too new

>> sudo port -pb install outdated > > -p is discouraged and harmful. OK. > We used to get numerous reports from users that expected > > sudo port install bison @3.7.4_0 > > to install bison 3.7.4, when in fact "install" ignores the version > specifier (except in cases where you already

license for stuff in `macports-www`

Looking at https://github.com/macports/macports-www/ I can't find a license statement that applies to the stuff in the repository. So: What license is it under? I suggest to add a small `README.md` file that mention it... Werner

'doctor' script

Folks, is there a 'doctor' script that walks over all installed MacPorts ports and checks whether its dependencies are installed, too? In general, what's the right action(s) to thoroughly check the integrity of a MacPorts installation? I have forcibly uninstalled some ports by accident, and

Re: 'doctor' script

>> is there a 'doctor' script that walks over all installed MacPorts >> ports and checks whether its dependencies are installed, too? In >> general, what's the right action(s) to thoroughly check the >> integrity of a MacPorts installation? >> >> I have forcibly uninstalled some ports by

Re: 'doctor' script

>> So: Is there a command (or a simple shell invocation) to walk over >> all packages to check whether all dependencies are fulfilled? I >> suppose that `sudo port upgrade outdated` doesn't do this for >> efficiency. > > Upgrading a port will first install any missing dependencies, so 'sudo >

ccache problem

[macports-base 5d637741b5ae04b63f7e99a9057c6764d29fd7fd (Mar 10 2022)] [macports-ports b6d340c43cdb2bef077f72edb075a124148832ed (Apr 1 2022)] I'm trying to install `lilypond-devel` on my macOS 10.7.5 box; due to using variants this must be compiled. Previously, this always worked, however, I

Re: ccache problem

>> It seems to be a problem with the 'ccache' package/port on MacOS >> 10.7.5. After updating to current git (and running `port sync`), >> `port upgrade outdated` just tried to compile emacs 28.1, and >> exactly the same problem happened. > > It looks like /run/user//ccache-tmp is indeed a

Re: ccache problem

>> ``` >> ccache /opt/local/bin/clang-mp-13 ... conftest.c >&5 >> ccache: error: Failed to create temporary file for >> /run/user/507/ccache-tmp/tmp.cpp_stdout.RTVNqj: Operation not permitted >> ``` >> >> What's the reason that `port` tries to use >> `/run/user/507/ccache-tmp/` (uid 507 =

compiling emacs-devel on Mac OS X Lion fails

The 'emacs-devel' package of MacPorts is currently based on commit 4650ea9c25514831d925e5006ea0c3679344333b (from 2022-Jul-12). On Mac OS X 10.7.5 (Lion), emacs 27.2 builds fine. However, the above commit fails with ``` ./temacs --batch -l loadup --temacs=pbootstrap \ --bin-dest

Re: compiling emacs-devel on Mac OS X Lion fails

>> The 'emacs-devel' package of MacPorts is currently based on commit >> 4650ea9c25514831d925e5006ea0c3679344333b (from 2022-Jul-12). >> >> On Mac OS X 10.7.5 (Lion), emacs 27.2 builds fine. However, the above >> commit fails with >> >> ``` >> ./temacs --batch -l loadup --temacs=pbootstrap \ >>

missing pre-compiled packages

Folks, I wonder why some pre-compiled packages are missing: * ccache – the directory `https://packages.macports.org/ccache/` is empty * git – the directory `https://packages.macports.org/git/` doesn't exist at all If this is expected, where is it documented? Werner

Re: missing pre-compiled packages

>> I wonder why some pre-compiled packages are missing: [...] If this >> is expected, where is it documented? > > Yes, it's expected that not all ports will have binaries available. > See . Thanks. > The automated license checking doesn't have

list of packages that are always compiled

Folks, is there an option to `port` that shows me the names of all packages that must be built from source, and which are not available pre-compiled from 'packages.macports.org'? Or maybe this list is somewhere else, ideally also giving a reason? [My use-case is 'ghostscript', for which I

Re: what is the MacPorts equivalent of homebrew pinning; freezing an installed version?

>> what is the MacPorts equivalent of homebrew pinning; freezing an >> installed version? > > There is none. > > Just don't upgrade. You might do sudo port upgrade outdated and not lilypond to update everything buth LilyPond. Werner

Re: list of packages that are always compiled

Sorry for the late reply; only yesterday I had access again to my Mac. >> is there an option to `port` that shows me the names of all packages >> that must be built from source, and which are not available >> pre-compiled from 'packages.macports.org'? [...] > > List which ports do and don't

Re: what is the meaning of a note that looks like a rhombus in a contrabass quartet arrangement?

> what is the meaning of a note that looks like a rhombus in a > contrabass quartet arrangement? I don't know how many people are both on the MacPorts and the LilyPond mailing list (you sent this e-mail to the wrong one :-), so I'm going to answer that: These notes are 'flageolet tones', also

pre-build packages for Lion

What are the intervals that pre-build packages for Lion are generated? For example, `libpaper` is already available, but `ghostscript` is not, and neither is 'texlive-bin'... And while we are at it, 'ports.macports.org' reports that 'lilypond' can't be build on Lion due to ``` Dependency

Re: pre-build packages for Lion

>> What are the intervals that pre-build packages for Lion are >> generated? For example, `libpaper` is already available, but >> `ghostscript` is not > > There will not be any prebuilt archives available for ghostscript > for any macOS version where one of its dependents, e.g. libpaper, is >

Ghostscript upgrade will break LilyPond

Just a heads-up for all LilyPond users: Updating Ghostscript to the most recent version (10.02.1) in MacPorts will break LilyPond.[*] If possible, please wait until newer LilyPond versions (2.24.3 and 2.25.10) are available in MacPorts, which should happen soon. If everything fails you might

Re: Lilypond documentation (info+man) installation?

> I'd say build it with +docs, but that failed for me: > > :info:build Making Documentation/out/lilypond-contributor.info < texi > :info:build bibtex: Not writing to >

Guile 3

Recent LilyPond development versions only compile with Guile 3. It would be great if https://github.com/macports/macports-ports/pull/14600 can be eventually finished and added to MacPorts. Werner