Hi,
I tried to port upgrade outdated subversion.
For some reason it wanted to compile serf1 instead of
installing a precompiled package.
configure of serf1 failed because /opt/local/bin/apr-1-config
tells serf1's configure that the C preprocessor is 'gcc-4.2 -E'
gcc-4.2 is not available on my
On Oct 15, 2012, at 03:42, Titus von Boxberg wrote:
I tried to port upgrade outdated subversion.
For some reason it wanted to compile serf1 instead of
installing a precompiled package.
configure of serf1 failed because /opt/local/bin/apr-1-config
tells serf1's configure that the C
On 10/15/2012 02:36 AM, Ryan Schmidt wrote:
On Oct 15, 2012, at 03:42, Titus von Boxberg wrote:
I tried to port upgrade outdated subversion.
For some reason it wanted to compile serf1 instead of
installing a precompiled package.
configure of serf1 failed because /opt/local/bin/apr-1-config
On Oct 15, 2012, at 06:45, Blair Zajac wrote:
On 10/15/2012 02:36 AM, Ryan Schmidt wrote:
http://lists.macosforge.org/pipermail/macports-dev/2012-October/020636.html
In this case, the package with the compiler baked in is apr.
To work around the problem, you could rebuild apr on your
Am 15.10.2012 13:47, schrieb Ryan Schmidt:
On Oct 15, 2012, at 06:45, Blair Zajac wrote:
On 10/15/2012 02:36 AM, Ryan Schmidt wrote:
http://lists.macosforge.org/pipermail/macports-dev/2012-October/020636.html
In this case, the package with the compiler baked in is apr.
To work around the
On Oct 15, 2012, at 07:16, Titus von Boxberg wrote:
Am 15.10.2012 13:47, schrieb Ryan Schmidt:
I agree generally with what jmr wrote earlier: any port not respecting the
value of configure.compiler should be made to do so. That will solve the
problem.
Would that solve the apr issue?
On 2012-10-15 23:16 , Titus von Boxberg wrote:
Am 15.10.2012 13:47, schrieb Ryan Schmidt:
I agree generally with what jmr wrote earlier: any port not respecting
the value of configure.compiler should be made to do so. That will
solve the problem.
Would that solve the apr issue?
I thought
On 2012-10-15 23:36 , Joshua Root wrote:
On 2012-10-15 23:16 , Titus von Boxberg wrote:
When I run port -v configure apr on my machine it says
checking how to run the C preprocessor... /usr/bin/clang -E
So apr does seem to respect the value of configure.compiler?
It's not apr but serf1
On Oct 15, 2012, at 5:34 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Oct 15, 2012, at 07:16, Titus von Boxberg wrote:
Am 15.10.2012 13:47, schrieb Ryan Schmidt:
I agree generally with what jmr wrote earlier: any port not respecting the
value of configure.compiler should be made to
On Oct 15, 2012, at 08:21, Blair Zajac wrote:
On Oct 15, 2012, at 5:34 AM, Ryan Schmidt wrote:
apr does respect configure.compiler, but it bakes the discovered value into
its apr-config script, which other programs, like serf1, then later use to
determine the compiler. So it is serf1 and
On Oct 15, 2012, at 9:56 AM, Joshua Root j...@macports.org wrote:
On 2012-10-16 00:27 , Ryan Schmidt wrote:
I just don't understand for what purpose apr installs a program that offers
information about what compiler was used. It's not apr's business to do
that. Or I would say no other
On Oct 15, 2012, at 09:09, Daniel J. Luke wrote:
Have we decided on which approach we want to take for this (in what I think
is decreasing order of likelihood)?
- We can change the compiler on activate, but that still can break if the
user upgrades xcode at some point while it's
On Oct 15, 2012, at 6:27 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Oct 15, 2012, at 08:21, Blair Zajac wrote:
On Oct 15, 2012, at 5:34 AM, Ryan Schmidt wrote:
apr does respect configure.compiler, but it bakes the discovered value into
its apr-config script, which other programs,
On Oct 15, 2012, at 10:16 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Oct 15, 2012, at 09:09, Daniel J. Luke wrote:
Have we decided on which approach we want to take for this (in what I think
is decreasing order of likelihood)?
- We can change the compiler on activate, but that
14 matches
Mail list logo
