- On 24 Feb, 2015, at 13:40, Ryan Schmidt ryandes...@macports.org wrote:
Are you able to build gettext universal with trace mode? I have a bug report
that this doesn't work:
https://trac.macports.org/ticket/46898#comment:1
Yes. It works fine for me.
--
Clemens Lang
On Feb 23, 2015, at 4:52 PM, Clemens Lang wrote:
I am only aware of two ports that do not build in trace mode
due to functional changes or problems that are caused by trace mode, and those
are:
- go, because the OS X loader uses malloc() when DYLD_INSERT_LIBRARIES is set
and that breaks a
On 24.02.2015 01:40 PM, Ryan Schmidt wrote:
On Feb 23, 2015, at 4:52 PM, Clemens Lang wrote:
I am only aware of two ports that do not build in trace mode
due to functional changes or problems that are caused by trace mode, and
those
are:
- go, because the OS X loader uses malloc() when
On Monday February 23 2015 05:22:50 Mihai Moldovan wrote:
Please don't do this. Tracemode will shadow any files from packages not
explicitly listed as a dependency. Builds in tracemode will thus
fail/not recognize harfbuzz at all, even if it installed.
How can it do that without deactivating
On Mon, Feb 23, 2015 at 9:18 AM, René J.V. rjvber...@gmail.com wrote:
How can it do that without deactivating everything that's not somehow a
dependency (and thus making it impossible to do anything while an install
is being done), or by duplicating potentially a huge portion of the entire
On Monday February 23 2015 09:19:35 Brandon Allbery wrote:
How can it do that without deactivating everything that's not somehow a
dependency (and thus making it impossible to do anything while an install
is being done), or by duplicating potentially a huge portion of the entire
MacPorts
On Feb 23, 2015, at 10:18 AM, René J.V. Bertin rjvber...@gmail.com wrote:
On Monday February 23 2015 09:19:35 Brandon Allbery wrote:
How can it do that without deactivating everything that's not somehow a
dependency (and thus making it impossible to do anything while an install
is being
On Feb 23, 2015, at 10:18 AM, René J.V. Bertin rjvber...@gmail.com wrote:
Ugh. Just make it optional (as in can be turned off), ok? ...
I don't see us ever making trace mode mandatory, but we would eventually like
to make it the default mode of operation. And if a port fails to build under
- On 23 Feb, 2015, at 23:34, René J.V. Bertin rjvber...@gmail.com wrote:
It intercepts all (file open and similar) system calls and then checks against
the installed files database, possibly for each and every header file included
(which often means the same header file multiple times),
On Monday February 23 2015 11:00:43 Lawrence Velázquez wrote:
I don't see us ever making trace mode mandatory, but we would eventually like
to make it the default mode of operation. And if a port fails to build under
trace mode, we consider that a bug in the port.
Sure. As I said, I'd probably
On Mon, February 23, 2015 16:50, René J.V. Bertin wrote:
Sure. As I said, I'd probably appreciate for certain things, but not as a
mandatory feature.
I have a hunch that it'd add non-negligible overhead too, if it's to be
used in as many stages as possible.
As someone routinely using trace
On Monday February 23 2015 16:51:15 Jeremy Lavergne wrote:
As someone routinely using trace mode across 10.5 to 10.10, I've run into
no significant impacts. I greatly appreciate all it provides, and all
It intercepts all (file open and similar) system calls and then checks against
the
On 21.02.2015 12:34 AM, René J.V. Bertin wrote:
It should however be possible to remove the dependency on harfbuzz, and let
the configure script figure out whether it's there (or, if that doesn't work,
do a `file exists libharfbuzz` to determine whether the support can be
activated).
On Feb 20, 2015, at 2:23 AM, Lawrence Velázquez lar...@macports.org wrote:
On Feb 20, 2015, at 1:46 AM, René J.V. Bertin rjvber...@gmail.com wrote:
Is there any support in MacPorts for circular dependencies (as far as such a
thing is possible)?
No. A port’s dependency graph must be acyclic
On Friday February 20 2015 09:31:28 Daniel J. Luke wrote:
if possible/reasonable, a good solution here is to break the port in question
up into two ports (one which installs the 'boostrap' version and one which
installs the extra pieces that the variant would have installed).
Sadly that
On Feb 20, 2015, at 5:34 PM, René J.V. Bertin wrote:
On Friday February 20 2015 09:31:28 Daniel J. Luke wrote:
if possible/reasonable, a good solution here is to break the port in
question up into two ports (one which installs the 'boostrap' version and
one which installs the extra
On Feb 20, 2015, at 1:46 AM, René J.V. Bertin rjvber...@gmail.com wrote:
Is there any support in MacPorts for circular dependencies (as far as such a
thing is possible)?
No. A port’s dependency graph must be acyclic.
I'm building the freetype +infinality version with harfbuzz support
Hello,
Is there any support in MacPorts for circular dependencies (as far as such a
thing is possible)?
I'm building the freetype +infinality version with harfbuzz support, which
depends on cairo, which ultimately depends on freetype. Would that make it
impossible to install that port variant
18 matches
Mail list logo
