I'm currently writing a portfile for re-alpine. I have cctools installed, so
re-alpine's configure script picks up cctools' nm and ar, and its build process
calls cctools' ar and ranlib.
Is it advisable in this case to declare a build dependency (probably a
bin-style one) on cctools? I
That's not necessary unless you absolutely need *our* version of cctools.
On Feb 8, 2013, at 1:47 AM, Lawrence Velázquez lar...@macports.org wrote:
I'm currently writing a portfile for re-alpine. I have cctools installed, so
re-alpine's configure script picks up cctools' nm and ar, and its
On Feb 8, 2013, at 03:47, Lawrence Velázquez wrote:
I'm currently writing a portfile for re-alpine. I have cctools installed, so
re-alpine's configure script picks up cctools' nm and ar, and its build
process calls cctools' ar and ranlib.
Is it advisable in this case to declare a build
ar and ranlib and the like are utilities most ports use to compile, and
they're expected to be provided by Xcode's command line tools, so we don't
declare dependencies on them, just like we don't declare dependencies on gcc,
sed, awk, grep, gawk, etc. cctools happens to provide (newer
Hi,
On Fri, Feb 08, 2013 at 03:11:26PM -0800, m...@macports.org wrote:
Revision: 102821
https://trac.macports.org/changeset/102821
Author: m...@macports.org
Date: 2013-02-08 15:11:26 -0800 (Fri, 08 Feb 2013)
Log Message:
---
openssl: version 1.0.1d
just a quick
On Sat, Feb 09, 2013 at 01:48:53AM +0100, Clemens Lang wrote:
just a quick warning that the update of openssl to 1.0.1d breaks
MacPorts OpenSSH in the sense that connecting to other machines using
the ssh client is no longer possible. Rebuilding openssh does not fix
this. I haven't had any
I'd like to upgrade the icu port to version 50. This changes the library
version number so I'll need to revbump everything linking with it. Any tips on
how to identify what ports those are? I know I can find ports declaring a
dependency on icu with:
port file all | sort -u | xargs grep :icu
