On May 2, 2014, at 20:20, Craig Treleaven wrote:
>
> For my mythtv-core.xx ports, I want to blacklist clang prior to XCode 5, so I
> added:
>
> compiler.blacklist-append { clang <= 500.2.79 } \
>macports-clang*
>
> That doesn't work when I build on Lion with XCode 4.3.3 (clang 318.0.61)--it
Hi:
For my mythtv-core.xx ports, I want to blacklist clang prior to XCode
5, so I added:
compiler.blacklist-append { clang <= 500.2.79 } \
macports-clang*
That doesn't work when I build on Lion with XCode 4.3.3 (clang
318.0.61)--it tries to build with clang and falls over.
Looking at a
On 02 May 2014, at 21:12 , Clemens Lang wrote:
> Maybe it depends on the comment content?
I couldn’t figure it out where it was, but it must have been some invisible
character which wasn’t really deleted.
The only idea how it might have happened is that I had tried to input a “TM"
symbol at s
On 02 May 2014, at 21:12 , Clemens Lang wrote:
> Maybe it depends on the comment content? Did you try adding a comment with
> a different text?
Ha, thanks, why didn’t I think of that now…
It worked.
So, I have to rewrite my message and see.
signature.asc
Description: Message signed with OpenPGP
Is anyone else having a similar problem ?
Marko
I know this sounds basic but can you try flushing the cache, cookies etc?
Shree
Sent from my iPhone
> On May 2, 2014, at 12:01 PM, mk-macpo...@techno.ms wrote:
>
> Hmmm, you could add a comment? I see you could...
>
> Well, yes, I was logged on
Hmmm, you could add a comment? I see you could...
Well, yes, I was logged on with my handle. Used Safari and Firefox and both
gave and still give me this error!
Greets,
Marko
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
ma
Marko
I just added a comment to the ticket. Are you logged in as m...@macports.org?
Shree
On May 2, 2014, at 11:36 AM, mk-macpo...@techno.ms wrote:
> Hi Shree,
>
> when I tried to add a comment to a ticket [1] I just got the response “Trac
> Error” from MacPorts trac.
>
> Since this happene
Hi Shree,
when I tried to add a comment to a ticket [1] I just got the response “Trac
Error” from MacPorts trac.
Since this happened a couple of times within the last 2 hrs or so I guess
something is wrong on the server side, because switching to another web client
didn’t help either.
Greets,
I think I'll just increase the disk size. I'll do it a little later today will
need a reboot.
Shree
Sent from my iPhone
> On May 2, 2014, at 6:06 AM, Christoph Iserlohn wrote:
>
> See
> https://build.macports.org/builders/buildports-snowleopard-x86_64/builds/26132/steps/compile/logs/stdio
>
See
https://build.macports.org/builders/buildports-snowleopard-x86_64/builds/26132/steps/compile/logs/stdio
--
Christoph
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Hi Frank,
thanks for pointing that out. I wasn’t aware of the stub!
I’ve reopened the ticket and am awaiting input from the portfile author.
Thanks again,
Marko
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
macports-dev ma
11 matches
Mail list logo