On 24 March 2018 at 02:57, Ryan Schmidt wrote:
> On Mar 23, 2018, at 05:35, Mojca Miklavec wrote:
>
>> I'm compiling some command-line tools and I tried to aim supporting
>> 10.6 (asking 10.6 users to grab libc++ from somewhere if they are
>> desperate enough to want to use the binaries).
>>
>> I c
On 24 March 2018 at 01:51, Ryan Schmidt wrote:
> On Mar 23, 2018, at 15:47, Mojca Miklavec wrote:
>
>> +PortGroup compiler_blacklist_versions 1.0
>
> The below doesn't blacklist compilers by version; it only blacklists them by
> name, so this portgroup isn't needed.
Thanks. It always co
On Mar 23, 2018, at 05:35, Mojca Miklavec wrote:
> I'm compiling some command-line tools and I tried to aim supporting
> 10.6 (asking 10.6 users to grab libc++ from somewhere if they are
> desperate enough to want to use the binaries).
>
> I compiled against libc++ provided by MacPorts and asked
On Mar 23, 2018, at 15:10, Mojca Miklavec wrote:
> In the absence of any PortGroup implementing the build system, this
> should make sure that autotools-based ports would properly build out
> of source without changing anything else.
I didn't think that autotools in general supported out-of-sour
On Mar 23, 2018, at 14:42, Kenneth F. Cunningham wrote:
> On 2018-03-23, at 12:02 PM, Mojca Miklavec wrote:
>>
>> I still like the convention of marking ports as "requires C++11" much
>> more than "please blacklist gcc 3.0 and gcc 4.2".
>
> It's elegant, but also opens endless issues about C11
On Mar 23, 2018, at 15:47, Mojca Miklavec wrote:
> Mojca Miklavec (mojca) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/e3bfbbf91a558abf777b45926ab79f1dde88b811
>
> The following commit(s) were added to refs/heads/maste
On 23 March 2018 at 19:26, Rainer Müller wrote:
> On 2018-03-23 17:52, Mojca Miklavec wrote:
>> I would like to propose introducing some "build-out-of-source"
>> variable that would work for any build system (CMake, meson,
>> configure, ...).
> For cmake, you run in the build directory, specifying
On 2018-03-23, at 12:02 PM, Mojca Miklavec wrote:
>
> I still like the convention of marking ports as "requires C++11" much
> more than "please blacklist gcc 3.0 and gcc 4.2".
>
It's elegant, but also opens endless issues about C11 or C14 or C17 or c++17
and brings much confusion, IMHO.
On In
Please join us in welcoming the following new MacPorts project member:
- Enrico Maria Crisostomo (emcrisostomo)
We look forward to continued excellent contributions from these new team
members.
- Joshua, Rainer, and Ryan
Do you want to join the MacPorts team? If you would like to be
considere
On 2018-03-23 19:26, Rainer Müller wrote:
> For meson, you run in the source directory, specifying the path to the
> build directory.
>
> build.dir${workpath}/build
> configure.cmdmeson
> configure.post_args ${configure.dir} ${build.dir}
Wait, I misunderstood meson here
On 2018-03-23 17:52, Mojca Miklavec wrote:
> I would like to propose introducing some "build-out-of-source"
> variable that would work for any build system (CMake, meson,
> configure, ...).
For cmake, you run in the build directory, specifying the path to the
source directory.
configure.dir
On 23 March 2018 at 15:59, Kenneth F. Cunningham wrote:
> On 2018-03-23, at 1:44 AM, Mojca Miklavec wrote:
>>
>> Additional question for Ken: if we do (b) and keep using gcc6(?), do
>> we then even need any special (buildbot) setup for C++11 builds like
>> we plan to do for libc++-based builders?
>
I would like to propose introducing some "build-out-of-source"
variable that would work for any build system (CMake, meson,
configure, ...).
At the moment we do this semi-optionally for CMake, by default for
meson and don't explicitely support it for other build systems at all
(there might be exce
On 2018-03-23, at 1:44 AM, Mojca Miklavec wrote:
>
> Additional question for Ken: if we do (b) and keep using gcc6(?), do
> we then even need any special (buildbot) setup for C++11 builds like
> we plan to do for libc++-based builders?
Once the 10.6 to 10.8 buildbots are configured for libc++ an
Hi,
- On 23 Mar, 2018, at 15:50, Abhishek Kashyap abhishek.kasya...@gmail.com
wrote:
> Can I use Itcl script for using object oriented features reqiured for this
> project.
Rainer already replied to this question:
https://lists.macports.org/pipermail/macports-dev/2018-March/037823.html
Can I use Itcl script for using object oriented features reqiured for this
project.
> On 23 Mar 2018, at 15:27, Rainer Müller wrote:
>
> On 2018-03-23 11:06, Mojca Miklavec wrote:
>> For the moment by far the easiest thing to do would be to use
>>system "chmod +r ${worksrcpath}/wherever-the-file-is"
>> probably in post-extract phase.
>
> In pure Tcl:
> file attributes ${
On 2018-03-23 11:06, Mojca Miklavec wrote:
> For the moment by far the easiest thing to do would be to use
> system "chmod +r ${worksrcpath}/wherever-the-file-is"
> probably in post-extract phase.
In pure Tcl:
file attributes ${worksrcpath}/wherever-the-file-is -permissions a+r
Rainer
> On 23 Mar 2018, at 11:37, Mojca Miklavec wrote:
>
> On 23 March 2018 at 11:35, Enrico Maria Crisostomo wrote:
>> On 23 Mar 2018, at 11:06, Mojca Miklavec wrote:
>>>
>>> I would say this in an upstream issue that should be reported and
>>> fixed. (That said, we could probably also have some c
On 23 March 2018 at 11:35, Enrico Maria Crisostomo wrote:
> On 23 Mar 2018, at 11:06, Mojca Miklavec wrote:
>>
>> I would say this in an upstream issue that should be reported and
>> fixed. (That said, we could probably also have some code to
>> automatically fix these kind of problems after extrac
Hi,
I'm compiling some command-line tools and I tried to aim supporting
10.6 (asking 10.6 users to grab libc++ from somewhere if they are
desperate enough to want to use the binaries).
I compiled against libc++ provided by MacPorts and asked a user to
test that binary on 10.7 (I would need to ins
On 23 Mar 2018, at 11:06, Mojca Miklavec wrote:
>
> On 23 March 2018 at 10:28, Enrico Maria Crisostomo
> wrote:
>> Hi all,
>>
>> I'm working on fixing a `py-tensorflow` port issue
>> (https://trac.macports.org/ticket/55972) and I've found the following
>> problem when building `py-protobuf3`:
Hi,
I just stumbled upon this app (I haven't tested it yet) which might be
able to avoid some pain when editing git history before pushing your
changes upstream:
http://gitup.co
Mojca
On 23 March 2018 at 10:28, Enrico Maria Crisostomo
wrote:
> Hi all,
>
> I'm working on fixing a `py-tensorflow` port issue
> (https://trac.macports.org/ticket/55972) and I've found the following problem
> when building `py-protobuf3`:
>
> ---> Building py36-protobuf3
> Error: Failed to
Hi all,
I'm working on fixing a `py-tensorflow` port issue
(https://trac.macports.org/ticket/55972) and I've found the following problem
when building `py-protobuf3`:
---> Building py36-protobuf3
Error: Failed to build py36-protobuf3: command execution failed
The log shows the followi
Dear Ryan,
I have no idea how to solve the issue with existing-possibly-broken
binaries (the problem with 10.5/PPC is that lots and lots of binaries
do not even build, so worrying about the few
built-but-new-to-be-broken binaries is not worrying me too much in
comparison). I admit it's a problem a
26 matches
Mail list logo
