> Where did you get this quote (URL)? I need a source, thanks.
Direct conversation with Ben Pfaff.
Prior to discovering libpixman.
smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
On Jul 26, 2011, at 8:39 PM, Joshua Root wrote:
> On 2011-7-27 13:35 , Jeremy Huddleston wrote:
>>
>> On Jul 26, 2011, at 5:57 PM, Ryan Schmidt wrote:
>>
>>>
>>> On Jul 26, 2011, at 19:44, Jeremy Huddleston wrote:
>>>
I will continue to maintain the option for anyone to install Apple's
Where did you get this quote (URL)? I need a source, thanks.
>
>From PSPP devs:
We suspect that it must not be a problem with the Quartz or X rendering,
whichever Cairo uses on Mac, because otherwise GTK+ programs wouldn't
work. Probably, fewer programs use Cairo to render to PDF, which is where
On 2011-7-27 13:35 , Jeremy Huddleston wrote:
>
> On Jul 26, 2011, at 5:57 PM, Ryan Schmidt wrote:
>
>>
>> On Jul 26, 2011, at 19:44, Jeremy Huddleston wrote:
>>
>>> I will continue to maintain the option for anyone to install Apple's
>>> gcc-4.2 via the apple-gcc-4.2 port for as long as it is r
On Jul 26, 2011, at 5:57 PM, Ryan Schmidt wrote:
>
> On Jul 26, 2011, at 19:44, Jeremy Huddleston wrote:
>
>> I will continue to maintain the option for anyone to install Apple's gcc-4.2
>> via the apple-gcc-4.2 port for as long as it is required. Thankfully there
>> don't seem to be too man
On Jul 26, 2011, at 19:44, Jeremy Huddleston wrote:
> I will continue to maintain the option for anyone to install Apple's gcc-4.2
> via the apple-gcc-4.2 port for as long as it is required. Thankfully there
> don't seem to be too many ports that require it.
libpixman now, apparently. Any inp
On Jul 26, 2011, at 2:36 PM, Jeremy Lavergne wrote:
>> Remind me, what is the purpose for the "if {![file executable
>> ${configure.cc}]}" block? On what systems would /usr/bin/gcc-4.2 not exist?
>> I'm only coming up with Tiger, but nobody would request llvm-gcc-4.2 or
>> clang on Tiger eithe
On Jul 26, 2011, at 2:36 PM, Jeremy Lavergne wrote:
>> Remind me, what is the purpose for the "if {![file executable
>> ${configure.cc}]}" block? On what systems would /usr/bin/gcc-4.2 not exist?
>> I'm only coming up with Tiger, but nobody would request llvm-gcc-4.2 or
>> clang on Tiger eithe
> Remind me, what is the purpose for the "if {![file executable
> ${configure.cc}]}" block? On what systems would /usr/bin/gcc-4.2 not exist?
> I'm only coming up with Tiger, but nobody would request llvm-gcc-4.2 or clang
> on Tiger either.
Is gcc 4.2 now an optional install?
smime.p7s
Descr
On Jul 20, 2011, at 11:26, Jeremy Huddleston wrote:
> If both clang and llvm-gcc-4.2 fail to build, you can try falling back on
> gcc-4.2. If gcc-4.2 works, you can fall back on it, but we recommend you try
> to fix the problem. A common reason for both llvm-gcc and clang failing
> where gcc
On 24 Ιουλ 2011, at 11:32 μ.μ., Ryan Schmidt wrote:
>
> On Jul 24, 2011, at 13:22, Panayotis Katsaloulis wrote:
>
>> On 20 Ιουλ 2011, at 7:26 μ.μ., Jeremy Huddleston wrote:
>>
>>> wine and libsdl are the only two ports that I've run into that need to fall
>>> back on gcc-4.2
>>
>> I tried to
On Jul 24, 2011, at 13:22, Panayotis Katsaloulis wrote:
> On 20 Ιουλ 2011, at 7:26 μ.μ., Jeremy Huddleston wrote:
>
>> wine and libsdl are the only two ports that I've run into that need to fall
>> back on gcc-4.2
>
> I tried to install wine with 2.0.0 and Lion, and it failed, probably for the
On Jul 24, 2011, at 13:34, Jack Howarth wrote:
> On Sun, Jul 24, 2011 at 09:22:16PM +0300, Panayotis Katsaloulis wrote:
>>
>> On 20 Ιουλ 2011, at 7:26 μ.μ., Jeremy Huddleston wrote:
>>
>>> wine and libsdl are the only two ports that I've run into that need to fall
>>> back on gcc-4.2
>>
>> I
On Sun, Jul 24, 2011 at 09:22:16PM +0300, Panayotis Katsaloulis wrote:
>
> On 20 Ιουλ 2011, at 7:26 μ.μ., Jeremy Huddleston wrote:
>
> > wine and libsdl are the only two ports that I've run into that need to fall
> > back on gcc-4.2
>
> I tried to install wine with 2.0.0 and Lion, and it failed
On 20 Ιουλ 2011, at 7:26 μ.μ., Jeremy Huddleston wrote:
> wine and libsdl are the only two ports that I've run into that need to fall
> back on gcc-4.2
I tried to install wine with 2.0.0 and Lion, and it failed, probably for the
reason you are mentioning here.
Is there any trick I should do to
Yes, that is what I was eventually going to do, but it requires a lot of
synchronous changes and revbumps. If you have the time to do that, it's
certainly a good solution.
--Jeremy
On Jul 20, 2011, at 12:43, Peter O'Gorman wrote:
> On 07/20/2011 11:26 AM, Jeremy Huddleston wrote:
>
>> 6) lib
The problem is resolution at link time.
-L/opt/local/lib caues /opt/local/lib/libnotify.dylib to be used to satisfy
/usr/lib/libSystem.B.dylib's dependency of /usr/lib/system/libnotify.dylib
The -L options on the command line are the link-time equivalent of
DYLD_LIBRARY_PATH at runtime.
On Jul
On 2011-07-20 18:26 , Jeremy Huddleston wrote:
> 6) libnotify
>
> The libnotify port is disabled on Lion. This blocks gnome,
> firefox-x11, and other ports. There is a hacky workaround discussed
> in the Portfile, but it is recommended for *experts only* ... I
> really can't stress that enough.
On 07/20/2011 11:26 AM, Jeremy Huddleston wrote:
6) libnotify
The libnotify port is disabled on Lion. This blocks gnome,
firefox-x11, and other ports. There is a hacky workaround discussed
in the Portfile, but it is recommended for *experts only* ... I
really can't stress that enough.
Hi,
On Wed, Jul 20, 2011 at 09:26:46AM -0700, Jeremy Huddleston wrote:
>
> 4) compiler codegen issues
>
> As discussed on this list over the past month or so, we've run into some
> codegen issues when using llvm-gcc-4.2. This will appear as a segfault,
> timeout, bad visual artifacts, or just plai
On Jul 20, 2011, at 10:24 AM, Jeremy Lavergne wrote:
>> Clang is LLVM. You probably mean "llvm-gcc" rather than "llvm"?
>
> Yup, llvm-gcc is what I meant, not clang.
>
> Is it correct to say?
> * llvm-gcc is llvm 2
> * clang is llvm 3
There are too many differnet versions floating around for
> Clang is LLVM. You probably mean "llvm-gcc" rather than "llvm"?
Yup, llvm-gcc is what I meant, not clang.
Is it correct to say?
* llvm-gcc is llvm 2
* clang is llvm 3
> Do you know if it is specifically cairo or pango that has the issue (or
> both)? I'd suggest just having cairo and pango
On Jul 20, 2011, at 10:12 AM, Jeremy Lavergne wrote:
> With regards to the upcoming use of LLVM: has anyone had issues with any
> programs that use Cairo to print, which would involve output to PDF or PS?
> I don't think it's a match with the ticket already open [1].
>
> PSPP is having issues wh
With regards to the upcoming use of LLVM: has anyone had issues with any
programs that use Cairo to print, which would involve output to PDF or PS?
I don't think it's a match with the ticket already open [1].
PSPP is having issues whenever pango/cairo are built with LLVM 2: the
problem goes away w
MacPorts on Lion works fairly well out of the box with a few exceptions. I've
fixed a number of build issues already, so I'd like to share the common cases
for other developers to benefit from:
1) Reinventing functionality added to Libc
Lion's Libc pulled in some new functionality from POSIX 20
25 matches
Mail list logo
