Re: [119589] trunk/dports/graphics
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 mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Snow Leopard buildbot out of disk space
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
Re: Snow Leopard buildbot out of disk space
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 ciserl...@macports.org wrote: 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
trac is currently having a problem: adding comments isn't possible
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, Marko [1] https://trac.macports.org/ticket/43539#trac-add-comment signature.asc Description: Message signed with OpenPGP using GPGMail ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac is currently having a problem: adding comments isn't possible
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 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, Marko [1] https://trac.macports.org/ticket/43539#trac-add-comment ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
trac is currently having a problem: adding comments isn't possible
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 ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac is currently having a problem: adding comments isn't possible
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 with my handle. Used Safari and Firefox and both gave and still give me this error! Greets, Marko ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac is currently having a problem: adding comments isn't possible
On 02 May 2014, at 21:12 , Clemens Lang c...@macports.org 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 using GPGMail ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac is currently having a problem: adding comments isn't possible
On 02 May 2014, at 21:12 , Clemens Lang c...@macports.org 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 some stage and then deleted it again, but obviously left some traces of it in there… I had to rewrite what I wanted to post initially and then the comment could be posted eventually. Thanks Shree and Clemens. Greets, Marko signature.asc Description: Message signed with OpenPGP using GPGMail ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
compiler.blacklist
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 bunch of Portfiles that use compiler blacklist, there
seem to be two approaches used about equally:
{clang 425} eg webkit-gtk, and
{clang 425.0.24} eg mpd
If I change my test to { clang 500 }, is it going to work right?
Thanks,
Craig
(Yes, I'm rather TCL-challenged. ;)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: compiler.blacklist
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
tries to build with clang and falls over.
That sounds like you may not have included the compiler_blacklist_versions 1.0
portgroup. If you do that, it should do what you say: blacklist all MacPorts
clangs, and Xcode clangs less than 500. So on Macs with Xcode 4 or earlier,
you'll be building with llvm-gcc-4.2 or gcc-4.2. Is that really what you want?
If Xcode 5's clang is ok, presumably MacPorts clang 3.5 would work too, maybe
even 3.4, and those would probably be preferable to the old llvm-gcc or gcc.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
