On Dec 27, 2016, at 13:15, Michael Dickens wrote:
> Mark Evenson (easye) pushed a commit to branch boost_update
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/b06095e1e52e6766a130e174786e023b9feeed04
>
> commit b06095e1e52e6766a130e174786e023b9feeed04
>
>
>
> The issue in doing that is that C++ ports will possibly be build
> inconsistently because macports-gcc6 will use the MacPorts-provided runtimes
> from libgcc which are not compatible with the host's libstdc++ (used by
> gcc42).
>
> If you want to use gcc6 for a full build of MacPorts on
> On Oct 20, 2017, at 20:32, Ken Cunningham
> wrote:
>
>
>
>> On Oct 20, 2017, at 7:39 PM, Ryan Schmidt wrote:
>>
>> I guess my question was: is there something unique about ffmpeg that makes
>> it require gcc6 on PowerPC, as opposed to one of the alternatives MacPorts
>> would choose, o
Note that credential.helper=osxkeychain is the default when using git provided
by Xcode. If you recently installed the git project in MacPorts (or
elsewhere), that might explain why you're now entering your password.
> On Oct 20, 2017, at 20:10, Joshua Root wrote:
>
> On 2017-10-21 08:00 , Cr
> On Oct 20, 2017, at 7:39 PM, Ryan Schmidt wrote:
>
> I guess my question was: is there something unique about ffmpeg that makes it
> require gcc6 on PowerPC, as opposed to one of the alternatives MacPorts would
> choose, or is MacPorts choosing inappropriate alternatives for all ports on
>
On 2017-10-21 08:00 , Craig Treleaven wrote:
Hi:
Lately, I have to enter my github username and password every time I commit;
git used to just remember these. I suppose it is in a hidden config file
somewhere but I don’t know where.
Could some kind soul please give me directions in suitably
I guess my question was: is there something unique about ffmpeg that makes it
require gcc6 on PowerPC, as opposed to one of the alternatives MacPorts would
choose, or is MacPorts choosing inappropriate alternatives for all ports on
PowerPC? If the latter, the fix should be in base, not in indivi
The fallbacks on PPC don't work correctly, I find.
If I were to blacklist gcc42, MacPorts would lead in almost all cases to
building it with clang-3.4, which always fails.
Also, there's no point falling back to any gcc prior to gcc6.
So what I saw as options was to blacklist:
all the gcc vers
On Oct 20, 2017, at 20:49, Ken wrote:
> Ken (kencu) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/e1f1b6b20678fed08e81f8a65ea0062f59a1f64c
>
> The following commit(s) were added to refs/heads/master by this push:
>
>
On Oct 20, 2017, at 16:03, Marcus Calhoun-Lopez wrote:
> On Fri, Oct 20, 2017 at 1:32 PM, Mojca Miklavec wrote:
>> On 20 October 2017 at 11:58, Marcus Calhoun-Lopez wrote:
>>> I am trying to figure out whey llvm-5.0 and clang-5.0 are not located
>>> on packages.macports.org for Mac OS X 10.6.
>>
>
Hi:
$ git remote -v
origin https://github.com/macports/macports-ports.git (fetch)
origin https://github.com/macports/macports-ports.git (push)
So, you’re saying that it is normal to have to enter the userid/password on
each commit? Maybe senility is sneaking up on me, but I don’t think I had
Craig,
What is the result of `git remote -v`?
Path 1: If it is http, that makes sense that it prompts you each time you push
(not commit) for your username/password. It is possible to set up ssh keys for
connecting to GitHub without entering username/password every time.
Path 2: If it is gi
The files are now available on packages.macports.org.
My apologies for the noise.
-Marcus
On Fri, Oct 20, 2017 at 1:32 PM, Mojca Miklavec
wrote:
> On 20 October 2017 at 11:58, Marcus Calhoun-Lopez wrote:
>> I am trying to figure out whey llvm-5.0 and clang-5.0 are not located
>> on packages.macp
Hi:
Lately, I have to enter my github username and password every time I commit;
git used to just remember these. I suppose it is in a hidden config file
somewhere but I don’t know where.
Could some kind soul please give me directions in suitably small words for
someone of limited git underst
I am trying to figure out whey llvm-5.0 and clang-5.0 are not located
on packages.macports.org for Mac OS X 10.6.
Below are the steps I have tried.
Can anyone help me understand where I am going wrong?
1) On my local virtual machine, llvm-5.0 and clang-5.0 build on Mac OS X 10.6
(see https://trac.
Could somebody with access to a 10.6 (or earlier) box test if this
builds successfully?
https://github.com/macports/macports-ports/pull/938
Unfortunately, I don't have access to such a box and I need to figure
out if the upstream fix that I incorporated into the above PR solves the
build issu
16 matches
Mail list logo
