> On Sep 3, 2016, at 12:52 AM, Ken Cunningham
> wrote:
>
> now I need to figure out how to customize the "make" to "make XYZ".
Use "build.target XYZ".
> PortSystem 1.0
> PortGroup github 1.0
> PortGroup active_variants 1.1
>
> Sounds like a jit variant which sets supported_archs may be in order then.
> That way users on x86_64 systems can decide whether they want to lose the JIT
> or rebuild all the dependencies with +universal.
>
> - Josh
Hey! I feel a little better about my lack of knowledge now -- I think I mi
On 2016-9-3 06:11 , Ken Cunningham wrote:
This is ludicrous. GCC 4.0 is a decade old.
Oh, way better news.
BasiliskII builds and runs, including the JIT, with clang-3.7 at least,
when it's held to i386 arch.
Apparently nobody has been able to do that before, assuming Dr. Google
is correct
> On Sep 2, 2016, at 2:41 PM, René J.V. Bertin wrote:
>
> On Friday September 02 2016 13:45:56 Lawrence Velázquez wrote:
>
>>> Or is it something that will in fact mostly/only benefit Linux users?
>>
>> Yes. This is meant to keep Clang compatible with ABI changes to GCC 5.1's
>> libstdc++.
>
>
>
> This is ludicrous. GCC 4.0 is a decade old.
>
Oh, way better news.
BasiliskII builds and runs, including the JIT, with clang-3.7 at least, when
it's held to i386 arch.
Apparently nobody has been able to do that before, assuming Dr. Google is
correct.
Built with arch x86_64 it runs
On Friday September 02 2016 19:51:07 Christopher Jones wrote:
> > That's about time ... GCC 6.1 is out …
>
> you are behind the times. gcc 6.2 is the current pro version…
Oh, quite likely - I'm running Ubuntu, hardly a pro distribution :))
R.
___
macp
>
> "supported_archs i386"
>
thanks. I couldn't seem to find that one anywhere, but now I see it's in a
different section of the portfile reference than I thought it would be.
> This is ludicrous. GCC 4.0 is a decade old.
I know. The JIT assembly uses some gcc-4.0 specific register assignment
> On 2 Sep 2016, at 7:41 pm, René J.V. Bertin wrote:
>
> On Friday September 02 2016 13:45:56 Lawrence Velázquez wrote:
>
>>> Or is it something that will in fact mostly/only benefit Linux users?
>>
>> Yes. This is meant to keep Clang compatible with ABI changes to GCC 5.1's
>> libstdc++.
>
On Sep 2, 2016, at 12:00, Lawrence Velázquez wrote:
>> Indeed I have the new portfile working to the latest github commits, BUT
>> because of the current BasiliskII JIT compiler internals, it requires
>> gcc-4.0 only
>
> This is ludicrous. GCC 4.0 is a decade old.
>
>> (I'm hoping that appl
On Friday September 02 2016 13:45:56 Lawrence Velázquez wrote:
>> Or is it something that will in fact mostly/only benefit Linux users?
>
>Yes. This is meant to keep Clang compatible with ABI changes to GCC 5.1's
>libstdc++.
That's about time ... GCC 6.1 is out ...
>P.S. Incidentally, this impl
> On Sep 2, 2016, at 1:25 PM, René J.V. Bertin wrote:
>
> Just caught this in the llvm-3.9 release message: "new libstdc++ ABI
> compatibility".
>
> I guess we'll be seeing port:llvm-3.9 provide 3.9.0 in a near future, but
> what does that ABI remark mean for us on OS X? Will it again be easie
On Fri, Sep 2, 2016 at 1:25 PM, René J.V. Bertin
wrote:
> I guess we'll be seeing port:llvm-3.9 provide 3.9.0 in a near future, but
> what does that ABI remark mean for us on OS X? Will it again be easier to
> build C++ code using GCC? Or will it be easier for older OS X versions to
> migrate to
Hi,
Just caught this in the llvm-3.9 release message: "new libstdc++ ABI
compatibility".
I guess we'll be seeing port:llvm-3.9 provide 3.9.0 in a near future, but what
does that ABI remark mean for us on OS X? Will it again be easier to build C++
code using GCC? Or will it be easier for older
> On Sep 2, 2016, at 12:42 PM, Ken Cunningham
> wrote:
>
> Short version:
>
> I have a port that builds correctly only with arch=i386. x86_64 builds fail.
> I can get this to build with "sudo port install basiliskII build_arch=i386"
> but I can't seem to find the command to specify that the por
Short version:
I have a port that builds correctly only with arch=i386. x86_64 builds fail.
I can get this to build with "sudo port install basiliskII build_arch=i386"
but I can't seem to find the command to specify that the portfile.
Is there a way?
Long version:
I'm working on updating the B
> On Sep 1, 2016, at 7:08 AM, michae...@macports.org wrote:
>
> Revision
> 152220
> Author
> michae...@macports.org
> Date
> 2016-09-01 05:08:28 -0700 (Thu, 01 Sep 2016)
> Log Message
>
> libuv:
> + add me as comaintainer, but still openmaintainer;
> + move to using github portgroup;
> + bump re
On Friday September 02 2016 14:19:02 Rainer Müller wrote:
>> https://trac.macports.org/ticket/45251
>
>That would equivalent to what gdb recommends for codesigning.
Yes, minus the part related to taskgated. And plus a few extra steps that
probably serve to add the certificate to the trust store.
On 2016-08-31 23:25, Lawrence Velázquez wrote:
>> On Aug 31, 2016, at 4:57 PM, René J.V. Bertin wrote:
>>
>> I noticed that Apple don't ship an lldb-mi executable (at least they don't
>> for OS X 10.9).
>
> Xcode 7.3 includes it (`xcrun --run lldb-mi`) but Xcode 4.6.3 does not.
> Someone else
On Sep 2, 2016, at 5:43 AM, Marius Schamschula wrote:
>
>>> On Sep 1, 2016, at 4:43 PM, m...@macports.org wrote:
>>>
>>> +platform darwin 9 {
>>> +depends_build port:flex
>>> +}
>>
>> Doesn't libpcap require flex to build on all operating systems, not just
>> Leopard?
>
> Ryan,
>
> On Sep 1, 2016, at 4:43 PM, m...@macports.org wrote:
>
> Revision
> 152245
> Author
> m...@macports.org
> Date
> 2016-09-01 14:43:27 -0700 (Thu, 01 Sep 2016)
> Log Message
>
> libpcap: require MacPorts flex to build under Leopard.
> Modified Paths
>
> • trunk/dports/net/libpcap/Portfile
20 matches
Mail list logo
