Hi,
Me and Aljaž would be willing to host the MacPorts meeting in 2017 again.
If you have any particular requests about the desired time / place /
or anything else, we can discuss it before we fix the dates, but we
should probably fix it some time soon.
In addition to the face-to-face meeting,
> On Oct 9, 2016, at 7:23 PM, Ryan Schmidt wrote:
>
> I've been with MacPorts for around 10 years and have thought of
> rewriting the documentation for several years so I feel I might be
> able to do it.
+1
> I'm just not doing it right this second because I'm busy
> On Oct 9, 2016, at 15:23, Rainer Müller wrote:
>
> Hello Marcel,
>
>> On 2016-10-09 15:53, Marcel Bischoff wrote:
>> As Ryan has identified that the online documentation needs work, I'm
>> hereby volunteering to give it a go. Since there appear to be quite
>> specific
On Sun, Oct 9, 2016 at 6:02 PM, Jack Howarth
wrote:
> On Sun, Oct 9, 2016 at 5:57 PM, Jack Howarth
> wrote:
>> On Sun, Oct 9, 2016 at 4:46 PM, Jack Howarth
>> wrote:
>>> On Sun, Oct 9, 2016 at 3:20 PM,
On Sun, Oct 9, 2016 at 5:57 PM, Jack Howarth
wrote:
> On Sun, Oct 9, 2016 at 4:46 PM, Jack Howarth
> wrote:
>> On Sun, Oct 9, 2016 at 3:20 PM, Jeremy Huddleston Sequoia
>> wrote:
>>>
On Oct 9, 2016, at 09:47,
On Sun, Oct 9, 2016 at 4:46 PM, Jack Howarth
wrote:
> On Sun, Oct 9, 2016 at 3:20 PM, Jeremy Huddleston Sequoia
> wrote:
>>
>>> On Oct 9, 2016, at 09:47, Jack Howarth
>>> wrote:
>>>
>>> On Sun, Oct 9, 2016 at
Hi,
On Fri, Oct 07, 2016 at 09:13:11AM -0500, Ryan Schmidt wrote:
> Regarding updating pandoc, see https://trac.macports.org/ticket/48324
> Regarding updating ghc, see https://trac.macports.org/ticket/48899
> Regarding old llvm on Sierra, see https://trac.macports.org/ticket/52424
As a follow-up
On Sat, Oct 08, 2016 at 04:10:34PM +0200, Mojca Miklavec wrote:
> >> The command "otool -L cfg" reports
> >>@rpath/libMiKTeX209-core.1.dylib
> >
> > That looks correct, but really depends on what "cfg"'s rpath is.
>
> "cfg" is a binary. I'm not sure whether it gets installed, but it
> does,
On Sun, Oct 9, 2016 at 4:46 PM, Jack Howarth
wrote:
> On Sun, Oct 9, 2016 at 3:20 PM, Jeremy Huddleston Sequoia
> wrote:
>>
>>> On Oct 9, 2016, at 09:47, Jack Howarth
>>> wrote:
>>>
>>> On Sun, Oct 9, 2016 at
On Sun, Oct 9, 2016 at 3:20 PM, Jeremy Huddleston Sequoia
wrote:
>
>> On Oct 9, 2016, at 09:47, Jack Howarth wrote:
>>
>> On Sun, Oct 9, 2016 at 3:53 AM, Jeremy Huddleston Sequoia
>> wrote:
>>> thread_local support was added
Hello Marcel,
On 2016-10-09 15:53, Marcel Bischoff wrote:
> As Ryan has identified that the online documentation needs work, I'm
> hereby volunteering to give it a go. Since there appear to be quite
> specific views on how everthing here needs to be, I'm asking in advance:
>
> - Is that in
> On Oct 9, 2016, at 09:47, Jack Howarth wrote:
>
> On Sun, Oct 9, 2016 at 3:53 AM, Jeremy Huddleston Sequoia
> wrote:
>> thread_local support was added in OS X 10.9 (along with __cxa_thread_atexit
>> being added to Libc as part of that
On Sun, Oct 9, 2016 at 3:53 AM, Jeremy Huddleston Sequoia
wrote:
> thread_local support was added in OS X 10.9 (along with __cxa_thread_atexit
> being added to Libc as part of that support). As long as your minimum
> deployment target is 10.9, you should be fine. The issue
On 16/10/09, Ken Cunningham wrote:
On 2016-10-09, at 6:53 AM, Marcel Bischoff wrote:
there appear to be quite specific views on how everthing here needs to be
This is true, and it doesn't take long to notice -- but over 20,000 ports hang
tight together and almost all of them work all the
On 2016-10-09, at 6:53 AM, Marcel Bischoff wrote:
> there appear to be quite specific views on how everthing here needs to be
This is true, and it doesn't take long to notice -- but over 20,000 ports hang
tight together and almost all of them work all the way back to Tiger. And that
is no
Hi all.
As Ryan has identified that the online documentation needs work, I'm
hereby volunteering to give it a go. Since there appear to be quite
specific views on how everthing here needs to be, I'm asking in advance:
- Is that in everyone's interest?
- Is there already someone working on it?
On Sunday October 09 2016 01:04:39 Jeremy Huddleston Sequoia wrote:
>That being said, it's technically possible and they should be binary
>compatible.
Oh, and what about using DYLD_LIBRARY_PRELOAD? Not for systematic use, but
shouldn't it be useful for testing purposes, or for debugging for
On Sunday October 09 2016 01:04:39 Jeremy Huddleston Sequoia wrote:
>My advice is to not mess with the base OS. There is a very good reason why I
>force the user to use a variant and don't even give instructions on how to use
>darwinup to install the libcxxabi and libcxx tarballs.
>
>That
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi David,
thanks for the help.
On 09.10.16 07:50 David Evans wrote:
> I've confirmed that gcr's dependency on gnupg is unnecessary --
> works fine without it. Removed in r153722. Let me know if you
> have any further problems upgrading gimp2.
I
> On Oct 7, 2016, at 08:59, René J.V. Bertin wrote:
>
> On Friday October 07 2016 11:43:48 Lawrence Velázquez wrote:
>
> [was Re: dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of
> using libstdc++]
>
>> it might be useful to refine this mechanism to allow
thread_local support was added in OS X 10.9 (along with __cxa_thread_atexit
being added to Libc as part of that support). As long as your minimum
deployment target is 10.9, you should be fine. The issue is that you're on
10.6, so you don't have __cxa_thread_atexit.
There is active
On 2016-10-08, at 10:03 PM, Stephen J. Butler wrote:
> FYI, it's in the Xcode 8 release notes:
>
> https://developer.apple.com/library/content/releasenotes/DeveloperTools/RN-Xcode/Introduction.html
>
> I did a quick test file and it seems to compile with Apple clang. No clue on
>
22 matches
Mail list logo