Installing nokogiri with --use-system-libraries
Rainer Müller
raimue at macports.org
Tue Apr 24 10:31:32 UTC 2018
On 2018-04-24 07:50, Mojca Miklavec wrote:
> On 23 April 2018 at 17:42, Rainer Müller wrote:
>>
>> Ruby and gems are really strange...
>>
>> Apparently, installing nokogiri with bundle fails
>
> Wasn't it you who said that we don't need a port for it as it's just a
> one-time conversion? :)
> (I'm honestly not sure who said that.)
Yes, that was me... :-)
I thought we could just edit unprocessed elements in in *.adoc, but as
I looked at them, some seemed really simple to be added to docbookrx in
order to avoid manual work.
> I have huge philosophical problems with this line:
> --use-system-libraries --with-xml2-dir=/opt/local
> --with-xml2-include=/opt/local/include/libxml2
> --with-xslt-dir=/opt/local --with-zlib-dir=/opt/local
> --with-exslt-dir=/opt/local
> because this will lead to broken software as soon as one updates some
> libraries under MacPorts. (Does HomeBrew ever delete old versions or
> do their old versions of libraries remain installed forever until the
> user removes them?)
It is just a shortcut to avoid pkg-config and tell it the paths
manually. I assume the result would be the same if pkg-config worked.
This is not that different from compiling software outside of MacPorts,
but linking to MacPorts libraries. This can break with updates to ports,
but it will work as long as the name of the .dylib does not change and
the ABI is compatible. If any of this changes, ports linking to the
library would also break.
> I did not use any of those workarounds this time for once (I didn't
> use external libraries).
Indeed, the external libraries caused the problems for me. That's what I
get for trying to save time by not compiling the libraries again...
Rainer
More information about the macports-dev
mailing list