On Sat, Jul 28, 2012 at 12:06:33AM +0200, Daniel Ericsson wrote:
On 27 jul 2012, at 18:41, Jeremy Huddleston Sequoia wrote:
I'm curious if this is still happening. If anyone sees this issue when
initiating the install from XCode's preferences (*after* this email),
please let me know.
On Fri, Jul 27, 2012 at 9:42 PM, Jack Repenning j...@netgate.net wrote:
Sometimes, I notice I have some port installed that I have no conscious
interest in. I'm sure it's there because it's depended upon by some other
port that I do care about (or recursively), but is there some way I can
On Sat, Jul 28, 2012 at 01:19:22PM +0200, heapifyman wrote:
is there a way to turn off localization for a specific port? In my
case git output on the command line is in German but I would like to
have the original English output.
Why don't you just export LC_MESSAGES=en_US.UTF-8 or
Hi,
I run macports under Mountain Lion an had some errors.
pan2 runs now, but if I run port outdated it comes a large list
port outdated
The following installed ports are outdated:
attica 0.4.0_0 0.4.0_0 (platform darwin 11 != darwin
12)
audiofile
I run macports under Mountain Lion an had some errors.
pan2 runs now, but if I run port outdated it comes a large list
port outdated
The following installed ports are outdated:
attica 0.4.0_0 0.4.0_0 (platform darwin 11 !=
darwin 12)
audiofile
The usual way of communicating the desired locale, certainly for command-line
programs, is by setting appropriate environment variables. The lowest priority
(overridden by any of the others where they conflict) is LANG, which applies to
all categories of locale information not set with one of
On Sat, Jul 28, 2012 at 9:29 PM, Richard L. Hamilton rlha...@smart.netwrote:
The usual way of communicating the desired locale, certainly for
command-line programs, is by setting appropriate environment variables.
The lowest priority (overridden by any of the others where they conflict)
is
On 26/07/2012, at 12:40 PM, Ryan Schmidt wrote:
On Jul 25, 2012, at 19:37, Ian Wadham wrote:
I reported a problem with kdelibs4 @4.8.2_0 failing to detect compiler
characteristics
correctly, see https://trac.macports.org/ticket/34605?replyto=1#comment and
also
I think I have got to the bottom of the problem I have been having
when I tried to compile and build some of my own source code, but
linking to the kdelibs4 @4.8.2_0 library from Macports. See:
https://trac.macports.org/ticket/34605?replyto=1#comment
The question now is What is the best thing
On Jul 28, 2012, at 21:35, Ian Wadham iandw...@gmail.com wrote:
I think I have got to the bottom of the problem I have been having
when I tried to compile and build some of my own source code, but
linking to the kdelibs4 @4.8.2_0 library from Macports. See:
10 matches
Mail list logo
