On Nov 29, 2015, at 7:15 PM, Thomas Ruedas wrote:
> Am 30.11.15 um 02:09 schrieb David Evans:
>> The problem is not with poppler per se but with gawk which is being used in
>> the configure script. It's complaining that
>> library /opt/local/lib/libintl.8.dylib, provided by gettext is not built
Am 30.11.15 um 02:09 schrieb David Evans:
The problem is not with poppler per se but with gawk which is being used in the
configure script. It's complaining that
library /opt/local/lib/libintl.8.dylib, provided by gettext is not built for
the right architecture.
This seems to be an installatio
On 11/29/15 1:43 PM, Thomas Ruedas wrote:
> Hi,
> I have just installed Macports 2.3.4 from scratch on a new computer that runs
> OS X 10.10.5 and has Xcode 7.1.1 and am
> now recompiling packages, among them latex-extra. In the process, poppler
> fails to configure/build with the errors shown
>
Hi,
I have just installed Macports 2.3.4 from scratch on a new computer that
runs OS X 10.10.5 and has Xcode 7.1.1 and am now recompiling packages,
among them latex-extra. In the process, poppler fails to configure/build
with the errors shown below (I begin quoting from where it seems to go
wr
On Sun, Nov 29, 2015 at 12:56 PM, Rob Stevens wrote:
> But then how would I, say months down the road,
> would I then be able to determine what variant of
> perl5 I actually have installed on my system?
>
port installed perl5 and active
--
brandon s allbery kf8nh
Hello
I recently reported what I thought was a bug in macports,
but was in fact a misunderstanding on my part.
Here is my report (in green) and the response to it (in blue) (between
= marks)
=
*port install perl5 -perl5_16 +perl5_22* seems to work (per
