Re: Trying to execute LibcxxOnOlderSytems (3rd ed.)

[[ftp83plus]]

Ok, I changed the topic to reflect the new attempt. MacPorts has been 
uninstalled as per instructions, and reinstalled. I am now attempting to run 
https://trac.macports.org/wiki/LibcxxOnOlderSystems in order to support 
software that may be written according to C++11 standard.

I ran step 2 as corrected. No error reported.
I ran step 3.1. No error reported at either step (3.1.1 and 3.1.2).
Edited /opt/local/etc/macports/macports.conf as per step 3.2:
The beginning of the file now looks like:
cxx_stdlib libc++
buildfromsourcealways
delete_la_filesyes
default_compilers  macports-clang-3.4 macports-clang-3.3 gcc-4.2 apple-gcc-4.2 
gcc-4.0

# $Id: macports.conf.in 117120 2014-02-17 00:55:33Z j...@macports.org $ […]

Then step 3.3. Received:
Error: No ports matched the given expression
I assumed it was normal since this is a fresh installation, no port has been 
inactivated by step 3.1.1.

Then step 3.4: was long and noisy, but received no error.
Then step 3.5: no error
Then step 3.6: no error
Then step 3.7: It says to edit /opt/local/etc/macports/macports.conf again ; 
mine now looks like
cxx_stdlib libc++
buildfromsourcealways
delete_la_filesyes
default_compilers  macports-clang-3.7 macports-clang-3.4 macports-clang-3.3 
gcc-4.2 apple-gcc-4.2 gcc-4.0

# $Id: macports.conf.in 117120 2014-02-17 00:55:33Z j...@macports.org $

As I understand it, this is the last step.

Then I tried to install Xsane, but it failed; I will open another thread so as 
to keep this one clean.






El 2016-03-15, a las 01:49, Ryan Schmidt escribió:

> 
>> On Mar 15, 2016, at 12:46 AM, [ftp83plus]  wrote:
>> 
>> Thanks all for your advices,
>> 
>> I see contradictions here: should I start afresh and bear hours of whining 
>> fans like Christopher suggests to make the topic easier to follow, or try to 
>> add precision to my former request like Ryan tries to tell?
>> 
>> The main concern is of course the fan noise and the fact I have to rely on a 
>> much slower backup Mac should I need to leave home. I try to bear in mind 
>> that you guys aren't in fort of my screen, and its not easy to follow who 
>> said what and when.
> 
> If you're stuck on the bootstrapping 2 step, starting over and following the 
> newly edited instructions, without the -s flag on that step, should be very 
> quick, since you'll be getting a precompiled archive from our server rather 
> than having to compile it on your system.
> 
> For subsequent steps, there will still be compiling involved, since we don't 
> yet have a naming convention for distinguishing libc++ packages from 
> libstdc++ packages, so we don't provide libc++ packages for older OSes.
> 
> 
> 
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Ryan Schmidt]

> On Mar 15, 2016, at 12:46 AM, [ftp83plus]  wrote:
> 
> Thanks all for your advices,
> 
> I see contradictions here: should I start afresh and bear hours of whining 
> fans like Christopher suggests to make the topic easier to follow, or try to 
> add precision to my former request like Ryan tries to tell?
> 
> The main concern is of course the fan noise and the fact I have to rely on a 
> much slower backup Mac should I need to leave home. I try to bear in mind 
> that you guys aren't in fort of my screen, and its not easy to follow who 
> said what and when.

If you're stuck on the bootstrapping 2 step, starting over and following the 
newly edited instructions, without the -s flag on that step, should be very 
quick, since you'll be getting a precompiled archive from our server rather 
than having to compile it on your system.

For subsequent steps, there will still be compiling involved, since we don't 
yet have a naming convention for distinguishing libc++ packages from libstdc++ 
packages, so we don't provide libc++ packages for older OSes.




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Thanks all for your advices,

I see contradictions here: should I start afresh and bear hours of whining fans 
like Christopher suggests to make the topic easier to follow, or try to add 
precision to my former request like Ryan tries to tell?

The main concern is of course the fan noise and the fact I have to rely on a 
much slower backup Mac should I need to leave home. I try to bear in mind that 
you guys aren't in fort of my screen, and its not easy to follow who said what 
and when.



Enviado desde mi iPhone

> El 14 mar 2016, a las 15:23, Christopher Jones  
> escribió:
> 
> 
>> On 14 Mar 2016, at 5:14 pm, [ftp83plus]  wrote:
>> 
>> Right, I had to reformat  because the Mac wouldn't boot anymore. 
>> 
>> This is actually a failure on step 1, the
>> 
>> sudo port install -v -f libcxx
>> 
>> Hope that helps.
> 
> No, not really. Like others I have I am afraid completely lost track of what 
> you have and have not run…
> 
> can I suggest you start afresh, so wipe out your current macports 
> installation, start again and this time provide a *full* transcript of 
> everything your run, and the complete final log file showing whatever error 
> you get.. Without that its pretty impossible to follow what you have done so 
> far.
> 
> Chris
> 
> 
>> 
>> Enviado desde mi iPhone
>> 
>>> El 14 mar 2016, a las 5:19, Ryan Schmidt  escribió:
>>> 
>>> 
 On Mar 14, 2016, at 2:14 AM, [ftp83plus]  wrote:
 
> El 2016-03-13, a las 22:14, Brandon Allbery escribió:
> 
> On Sun, Mar 13, 2016 at 10:10 PM, Chris Jones  
> wrote:
> Unordered_set is only available in C++11, which the ancient gcc 4.2 
> compiler being used will not support... 
> 
> Then something has gone wrong because, per subject line, it's supposed to 
> be using a newer clang built with libc++ (aka C++11) support.
>>> 
>>> 
 So is it a case of missing instruction or variant? 
 That one dependency would precisely need the very compiler I am trying to 
 install in case I happen to need it for a recent software written under 
 C++11standard?
>>> 
>>> 
>>> It is difficult for me to follow this thread because it has gone on so long 
>>> and you're not telling us exactly what step of the process you're stuck on.
>>> 
>>> Last month you said you were able to follow the instructions successfully...
>>> 
>>> https://lists.macosforge.org/pipermail/macports-users/2016-February/040540.html
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-users
> 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Ryan Schmidt]

> On Mar 14, 2016, at 7:55 PM, Ryan Schmidt  wrote:
> 
> 
>> On Mar 14, 2016, at 12:14 PM, [ftp83plus]  wrote:
>> 
>> Right, I had to reformat  because the Mac wouldn't boot anymore. 
>> 
>> This is actually a failure on step 1, the
>> 
>> sudo port install -v -f libcxx
> 
> You mean step 2 of bootstrapping 2? Which says to run:
> 
> sudo port -v -s install libcxx

Jeremy has confirmed building from source is not needed at this step, since you 
should still be at the default MacPorts configuration at this point, so if you 
just run

sudo port install libcxx

you should be able to get a binary from our server.


> You normally should not use "-f" to force an installation. And single-letter 
> flags (like "-v" and "-s") must go immediately after the word "port", and 
> before the next word, for them to have any effect.
> 
> Please confirm that at this point, you have not done any of the steps from 
> bootstrapping 3, such as editing macports.conf...


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Ryan Schmidt]

> On Mar 14, 2016, at 12:14 PM, [ftp83plus]  wrote:
> 
> Right, I had to reformat  because the Mac wouldn't boot anymore. 
> 
> This is actually a failure on step 1, the
> 
> sudo port install -v -f libcxx

You mean step 2 of bootstrapping 2? Which says to run:

sudo port -v -s install libcxx

You normally should not use "-f" to force an installation. And single-letter 
flags (like "-v" and "-s") must go immediately after the word "port", and 
before the next word, for them to have any effect.

Please confirm that at this point, you have not done any of the steps from 
bootstrapping 3, such as editing macports.conf...

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Christopher Jones]

> On 14 Mar 2016, at 5:14 pm, [ftp83plus]  wrote:
> 
> Right, I had to reformat  because the Mac wouldn't boot anymore. 
> 
> This is actually a failure on step 1, the
> 
> sudo port install -v -f libcxx
> 
> Hope that helps.

No, not really. Like others I have I am afraid completely lost track of what 
you have and have not run…

can I suggest you start afresh, so wipe out your current macports installation, 
start again and this time provide a *full* transcript of everything your run, 
and the complete final log file showing whatever error you get.. Without that 
its pretty impossible to follow what you have done so far.

Chris


> 
> Enviado desde mi iPhone
> 
> El 14 mar 2016, a las 5:19, Ryan Schmidt  > escribió:
> 
>> 
>> On Mar 14, 2016, at 2:14 AM, [ftp83plus] > > wrote:
>> 
>>> El 2016-03-13, a las 22:14, Brandon Allbery escribió:
>>> 
 On Sun, Mar 13, 2016 at 10:10 PM, Chris Jones > wrote:
 Unordered_set is only available in C++11, which the ancient gcc 4.2 
 compiler being used will not support... 
 
 Then something has gone wrong because, per subject line, it's supposed to 
 be using a newer clang built with libc++ (aka C++11) support.
>> 
>>> 
>> 
>>> So is it a case of missing instruction or variant? 
>>> That one dependency would precisely need the very compiler I am trying to 
>>> install in case I happen to need it for a recent software written under 
>>> C++11standard?
>> 
>> 
>> It is difficult for me to follow this thread because it has gone on so long 
>> and you're not telling us exactly what step of the process you're stuck on.
>> 
>> Last month you said you were able to follow the instructions successfully...
>> 
>> https://lists.macosforge.org/pipermail/macports-users/2016-February/040540.html
>>  
>> 
>> 
>> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users



smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Right, I had to reformat  because the Mac wouldn't boot anymore. 

This is actually a failure on step 1, the

sudo port install -v -f libcxx

Hope that helps.

Enviado desde mi iPhone

> El 14 mar 2016, a las 5:19, Ryan Schmidt  escribió:
> 
> 
>> On Mar 14, 2016, at 2:14 AM, [ftp83plus]  wrote:
>> 
>>> El 2016-03-13, a las 22:14, Brandon Allbery escribió:
>>> 
>>> On Sun, Mar 13, 2016 at 10:10 PM, Chris Jones  
>>> wrote:
>>> Unordered_set is only available in C++11, which the ancient gcc 4.2 
>>> compiler being used will not support... 
>>> 
>>> Then something has gone wrong because, per subject line, it's supposed to 
>>> be using a newer clang built with libc++ (aka C++11) support.
> 
> 
>> So is it a case of missing instruction or variant? 
>> That one dependency would precisely need the very compiler I am trying to 
>> install in case I happen to need it for a recent software written under 
>> C++11standard?
> 
> 
> It is difficult for me to follow this thread because it has gone on so long 
> and you're not telling us exactly what step of the process you're stuck on.
> 
> Last month you said you were able to follow the instructions successfully...
> 
> https://lists.macosforge.org/pipermail/macports-users/2016-February/040540.html
> 
> 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Ryan Schmidt]

On Mar 14, 2016, at 2:14 AM, [ftp83plus]  wrote:

> El 2016-03-13, a las 22:14, Brandon Allbery escribió:
> 
>> On Sun, Mar 13, 2016 at 10:10 PM, Chris Jones  
>> wrote:
>> Unordered_set is only available in C++11, which the ancient gcc 4.2 compiler 
>> being used will not support... 
>> 
>> Then something has gone wrong because, per subject line, it's supposed to be 
>> using a newer clang built with libc++ (aka C++11) support.

> 

> So is it a case of missing instruction or variant? 
> That one dependency would precisely need the very compiler I am trying to 
> install in case I happen to need it for a recent software written under 
> C++11standard?


It is difficult for me to follow this thread because it has gone on so long and 
you're not telling us exactly what step of the process you're stuck on.

Last month you said you were able to follow the instructions successfully...

https://lists.macosforge.org/pipermail/macports-users/2016-February/040540.html


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

So is it a case of missing instruction or variant? 
That one dependency would precisely need the very compiler I am trying to 
install in case I happen to need it for a recent software written under 
C++11standard?


El 2016-03-13, a las 22:14, Brandon Allbery escribió:

> On Sun, Mar 13, 2016 at 10:10 PM, Chris Jones  
> wrote:
> Unordered_set is only available in C++11, which the ancient gcc 4.2 compiler 
> being used will not support... 
> 
> Then something has gone wrong because, per subject line, it's supposed to be 
> using a newer clang built with libc++ (aka C++11) support.
> 
> -- 
> brandon s allbery kf8nh   sine nomine associates
> allber...@gmail.com  ballb...@sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Brandon Allbery]

On Sun, Mar 13, 2016 at 10:10 PM, Chris Jones 
wrote:

> Unordered_set is only available in C++11, which the ancient gcc 4.2
> compiler being used will not support...


Then something has gone wrong because, per subject line, it's supposed to
be using a newer clang built with libc++ (aka C++11) support.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Chris Jones]

> On 14 Mar 2016, at 12:49 am, [ftp83plus]  wrote:
> 
> I thought I done that with :
> 
>> sudo port clean ld64-136
>> and
>> sudo port clean libcxx
>> 
>> as ld54-136 failed to compile as a dependency of libcxx. Received:
>> 
>> Error: Failed to install ld64-136
>> Please see the log file for port ld64-136 for details:
>> 
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64-136/main.log
>> Error: The following dependencies were not installed: clang-3.4 ld64 
>> ld64-136 libcxxab
> 
> 
> After correcting these lines in the macports.conf file following Ryan's 
> advice:
> 
> # Whether MacPorts should automatically run rev-upgrade after upgrading
> # ports.
> #revupgrade_autorun yes
> 
> # Whether rev-upgrade should automatically rebuild ports with broken
> # linking or merely report the breakage. Supported values are "report"
> # and "rebuild".
> revupgrade_mode report
> 
> The last line originally read:
> #revupgrade_mode  rebuild
> 
> ld64-136 build log is there: http://pastebin.com/rJ95ZwK9
> libcxx build log is there: http://pastebin.com/7DZGYGCV
> Both logs were updated at the same time, so I posted them both.
> 
> I don't see the "Skipping complete" anymore in the logs as Ryan said, but the 
> first error reads:
> :info:build src/ld/parsers/lto_file.cpp:36:25: error: unordered_set: No such 
> file or directory
> 
> Could it be that some important file is missing or wasn't fetched properly?


Unordered_set is only available in C++11, which the ancient gcc 4.2 compiler 
being used will not support... 
> 
> 
> 
>> El 2016-03-13, a las 16:11, Chris Jones escribió:
>> 
>> 
>> 
>>> On 13 Mar 2016, at 7:02 pm, [ftp83plus]  wrote:
>>> 
>>> Ok, thanks for specifying. 
>>> 
>>> Why does it fail, now?
>> 
>> Because you have not changed anything... You are simply explicitly 
>> specifying some options identical to the defaults... You need to follow the 
>> advice Ryan has already given you...
>> 
>>> 
 El 2016-03-13, a las 12:30, Brandon Allbery escribió:
 
> On Sun, Mar 13, 2016 at 5:18 AM, [ftp83plus]  wrote:
> Now it's getting even more confusing for me: why would a commented out 
> line still be run? 
 
 The comment is showing you what the default action is if you don't say 
 anything.
 
 -- 
 brandon s allbery kf8nh   sine nomine 
 associates
 allber...@gmail.com  
 ballb...@sinenomine.net
 unix, openafs, kerberos, infrastructure, xmonad
 http://sinenomine.net
>>> 
>>> ___
>>> macports-users mailing list
>>> macports-users@lists.macosforge.org
>>> https://lists.macosforge.org/mailman/listinfo/macports-users
> 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

I thought I done that with :

> sudo port clean ld64-136
> and
> sudo port clean libcxx
> 
> as ld54-136 failed to compile as a dependency of libcxx. Received:
> 
> Error: Failed to install ld64-136
> Please see the log file for port ld64-136 for details:
> 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64-136/main.log
> Error: The following dependencies were not installed: clang-3.4 ld64 ld64-136 
> libcxxab


After correcting these lines in the macports.conf file following Ryan's advice:

# Whether MacPorts should automatically run rev-upgrade after upgrading
# ports.
#revupgrade_autorun yes

# Whether rev-upgrade should automatically rebuild ports with broken
# linking or merely report the breakage. Supported values are "report"
# and "rebuild".
revupgrade_mode report

The last line originally read:
#revupgrade_moderebuild

ld64-136 build log is there: http://pastebin.com/rJ95ZwK9
libcxx build log is there: http://pastebin.com/7DZGYGCV
Both logs were updated at the same time, so I posted them both.

I don't see the "Skipping complete" anymore in the logs as Ryan said, but the 
first error reads:
:info:build src/ld/parsers/lto_file.cpp:36:25: error: unordered_set: No such 
file or directory

Could it be that some important file is missing or wasn't fetched properly?



El 2016-03-13, a las 16:11, Chris Jones escribió:

> 
> 
> On 13 Mar 2016, at 7:02 pm, [ftp83plus]  wrote:
> 
>> Ok, thanks for specifying. 
>> 
>> Why does it fail, now?
> 
> Because you have not changed anything... You are simply explicitly specifying 
> some options identical to the defaults... You need to follow the advice Ryan 
> has already given you...
> 
>> 
>> El 2016-03-13, a las 12:30, Brandon Allbery escribió:
>> 
>>> On Sun, Mar 13, 2016 at 5:18 AM, [ftp83plus]  wrote:
>>> Now it's getting even more confusing for me: why would a commented out line 
>>> still be run? 
>>> 
>>> The comment is showing you what the default action is if you don't say 
>>> anything.
>>> 
>>> -- 
>>> brandon s allbery kf8nh   sine nomine associates
>>> allber...@gmail.com  ballb...@sinenomine.net
>>> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
>> 
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Chris Jones]

> On 13 Mar 2016, at 7:02 pm, [ftp83plus]  wrote:
> 
> Ok, thanks for specifying. 
> 
> Why does it fail, now?

Because you have not changed anything... You are simply explicitly specifying 
some options identical to the defaults... You need to follow the advice Ryan 
has already given you...

> 
>> El 2016-03-13, a las 12:30, Brandon Allbery escribió:
>> 
>>> On Sun, Mar 13, 2016 at 5:18 AM, [ftp83plus]  wrote:
>>> Now it's getting even more confusing for me: why would a commented out line 
>>> still be run? 
>> 
>> The comment is showing you what the default action is if you don't say 
>> anything.
>> 
>> -- 
>> brandon s allbery kf8nh   sine nomine associates
>> allber...@gmail.com  ballb...@sinenomine.net
>> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Ok, thanks for specifying. 

Why does it fail, now?

El 2016-03-13, a las 12:30, Brandon Allbery escribió:

> On Sun, Mar 13, 2016 at 5:18 AM, [ftp83plus]  wrote:
> Now it's getting even more confusing for me: why would a commented out line 
> still be run? 
> 
> The comment is showing you what the default action is if you don't say 
> anything.
> 
> -- 
> brandon s allbery kf8nh   sine nomine associates
> allber...@gmail.com  ballb...@sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Brandon Allbery]

On Sun, Mar 13, 2016 at 5:18 AM, [ftp83plus]  wrote:

> Now it's getting even more confusing for me: why would a commented out
> line still be run?


The comment is showing you what the default action is if you don't say
anything.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Now it's getting even more confusing for me: why would a commented out line 
still be run? 

Anyway I un-commented it and replaced "rebuild" by "report"

Log is here:
http://pastebin.com/g4A7B4Cp

But still no installation…



El 2016-03-12, a las 08:39, Ryan Schmidt escribió:

> 
>> On Mar 11, 2016, at 11:33 PM, [ftp83plus]  wrote:
>> 
>> Hi there, 
>> 
>> back after days of being unable to work on MacPorts.
>> 
>> for revupgrade, I have, in /opt/local/etc/macports/macports.conf:
>> 
>> #revupgrade_autorun yes
>> #revupgrade_moderebuild
>> 
>> So I don't think it it is the culprit.
> 
> The default is to rebuild. Rebuilding may be the problem. Set it to report 
> instead and try again, after cleaning again.
> 
> 
>> 
>> First step of Bug Reporting Guidelines:
>> "Clean and try again:"
>> FAILS
>> Log is here: http://pastebin.com/HzyGx3ei
> 
> That log contains lines that say "Skipping completed". This means it was not 
> a clean attempt. It could be that although you cleaned before trying again, 
> rev-upgrade then tried to rebuild it again (uncleanly). That's why I suggest 
> turning rev-upgrade off for a moment to test.
> 
> 
>> I still fail to understand wether this is a true bug or an error of my part.
>> 
>> 
>> 
>> 
>> 
>> El 2016-02-29, a las 06:21, Ryan Schmidt escribió:
>> 
>>> 
 On Feb 28, 2016, at 9:33 PM, [ftp83plus]  wrote:
 
 Did that
 sudo port clean ld64-136
 and
 sudo port clean libcxx
 
 as ld54-136 failed to compile as a dependency of libcxx. Received:
 
 Error: Failed to install ld64-136
 Please see the log file for port ld64-136 for details:
   
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64-136/main.log
 Error: The following dependencies were not installed: clang-3.4 ld64 
 ld64-136 libcxxab
 
 log is available at
 http://pastebin.com/DKp0a4n9
 
 thanks
>>> 
>>> The log still contains lines that say "Skipping completed" which means the 
>>> log was not from a clean attempt.
>>> 
>>> Is rev-upgrade perhaps running and trying 3 times to rebuild? If so, 
>>> temporarily disable rev-upgrade in macports.conf.
>>> 
>>> 
>> 
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Ryan Schmidt]

> On Mar 11, 2016, at 11:33 PM, [ftp83plus]  wrote:
> 
> Hi there, 
> 
> back after days of being unable to work on MacPorts.
> 
> for revupgrade, I have, in /opt/local/etc/macports/macports.conf:
> 
> #revupgrade_autorun yes
> #revupgrade_moderebuild
> 
> So I don't think it it is the culprit.

The default is to rebuild. Rebuilding may be the problem. Set it to report 
instead and try again, after cleaning again.


> 
> First step of Bug Reporting Guidelines:
> "Clean and try again:"
> FAILS
> Log is here: http://pastebin.com/HzyGx3ei

That log contains lines that say "Skipping completed". This means it was not a 
clean attempt. It could be that although you cleaned before trying again, 
rev-upgrade then tried to rebuild it again (uncleanly). That's why I suggest 
turning rev-upgrade off for a moment to test.


> I still fail to understand wether this is a true bug or an error of my part.
> 
> 
> 
> 
> 
> El 2016-02-29, a las 06:21, Ryan Schmidt escribió:
> 
>> 
>>> On Feb 28, 2016, at 9:33 PM, [ftp83plus]  wrote:
>>> 
>>> Did that
>>> sudo port clean ld64-136
>>> and
>>> sudo port clean libcxx
>>> 
>>> as ld54-136 failed to compile as a dependency of libcxx. Received:
>>> 
>>> Error: Failed to install ld64-136
>>> Please see the log file for port ld64-136 for details:
>>>
>>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64-136/main.log
>>> Error: The following dependencies were not installed: clang-3.4 ld64 
>>> ld64-136 libcxxab
>>> 
>>> log is available at
>>> http://pastebin.com/DKp0a4n9
>>> 
>>> thanks
>> 
>> The log still contains lines that say "Skipping completed" which means the 
>> log was not from a clean attempt.
>> 
>> Is rev-upgrade perhaps running and trying 3 times to rebuild? If so, 
>> temporarily disable rev-upgrade in macports.conf.
>> 
>> 
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Hi there, 

back after days of being unable to work on MacPorts.

for revupgrade, I have, in /opt/local/etc/macports/macports.conf:

#revupgrade_autorun yes
#revupgrade_moderebuild

So I don't think it it is the culprit.


First step of Bug Reporting Guidelines:
"Clean and try again:"
FAILS
Log is here: http://pastebin.com/HzyGx3ei


I still fail to understand wether this is a true bug or an error of my part.





El 2016-02-29, a las 06:21, Ryan Schmidt escribió:

> 
>> On Feb 28, 2016, at 9:33 PM, [ftp83plus]  wrote:
>> 
>> Did that
>> sudo port clean ld64-136
>> and
>> sudo port clean libcxx
>> 
>> as ld54-136 failed to compile as a dependency of libcxx. Received:
>> 
>> Error: Failed to install ld64-136
>> Please see the log file for port ld64-136 for details:
>>
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64-136/main.log
>> Error: The following dependencies were not installed: clang-3.4 ld64 
>> ld64-136 libcxxab
>> 
>> log is available at
>> http://pastebin.com/DKp0a4n9
>> 
>> thanks
> 
> The log still contains lines that say "Skipping completed" which means the 
> log was not from a clean attempt.
> 
> Is rev-upgrade perhaps running and trying 3 times to rebuild? If so, 
> temporarily disable rev-upgrade in macports.conf.
> 
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Ryan Schmidt]

> On Feb 28, 2016, at 9:33 PM, [ftp83plus]  wrote:
> 
> Did that
> sudo port clean ld64-136
> and
> sudo port clean libcxx
> 
> as ld54-136 failed to compile as a dependency of libcxx. Received:
> 
> Error: Failed to install ld64-136
> Please see the log file for port ld64-136 for details:
> 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64-136/main.log
> Error: The following dependencies were not installed: clang-3.4 ld64 ld64-136 
> libcxxab
> 
> log is available at
> http://pastebin.com/DKp0a4n9
> 
> thanks

The log still contains lines that say "Skipping completed" which means the log 
was not from a clean attempt.

Is rev-upgrade perhaps running and trying 3 times to rebuild? If so, 
temporarily disable rev-upgrade in macports.conf.


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Did that
sudo port clean ld64-136
and
sudo port clean libcxx

as ld54-136 failed to compile as a dependency of libcxx. Received:

Error: Failed to install ld64-136
Please see the log file for port ld64-136 for details:

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64-136/main.log
Error: The following dependencies were not installed: clang-3.4 ld64 ld64-136 
libcxxab

log is available at
http://pastebin.com/DKp0a4n9

thanks


El 2016-02-28, a las 9:45 PM, Ryan Schmidt escribió:

> On Feb 28, 2016, at 19:15, [ftp83plus]  wrote:
> 
>> I had a serious issue with the machine, and needed to reformat the whole 
>> machine.
>> 
>> One of my first step was of course to reinstall MacPorts and selfupdate it. 
>> I started from a clean machine. But now fails to build clang-3.4. There's a 
>> full pastebin fo the log there:
>> http://pastebin.com/65xnyTKj
>> 
>> What is it, exactly?
> 
> That's a build failure of ld64-136, not clang-3.4. And it was not a clean 
> build attempt. Do the first step in the bug reporting guidelines and clean 
> the failing port and try again. 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Hi there, 

I had a serious issue with the machine, and needed to reformat the whole 
machine.

One of my first step was of course to reinstall MacPorts and selfupdate it. I 
started from a clean machine. But now fails to build clang-3.4. There's a full 
pastebin fo the log there:
http://pastebin.com/65xnyTKj

What is it, exactly?

Thanks all,



El 2016-02-12, a las 12:46 PM, Jeremy Huddleston Sequoia escribió:

> 
>> On Feb 12, 2016, at 09:02, Ryan Schmidt  wrote:
>> 
>> 
>> On Feb 11, 2016, at 9:06 PM, Ryan Schmidt wrote:
>> 
>>> On Feb 11, 2016, at 19:27, [ftp83plus]  wrote:
 
 Hum, still fails:
 
 --->  Deactivating llvm-3.4 @3.4.2_8
 --->  Unable to deactivate llvm-3.4 @3.4.2_8, the following ports depend 
 on it:
 --->  ld64-136 @136_2+llvm34
 Error: org.macports.deactivate for port llvm-3.4 returned: Please 
 uninstall the ports that depend on llvm-3.4 first.
>>> 
>>> So uninstall ld64-136 @136_2+llvm34 first. Check the revised instructions 
>>> in the wiki.
>> 
>> Sorry, the revised instructions I was referring to are the ones that were 
>> already mentioned by Jeremy earlier in this thread: to uninstall inactive 
>> ports.
>> 
>> The instructions appear to still have an error: step 5 says to rebuild ld64 
>> with the +llvm37 variant, but ld64 doesn't have llvm variants; its subports 
>> do. You have rebuild whichever subport of ld64 you're using with the +llvm37 
>> variant. In your case, that subport is ld64-136 so you need to run:
>> 
>> sudo port -v -n upgrade --force --enforce-variants ld64-136 -llvm33 -llvm34 
>> +llvm37 configure.compiler=macports-clang-3.7
>> 
>> Then you can uninstall inactive ports, which will then include ld64-136 
>> @136_2+llvm34.
> 
> Right, I forgot about that.  Give this a try as it should end up just 
> updating your relevant ld64 subport:
> 
> sudo port -v upgrade --force --enforce-variants ld64 -llvm33 -llvm34 +llvm37 
> configure.compiler=macports-clang-3.7
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Ryan Schmidt]

On Feb 11, 2016, at 9:06 PM, Ryan Schmidt wrote:

> On Feb 11, 2016, at 19:27, [ftp83plus]  wrote:
>> 
>> Hum, still fails:
>> 
>> --->  Deactivating llvm-3.4 @3.4.2_8
>> --->  Unable to deactivate llvm-3.4 @3.4.2_8, the following ports depend on 
>> it:
>> --->  ld64-136 @136_2+llvm34
>> Error: org.macports.deactivate for port llvm-3.4 returned: Please uninstall 
>> the ports that depend on llvm-3.4 first.
> 
> So uninstall ld64-136 @136_2+llvm34 first. Check the revised instructions in 
> the wiki.

Sorry, the revised instructions I was referring to are the ones that were 
already mentioned by Jeremy earlier in this thread: to uninstall inactive ports.

The instructions appear to still have an error: step 5 says to rebuild ld64 
with the +llvm37 variant, but ld64 doesn't have llvm variants; its subports do. 
You have rebuild whichever subport of ld64 you're using with the +llvm37 
variant. In your case, that subport is ld64-136 so you need to run:

sudo port -v -n upgrade --force --enforce-variants ld64-136 -llvm33 -llvm34 
+llvm37 configure.compiler=macports-clang-3.7

Then you can uninstall inactive ports, which will then include ld64-136 
@136_2+llvm34.


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Jeremy Huddleston Sequoia]

> On Feb 12, 2016, at 09:02, Ryan Schmidt  wrote:
> 
> 
> On Feb 11, 2016, at 9:06 PM, Ryan Schmidt wrote:
> 
>> On Feb 11, 2016, at 19:27, [ftp83plus]  wrote:
>>> 
>>> Hum, still fails:
>>> 
>>> --->  Deactivating llvm-3.4 @3.4.2_8
>>> --->  Unable to deactivate llvm-3.4 @3.4.2_8, the following ports depend on 
>>> it:
>>> --->  ld64-136 @136_2+llvm34
>>> Error: org.macports.deactivate for port llvm-3.4 returned: Please uninstall 
>>> the ports that depend on llvm-3.4 first.
>> 
>> So uninstall ld64-136 @136_2+llvm34 first. Check the revised instructions in 
>> the wiki.
> 
> Sorry, the revised instructions I was referring to are the ones that were 
> already mentioned by Jeremy earlier in this thread: to uninstall inactive 
> ports.
> 
> The instructions appear to still have an error: step 5 says to rebuild ld64 
> with the +llvm37 variant, but ld64 doesn't have llvm variants; its subports 
> do. You have rebuild whichever subport of ld64 you're using with the +llvm37 
> variant. In your case, that subport is ld64-136 so you need to run:
> 
> sudo port -v -n upgrade --force --enforce-variants ld64-136 -llvm33 -llvm34 
> +llvm37 configure.compiler=macports-clang-3.7
> 
> Then you can uninstall inactive ports, which will then include ld64-136 
> @136_2+llvm34.

Right, I forgot about that.  Give this a try as it should end up just updating 
your relevant ld64 subport:

sudo port -v upgrade --force --enforce-variants ld64 -llvm33 -llvm34 +llvm37 
configure.compiler=macports-clang-3.7

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Hello, 

that worked, thanks to all Jeremy, Ryan, Bradley and Rainer!



El 12 févr. 2016, a las 12:46, Jeremy Huddleston Sequoia escribió:

> 
>> On Feb 12, 2016, at 09:02, Ryan Schmidt  wrote:
>> 
>> 
>> On Feb 11, 2016, at 9:06 PM, Ryan Schmidt wrote:
>> 
>>> On Feb 11, 2016, at 19:27, [ftp83plus]  wrote:
 
 Hum, still fails:
 
 --->  Deactivating llvm-3.4 @3.4.2_8
 --->  Unable to deactivate llvm-3.4 @3.4.2_8, the following ports depend 
 on it:
 --->  ld64-136 @136_2+llvm34
 Error: org.macports.deactivate for port llvm-3.4 returned: Please 
 uninstall the ports that depend on llvm-3.4 first.
>>> 
>>> So uninstall ld64-136 @136_2+llvm34 first. Check the revised instructions 
>>> in the wiki.
>> 
>> Sorry, the revised instructions I was referring to are the ones that were 
>> already mentioned by Jeremy earlier in this thread: to uninstall inactive 
>> ports.
>> 
>> The instructions appear to still have an error: step 5 says to rebuild ld64 
>> with the +llvm37 variant, but ld64 doesn't have llvm variants; its subports 
>> do. You have rebuild whichever subport of ld64 you're using with the +llvm37 
>> variant. In your case, that subport is ld64-136 so you need to run:
>> 
>> sudo port -v -n upgrade --force --enforce-variants ld64-136 -llvm33 -llvm34 
>> +llvm37 configure.compiler=macports-clang-3.7
>> 
>> Then you can uninstall inactive ports, which will then include ld64-136 
>> @136_2+llvm34.
> 
> Right, I forgot about that.  Give this a try as it should end up just 
> updating your relevant ld64 subport:
> 
> sudo port -v upgrade --force --enforce-variants ld64 -llvm33 -llvm34 +llvm37 
> configure.compiler=macports-clang-3.7
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Bradley Giesbrecht]

> On Feb 11, 2016, at 10:37 AM, [ftp83plus]  wrote:
> 
> Not working, ld64-136 must be uninstalled first:
> 
> --->  Deactivating llvm-3.4 @3.4.2_8
> --->  Unable to deactivate llvm-3.4 @3.4.2_8, the following ports depend on 
> it:
> --->  ld64-136 @136_2+llvm34
> Error: org.macports.deactivate for port llvm-3.4 returned: Please uninstall 
> the ports that depend on llvm-3.4 first.
> 
> Is my assumed syntax correct? Or should I simply add ld64-136 to the 
> "deactivate" line?

Yes, llvm-3.4 is installed with the +llvm34 variant which is preventing the 
deactivation of llvm-3.4.

Regards,
Bradley Giesbrecht (pixilla)

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Rainer Müller]

On 2016-02-11 01:55, [ftp83plus] wrote:
> should I type
> sudo port -v uninstall cctools +llvm34
> sudo port -v uninstall ld64-136 +llvm34
> 
> then do 
> sudo port -v uninstall llvm-3.4 clang-3.4
> ?
> 
> The guide is not too clear on the exact syntax.

Specify the version and variants as listed in the output. You can also
look this up with 'port installed'. For example:

$ port installed cctools
The following ports are currently installed:
  cctools @877.5_2+llvm34 (active)
  ...

$ sudo port uninstall cctools @877.5_2+llvm34

HTH,
Rainer
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Hum, still fails:

--->  Deactivating llvm-3.4 @3.4.2_8
--->  Unable to deactivate llvm-3.4 @3.4.2_8, the following ports depend on it:
--->ld64-136 @136_2+llvm34
Error: org.macports.deactivate for port llvm-3.4 returned: Please uninstall the 
ports that depend on llvm-3.4 first.



El 11 févr. 2016, a las 16:19, Bradley Giesbrecht escribió:

>> On Feb 11, 2016, at 1:08 PM, [ftp83plus]  wrote:
>> 
>> Did you mean "ld64-136 is installed with the +llvm64 variant" ?
>> 
>> Just want to be sure
>> 
>> El 11 févr. 2016, a las 15:16, Bradley Giesbrecht escribió:
>> 
 On Feb 11, 2016, at 10:37 AM, [ftp83plus]  wrote:
 
 Not working, ld64-136 must be uninstalled first:
 
 --->  Deactivating llvm-3.4 @3.4.2_8
 --->  Unable to deactivate llvm-3.4 @3.4.2_8, the following ports depend 
 on it:
 --->   ld64-136 @136_2+llvm34
 Error: org.macports.deactivate for port llvm-3.4 returned: Please 
 uninstall the ports that depend on llvm-3.4 first.
 
 Is my assumed syntax correct? Or should I simply add ld64-136 to the 
 "deactivate" line?
>>> 
>>> Yes, llvm-3.4 is installed with the +llvm34 variant which is preventing the 
>>> deactivation of llvm-3.4.
> 
> Correct, I meant to say “ld64-136 is installed with the +llvm34 variant”.
> 
> port info --depends ld64-136 +llvm34
> depends_build: path:include/mach-o/arm/reloc.h:libmacho-headers
> depends_run: 
> depends_fetch: 
> depends_lib: port:llvm-3.4
> depends_extract: 
> 
> 
> Regards,
> Bradley Giesbrecht (pixilla)
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Did you mean "ld64-136 is installed with the +llvm64 variant" ?

Just want to be sure

El 11 févr. 2016, a las 15:16, Bradley Giesbrecht escribió:

>> On Feb 11, 2016, at 10:37 AM, [ftp83plus]  wrote:
>> 
>> Not working, ld64-136 must be uninstalled first:
>> 
>> --->  Deactivating llvm-3.4 @3.4.2_8
>> --->  Unable to deactivate llvm-3.4 @3.4.2_8, the following ports depend on 
>> it:
>> ---> ld64-136 @136_2+llvm34
>> Error: org.macports.deactivate for port llvm-3.4 returned: Please uninstall 
>> the ports that depend on llvm-3.4 first.
>> 
>> Is my assumed syntax correct? Or should I simply add ld64-136 to the 
>> "deactivate" line?
> 
> Yes, llvm-3.4 is installed with the +llvm34 variant which is preventing the 
> deactivation of llvm-3.4.
> 
> Regards,
> Bradley Giesbrecht (pixilla)
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Bradley Giesbrecht]

> On Feb 11, 2016, at 1:08 PM, [ftp83plus]  wrote:
> 
> Did you mean "ld64-136 is installed with the +llvm64 variant" ?
> 
> Just want to be sure
> 
> El 11 févr. 2016, a las 15:16, Bradley Giesbrecht escribió:
> 
>>> On Feb 11, 2016, at 10:37 AM, [ftp83plus]  wrote:
>>> 
>>> Not working, ld64-136 must be uninstalled first:
>>> 
>>> --->  Deactivating llvm-3.4 @3.4.2_8
>>> --->  Unable to deactivate llvm-3.4 @3.4.2_8, the following ports depend on 
>>> it:
>>> --->ld64-136 @136_2+llvm34
>>> Error: org.macports.deactivate for port llvm-3.4 returned: Please uninstall 
>>> the ports that depend on llvm-3.4 first.
>>> 
>>> Is my assumed syntax correct? Or should I simply add ld64-136 to the 
>>> "deactivate" line?
>> 
>> Yes, llvm-3.4 is installed with the +llvm34 variant which is preventing the 
>> deactivation of llvm-3.4.

Correct, I meant to say “ld64-136 is installed with the +llvm34 variant”.

port info --depends ld64-136 +llvm34
depends_build: path:include/mach-o/arm/reloc.h:libmacho-headers
depends_run: 
depends_fetch: 
depends_lib: port:llvm-3.4
depends_extract: 


Regards,
Bradley Giesbrecht (pixilla)

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Ryan Schmidt]

On Feb 11, 2016, at 19:27, [ftp83plus]  wrote:
> 
> Hum, still fails:
> 
> --->  Deactivating llvm-3.4 @3.4.2_8
> --->  Unable to deactivate llvm-3.4 @3.4.2_8, the following ports depend on 
> it:
> --->  ld64-136 @136_2+llvm34
> Error: org.macports.deactivate for port llvm-3.4 returned: Please uninstall 
> the ports that depend on llvm-3.4 first.

So uninstall ld64-136 @136_2+llvm34 first. Check the revised instructions in 
the wiki. 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Jeremy Huddleston Sequoia]

> On Feb 10, 2016, at 16:55, [ftp83plus]  wrote:
> 
> Thanks both, 
> 
> should I type
> sudo port -v uninstall cctools +llvm34
> sudo port -v uninstall ld64-136 +llvm34
> 
> then do 
> sudo port -v uninstall llvm-3.4 clang-3.4
> ?
> 
> The guide is not too clear on the exact syntax.

I updated the wiki shortly after sending that email.  Please do what the guide 
instructs:

sudo port -v deactivate llvm-3.4 clang-3.4
sudo port -v uninstall inactive

Is that not working for you for some reason?

> 
> Pat
> 
> 
> El 9 févr. 2016, a las 15:26, Jeremy Huddleston Sequoia escribió:
> 
>> 
>>> On Feb 9, 2016, at 12:12, Ryan Schmidt  wrote:
>>> 
>>> On Feb 9, 2016, at 13:30, [ftp83plus]  wrote:
 
 Ok, after a night of fetching-compiling, it now fails at step 6
 
 --->  Unable to uninstall llvm-3.4 @3.4.2_8, the following ports depend on 
 it:
 --->  cctools @877.5_2+llvm34
 --->  ld64-136 @136_2+llvm34
>>> 
>>> I guess there's a missing step between steps 5 and 6 telling you to 
>>> uninstall those +llvm34 versions of cctools and ld64-136. 
>> 
>> Yep.  Just uninstall those at the same time and you'll be fine.  I'll update 
>> the wiki later.
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Not working, ld64-136 must be uninstalled first:

--->  Deactivating llvm-3.4 @3.4.2_8
--->  Unable to deactivate llvm-3.4 @3.4.2_8, the following ports depend on it:
--->ld64-136 @136_2+llvm34
Error: org.macports.deactivate for port llvm-3.4 returned: Please uninstall the 
ports that depend on llvm-3.4 first.

Is my assumed syntax correct? Or should I simply add ld64-136 to the 
"deactivate" line?



El 11 févr. 2016, a las 13:16, Jeremy Huddleston Sequoia escribió:

> 
>> On Feb 10, 2016, at 16:55, [ftp83plus]  wrote:
>> 
>> Thanks both, 
>> 
>> should I type
>> sudo port -v uninstall cctools +llvm34
>> sudo port -v uninstall ld64-136 +llvm34
>> 
>> then do 
>> sudo port -v uninstall llvm-3.4 clang-3.4
>> ?
>> 
>> The guide is not too clear on the exact syntax.
> 
> I updated the wiki shortly after sending that email.  Please do what the 
> guide instructs:
> 
> sudo port -v deactivate llvm-3.4 clang-3.4
> sudo port -v uninstall inactive
> 
> Is that not working for you for some reason?
> 
>> 
>> Pat
>> 
>> 
>> El 9 févr. 2016, a las 15:26, Jeremy Huddleston Sequoia escribió:
>> 
>>> 
 On Feb 9, 2016, at 12:12, Ryan Schmidt  wrote:
 
 On Feb 9, 2016, at 13:30, [ftp83plus]  wrote:
> 
> Ok, after a night of fetching-compiling, it now fails at step 6
> 
> --->  Unable to uninstall llvm-3.4 @3.4.2_8, the following ports depend 
> on it:
> --->  cctools @877.5_2+llvm34
> --->  ld64-136 @136_2+llvm34
 
 I guess there's a missing step between steps 5 and 6 telling you to 
 uninstall those +llvm34 versions of cctools and ld64-136. 
>>> 
>>> Yep.  Just uninstall those at the same time and you'll be fine.  I'll 
>>> update the wiki later.
>> 
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-users
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Thanks both, 

should I type
sudo port -v uninstall cctools +llvm34
sudo port -v uninstall ld64-136 +llvm34

then do 
sudo port -v uninstall llvm-3.4 clang-3.4
?

The guide is not too clear on the exact syntax.

Pat


El 9 févr. 2016, a las 15:26, Jeremy Huddleston Sequoia escribió:

> 
>> On Feb 9, 2016, at 12:12, Ryan Schmidt  wrote:
>> 
>> On Feb 9, 2016, at 13:30, [ftp83plus]  wrote:
>>> 
>>> Ok, after a night of fetching-compiling, it now fails at step 6
>>> 
>>> --->  Unable to uninstall llvm-3.4 @3.4.2_8, the following ports depend on 
>>> it:
>>> --->  cctools @877.5_2+llvm34
>>> --->  ld64-136 @136_2+llvm34
>> 
>> I guess there's a missing step between steps 5 and 6 telling you to 
>> uninstall those +llvm34 versions of cctools and ld64-136. 
> 
> Yep.  Just uninstall those at the same time and you'll be fine.  I'll update 
> the wiki later.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Ryan Schmidt]

On Feb 9, 2016, at 13:30, [ftp83plus]  wrote:
> 
> Ok, after a night of fetching-compiling, it now fails at step 6
> 
> --->  Unable to uninstall llvm-3.4 @3.4.2_8, the following ports depend on it:
> --->  cctools @877.5_2+llvm34
> --->  ld64-136 @136_2+llvm34

I guess there's a missing step between steps 5 and 6 telling you to uninstall 
those +llvm34 versions of cctools and ld64-136. 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Jeremy Huddleston Sequoia]

> On Feb 9, 2016, at 12:12, Ryan Schmidt  wrote:
> 
> On Feb 9, 2016, at 13:30, [ftp83plus]  wrote:
>> 
>> Ok, after a night of fetching-compiling, it now fails at step 6
>> 
>> --->  Unable to uninstall llvm-3.4 @3.4.2_8, the following ports depend on 
>> it:
>> --->  cctools @877.5_2+llvm34
>> --->  ld64-136 @136_2+llvm34
> 
> I guess there's a missing step between steps 5 and 6 telling you to uninstall 
> those +llvm34 versions of cctools and ld64-136. 

Yep.  Just uninstall those at the same time and you'll be fine.  I'll update 
the wiki later.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Ok, after a night of fetching-compiling, it now fails at step 6

--->  Unable to uninstall llvm-3.4 @3.4.2_8, the following ports depend on it:
--->cctools @877.5_2+llvm34
--->ld64-136 @136_2+llvm34
Error: org.macports.uninstall for port llvm-3.4 returned: Please uninstall the 
ports that depend on llvm-3.4 first.
Warning: targets not executed for llvm-3.4: org.macports.uninstall
Please see the log file for port llvm-3.4 for details:

/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_llvm-3.4-3.4.2_8_15b8a350e8ebfedc44efd55b4e7ca47de93e6f1c2d2686c8a60bf0ae8d52a73a-20651/llvm-3.4/main.log
Warning: Failed to execute portfile from registry for llvm-3.4 @3.4.2_8
--->  Unable to uninstall llvm-3.4 @3.4.2_8, the following ports depend on it:
--->cctools @877.5_2+llvm34
--->ld64-136 @136_2+llvm34
Error: port uninstall failed: Please uninstall the ports that depend on 
llvm-3.4 first.

The previous step 5 succeeded, but did it kept the clang-3.4 as well as the 
clang-3.7 variant? 





El 8 févr. 2016, a las 23:01, Jeremy Huddleston Sequoia escribió:

> 
>> On Feb 8, 2016, at 13:35, [ftp83plus]  wrote:
>> 
>> libffi or clang?
> 
> But you already had clang-3.7 installed, so why are you doing that?  I have 
> no idea what the state of your system is here.
> 
> However, since you were seeing an issue building libffi, file a bug against 
> libffi.
> 
> 
>> Don't know for which port to file the ticket. I did:
>> 
>> $ sudo port clean clang-3.7
>> --->  Cleaning clang-3.7
> 
>> Then:
>> $ sudo port -v install clang-3.7
>> --->  Computing dependencies for clang-3.7..
>> --->  Dependencies to be installed: cctools clang-3.4 clang-3.3 clang_select 
>> ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select ncurses zlib xz gettext 
>> expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm python27 bzip2 db48 
>> libedit openssl python2_select python_select sqlite3 libxml2 
>> libunwind-headers libcxx libcxxabi llvm-3.7
>> Error: The following dependencies were not installed: cctools clang-3.4 
>> clang-3.3 clang_select ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select 
>> ncurses zlib xz gettext expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm 
>> python27 bzip2 db48 libedit openssl python2_select python_select sqlite3 
>> libxml2 libunwind-headers libcxx libcxxabi llvm-3.7
>> To report a bug, follow the instructions in the guide:
>>   http://guide.macports.org/#project.tickets
>> Error: Processing of port clang-3.7 failed
> 
> 
> 
>> 
>> 
>> 
>> El 8 févr. 2016, a las 16:18, Jeremy Huddleston Sequoia escribió:
>> 
>>> 
 On Feb 8, 2016, at 12:31, [ftp83plus]  wrote:
 
 Not much success: it now fails to install clang-3.7
>>> 
>>> Oh, are you failing at the point when installing clang-3.7?  How is that 
>>> possible?  Your previous email was about an issue *AFTER* that point.
>>> 
>>> Regardless, it looks like libffi failed to compile for you, so file a 
>>> ticket about that.
>>> 
 
 --->  Cleaning libffi
 --->  Removing work directory for libffi
 Error: The following dependencies were not installed: cctools clang-3.4 
 clang-3.3 clang_select ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select 
 ncurses zlib xz gettext expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm 
 python27 bzip2 db48 libedit openssl python2_select python_select sqlite3 
 libxml2 libunwind-headers libcxx libcxxabi llvm-3.7
 To report a bug, follow the instructions in the guide:
 http://guide.macports.org/#project.tickets
 Error: Processing of port clang-3.7 failed
 
 
 
 
 
 El 8 févr. 2016, a las 12:45, Jeremy Huddleston Sequoia escribió:
 
> 
>> On Feb 8, 2016, at 03:44, Ryan Schmidt  wrote:
>> 
>> On Feb 8, 2016, at 12:07 AM, [ftp83plus]  wrote:
>>> 
>>> Hi, 
>>> 
>>> I assumed that because it is extremely rare not to get an answer from 
>>> either Brandon, Ryan or Adam. I see them having an answer to 
>>> practically every single request on the list…
>> 
>> These are Jeremy's instructions you're following. Maybe he needs to 
>> update them so that this problem is not encountered.
> 
> I updated the guide to include instructions that will get cctools and 
> ld64 rebuilt with the +llvm37 variant before removing llvm-3.4
> 
> sudo port -v upgrade -n -f --enforce-variants cctools -llvm33 -llvm34 
> +llvm37 configure.compiler=macports-clang-3.7
> sudo port -v upgrade -n -f --enforce-variants ld64 -llvm33 -llvm34 
> +llvm37 configure.compiler=macports-clang-3.7
> 
> --Jeremy
 
>>> 
>> 
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-users
> 

___

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Mojca Miklavec]

On 9 February 2016 at 20:30, [ftp83plus]  wrote:
> Ok, after a night of fetching-compiling, it now fails at step 6
>
> --->  Unable to uninstall llvm-3.4 @3.4.2_8, the following ports depend on it:
> --->cctools @877.5_2+llvm34
> --->ld64-136 @136_2+llvm34
> Error: org.macports.uninstall for port llvm-3.4 returned: Please uninstall 
> the ports that depend on llvm-3.4 first.
> Warning: targets not executed for llvm-3.4: org.macports.uninstall
> Please see the log file for port llvm-3.4 for details:
> 
> /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_llvm-3.4-3.4.2_8_15b8a350e8ebfedc44efd55b4e7ca47de93e6f1c2d2686c8a60bf0ae8d52a73a-20651/llvm-3.4/main.log
> Warning: Failed to execute portfile from registry for llvm-3.4 @3.4.2_8
> --->  Unable to uninstall llvm-3.4 @3.4.2_8, the following ports depend on it:
> --->cctools @877.5_2+llvm34
> --->ld64-136 @136_2+llvm34
> Error: port uninstall failed: Please uninstall the ports that depend on 
> llvm-3.4 first.
>
> The previous step 5 succeeded, but did it kept the clang-3.4 as well as the 
> clang-3.7 variant?

If "port installed cctools" shows two ports being installed and only
the one with "+llvm37" active (and the same for ld64), you can do:
sudo port -v uninstall cctools @877.5_2+llvm34
sudo port -v uninstall ld64-136 @136_2+llvm34
sudo port -v uninstall llvm-3.4 clang-3.4

Mojca
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Ryan Schmidt]

On Feb 8, 2016, at 12:07 AM, [ftp83plus]  wrote:
> 
> Hi, 
> 
> I assumed that because it is extremely rare not to get an answer from either 
> Brandon, Ryan or Adam. I see them having an answer to practically every 
> single request on the list…

These are Jeremy's instructions you're following. Maybe he needs to update them 
so that this problem is not encountered.


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Jeremy Huddleston Sequoia]

> On Feb 8, 2016, at 13:35, [ftp83plus]  wrote:
> 
> libffi or clang?

But you already had clang-3.7 installed, so why are you doing that?  I have no 
idea what the state of your system is here.

However, since you were seeing an issue building libffi, file a bug against 
libffi.


> Don't know for which port to file the ticket. I did:
> 
> $ sudo port clean clang-3.7
> --->  Cleaning clang-3.7

> Then:
> $ sudo port -v install clang-3.7
> --->  Computing dependencies for clang-3.7..
> --->  Dependencies to be installed: cctools clang-3.4 clang-3.3 clang_select 
> ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select ncurses zlib xz gettext 
> expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm python27 bzip2 db48 libedit 
> openssl python2_select python_select sqlite3 libxml2 libunwind-headers libcxx 
> libcxxabi llvm-3.7
> Error: The following dependencies were not installed: cctools clang-3.4 
> clang-3.3 clang_select ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select 
> ncurses zlib xz gettext expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm 
> python27 bzip2 db48 libedit openssl python2_select python_select sqlite3 
> libxml2 libunwind-headers libcxx libcxxabi llvm-3.7
> To report a bug, follow the instructions in the guide:
>http://guide.macports.org/#project.tickets
> Error: Processing of port clang-3.7 failed



> 
> 
> 
> El 8 févr. 2016, a las 16:18, Jeremy Huddleston Sequoia escribió:
> 
>> 
>>> On Feb 8, 2016, at 12:31, [ftp83plus]  wrote:
>>> 
>>> Not much success: it now fails to install clang-3.7
>> 
>> Oh, are you failing at the point when installing clang-3.7?  How is that 
>> possible?  Your previous email was about an issue *AFTER* that point.
>> 
>> Regardless, it looks like libffi failed to compile for you, so file a ticket 
>> about that.
>> 
>>> 
>>> --->  Cleaning libffi
>>> --->  Removing work directory for libffi
>>> Error: The following dependencies were not installed: cctools clang-3.4 
>>> clang-3.3 clang_select ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select 
>>> ncurses zlib xz gettext expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm 
>>> python27 bzip2 db48 libedit openssl python2_select python_select sqlite3 
>>> libxml2 libunwind-headers libcxx libcxxabi llvm-3.7
>>> To report a bug, follow the instructions in the guide:
>>>  http://guide.macports.org/#project.tickets
>>> Error: Processing of port clang-3.7 failed
>>> 
>>> 
>>> 
>>> 
>>> 
>>> El 8 févr. 2016, a las 12:45, Jeremy Huddleston Sequoia escribió:
>>> 
 
> On Feb 8, 2016, at 03:44, Ryan Schmidt  wrote:
> 
> On Feb 8, 2016, at 12:07 AM, [ftp83plus]  wrote:
>> 
>> Hi, 
>> 
>> I assumed that because it is extremely rare not to get an answer from 
>> either Brandon, Ryan or Adam. I see them having an answer to practically 
>> every single request on the list…
> 
> These are Jeremy's instructions you're following. Maybe he needs to 
> update them so that this problem is not encountered.
 
 I updated the guide to include instructions that will get cctools and ld64 
 rebuilt with the +llvm37 variant before removing llvm-3.4
 
 sudo port -v upgrade -n -f --enforce-variants cctools -llvm33 -llvm34 
 +llvm37 configure.compiler=macports-clang-3.7
 sudo port -v upgrade -n -f --enforce-variants ld64 -llvm33 -llvm34 +llvm37 
 configure.compiler=macports-clang-3.7
 
 --Jeremy
>>> 
>> 
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users



smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

I just restarted from scratch, uninstalling all traces of MacPorts first, 
although I'd rather avoid it because of the time involved to compile every 
dependency and fan noise.

Let me try once again…



El 8 févr. 2016, a las 23:01, Jeremy Huddleston Sequoia escribió:

> 
>> On Feb 8, 2016, at 13:35, [ftp83plus]  wrote:
>> 
>> libffi or clang?
> 
> But you already had clang-3.7 installed, so why are you doing that?  I have 
> no idea what the state of your system is here.
> 
> However, since you were seeing an issue building libffi, file a bug against 
> libffi.
> 
> 
>> Don't know for which port to file the ticket. I did:
>> 
>> $ sudo port clean clang-3.7
>> --->  Cleaning clang-3.7
> 
>> Then:
>> $ sudo port -v install clang-3.7
>> --->  Computing dependencies for clang-3.7..
>> --->  Dependencies to be installed: cctools clang-3.4 clang-3.3 clang_select 
>> ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select ncurses zlib xz gettext 
>> expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm python27 bzip2 db48 
>> libedit openssl python2_select python_select sqlite3 libxml2 
>> libunwind-headers libcxx libcxxabi llvm-3.7
>> Error: The following dependencies were not installed: cctools clang-3.4 
>> clang-3.3 clang_select ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select 
>> ncurses zlib xz gettext expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm 
>> python27 bzip2 db48 libedit openssl python2_select python_select sqlite3 
>> libxml2 libunwind-headers libcxx libcxxabi llvm-3.7
>> To report a bug, follow the instructions in the guide:
>>   http://guide.macports.org/#project.tickets
>> Error: Processing of port clang-3.7 failed
> 
> 
> 
>> 
>> 
>> 
>> El 8 févr. 2016, a las 16:18, Jeremy Huddleston Sequoia escribió:
>> 
>>> 
 On Feb 8, 2016, at 12:31, [ftp83plus]  wrote:
 
 Not much success: it now fails to install clang-3.7
>>> 
>>> Oh, are you failing at the point when installing clang-3.7?  How is that 
>>> possible?  Your previous email was about an issue *AFTER* that point.
>>> 
>>> Regardless, it looks like libffi failed to compile for you, so file a 
>>> ticket about that.
>>> 
 
 --->  Cleaning libffi
 --->  Removing work directory for libffi
 Error: The following dependencies were not installed: cctools clang-3.4 
 clang-3.3 clang_select ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select 
 ncurses zlib xz gettext expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm 
 python27 bzip2 db48 libedit openssl python2_select python_select sqlite3 
 libxml2 libunwind-headers libcxx libcxxabi llvm-3.7
 To report a bug, follow the instructions in the guide:
 http://guide.macports.org/#project.tickets
 Error: Processing of port clang-3.7 failed
 
 
 
 
 
 El 8 févr. 2016, a las 12:45, Jeremy Huddleston Sequoia escribió:
 
> 
>> On Feb 8, 2016, at 03:44, Ryan Schmidt  wrote:
>> 
>> On Feb 8, 2016, at 12:07 AM, [ftp83plus]  wrote:
>>> 
>>> Hi, 
>>> 
>>> I assumed that because it is extremely rare not to get an answer from 
>>> either Brandon, Ryan or Adam. I see them having an answer to 
>>> practically every single request on the list…
>> 
>> These are Jeremy's instructions you're following. Maybe he needs to 
>> update them so that this problem is not encountered.
> 
> I updated the guide to include instructions that will get cctools and 
> ld64 rebuilt with the +llvm37 variant before removing llvm-3.4
> 
> sudo port -v upgrade -n -f --enforce-variants cctools -llvm33 -llvm34 
> +llvm37 configure.compiler=macports-clang-3.7
> sudo port -v upgrade -n -f --enforce-variants ld64 -llvm33 -llvm34 
> +llvm37 configure.compiler=macports-clang-3.7
> 
> --Jeremy
 
>>> 
>> 
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-users
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Eneko Gotzon]

On Mon, Feb 8, 2016 at 7:07 AM, [ftp83plus]  wrote:

> them having an answer to practically every single request…


It is not fear, I think, to get used to or require them to be the ones who
assume the care responsibility of our issues.

We are a community, I believe.

Just writing.
-- 
Eneko Gotzon Ares
enekogot...@gmail.com
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Brandon Allbery]

On Mon, Feb 8, 2016 at 1:07 AM, [ftp83plus]  wrote:

>
> I assumed that because it is extremely rare not to get an answer from
> either Brandon, Ryan or Adam. I see them having an answer to practically
> every single request on the list…
>

I don't know much about this one, unfortunately.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Jeremy Huddleston Sequoia]

What is the command you are envoking and when?

You should only be rebuilding the cctools and ld64 ports.  There's really no 
reason for all those other ports to be installed.

--Jeremy

> On Feb 8, 2016, at 12:31, [ftp83plus]  wrote:
> 
> Not much success: it now fails to install clang-3.7
> 
> --->  Cleaning libffi
> --->  Removing work directory for libffi
> Error: The following dependencies were not installed: cctools clang-3.4 
> clang-3.3 clang_select ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select 
> ncurses zlib xz gettext expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm 
> python27 bzip2 db48 libedit openssl python2_select python_select sqlite3 
> libxml2 libunwind-headers libcxx libcxxabi llvm-3.7
> To report a bug, follow the instructions in the guide:
>   http://guide.macports.org/#project.tickets
> Error: Processing of port clang-3.7 failed
> 
> 
> 
> 
> 
> El 8 févr. 2016, a las 12:45, Jeremy Huddleston Sequoia escribió:
> 
>> 
>>> On Feb 8, 2016, at 03:44, Ryan Schmidt  wrote:
>>> 
>>> On Feb 8, 2016, at 12:07 AM, [ftp83plus]  wrote:
 
 Hi, 
 
 I assumed that because it is extremely rare not to get an answer from 
 either Brandon, Ryan or Adam. I see them having an answer to practically 
 every single request on the list…
>>> 
>>> These are Jeremy's instructions you're following. Maybe he needs to update 
>>> them so that this problem is not encountered.
>> 
>> I updated the guide to include instructions that will get cctools and ld64 
>> rebuilt with the +llvm37 variant before removing llvm-3.4
>> 
>> sudo port -v upgrade -n -f --enforce-variants cctools -llvm33 -llvm34 
>> +llvm37 configure.compiler=macports-clang-3.7
>> sudo port -v upgrade -n -f --enforce-variants ld64 -llvm33 -llvm34 +llvm37 
>> configure.compiler=macports-clang-3.7
>> 
>> --Jeremy
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users



smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Not much success: it now fails to install clang-3.7

--->  Cleaning libffi
--->  Removing work directory for libffi
Error: The following dependencies were not installed: cctools clang-3.4 
clang-3.3 clang_select ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select 
ncurses zlib xz gettext expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm 
python27 bzip2 db48 libedit openssl python2_select python_select sqlite3 
libxml2 libunwind-headers libcxx libcxxabi llvm-3.7
To report a bug, follow the instructions in the guide:
http://guide.macports.org/#project.tickets
Error: Processing of port clang-3.7 failed





El 8 févr. 2016, a las 12:45, Jeremy Huddleston Sequoia escribió:

> 
>> On Feb 8, 2016, at 03:44, Ryan Schmidt  wrote:
>> 
>> On Feb 8, 2016, at 12:07 AM, [ftp83plus]  wrote:
>>> 
>>> Hi, 
>>> 
>>> I assumed that because it is extremely rare not to get an answer from 
>>> either Brandon, Ryan or Adam. I see them having an answer to practically 
>>> every single request on the list…
>> 
>> These are Jeremy's instructions you're following. Maybe he needs to update 
>> them so that this problem is not encountered.
> 
> I updated the guide to include instructions that will get cctools and ld64 
> rebuilt with the +llvm37 variant before removing llvm-3.4
> 
> sudo port -v upgrade -n -f --enforce-variants cctools -llvm33 -llvm34 +llvm37 
> configure.compiler=macports-clang-3.7
> sudo port -v upgrade -n -f --enforce-variants ld64 -llvm33 -llvm34 +llvm37 
> configure.compiler=macports-clang-3.7
> 
> --Jeremy

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

Apparently these ports are dependencies… Will file a ticket. 


El 8 févr. 2016, a las 16:13, Jeremy Huddleston Sequoia escribió:

> What is the command you are envoking and when?
> 
> You should only be rebuilding the cctools and ld64 ports.  There's really no 
> reason for all those other ports to be installed.
> 
> --Jeremy
> 
>> On Feb 8, 2016, at 12:31, [ftp83plus]  wrote:
>> 
>> Not much success: it now fails to install clang-3.7
>> 
>> --->  Cleaning libffi
>> --->  Removing work directory for libffi
>> Error: The following dependencies were not installed: cctools clang-3.4 
>> clang-3.3 clang_select ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select 
>> ncurses zlib xz gettext expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm 
>> python27 bzip2 db48 libedit openssl python2_select python_select sqlite3 
>> libxml2 libunwind-headers libcxx libcxxabi llvm-3.7
>> To report a bug, follow the instructions in the guide:
>>  http://guide.macports.org/#project.tickets
>> Error: Processing of port clang-3.7 failed
>> 
>> 
>> 
>> 
>> 
>> El 8 févr. 2016, a las 12:45, Jeremy Huddleston Sequoia escribió:
>> 
>>> 
 On Feb 8, 2016, at 03:44, Ryan Schmidt  wrote:
 
 On Feb 8, 2016, at 12:07 AM, [ftp83plus]  wrote:
> 
> Hi, 
> 
> I assumed that because it is extremely rare not to get an answer from 
> either Brandon, Ryan or Adam. I see them having an answer to practically 
> every single request on the list…
 
 These are Jeremy's instructions you're following. Maybe he needs to update 
 them so that this problem is not encountered.
>>> 
>>> I updated the guide to include instructions that will get cctools and ld64 
>>> rebuilt with the +llvm37 variant before removing llvm-3.4
>>> 
>>> sudo port -v upgrade -n -f --enforce-variants cctools -llvm33 -llvm34 
>>> +llvm37 configure.compiler=macports-clang-3.7
>>> sudo port -v upgrade -n -f --enforce-variants ld64 -llvm33 -llvm34 +llvm37 
>>> configure.compiler=macports-clang-3.7
>>> 
>>> --Jeremy
>> 
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-users
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Jeremy Huddleston Sequoia]

> On Feb 8, 2016, at 12:31, [ftp83plus]  wrote:
> 
> Not much success: it now fails to install clang-3.7

Oh, are you failing at the point when installing clang-3.7?  How is that 
possible?  Your previous email was about an issue *AFTER* that point.

Regardless, it looks like libffi failed to compile for you, so file a ticket 
about that.

> 
> --->  Cleaning libffi
> --->  Removing work directory for libffi
> Error: The following dependencies were not installed: cctools clang-3.4 
> clang-3.3 clang_select ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select 
> ncurses zlib xz gettext expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm 
> python27 bzip2 db48 libedit openssl python2_select python_select sqlite3 
> libxml2 libunwind-headers libcxx libcxxabi llvm-3.7
> To report a bug, follow the instructions in the guide:
>http://guide.macports.org/#project.tickets
> Error: Processing of port clang-3.7 failed
> 
> 
> 
> 
> 
> El 8 févr. 2016, a las 12:45, Jeremy Huddleston Sequoia escribió:
> 
>> 
>>> On Feb 8, 2016, at 03:44, Ryan Schmidt  wrote:
>>> 
>>> On Feb 8, 2016, at 12:07 AM, [ftp83plus]  wrote:
 
 Hi, 
 
 I assumed that because it is extremely rare not to get an answer from 
 either Brandon, Ryan or Adam. I see them having an answer to practically 
 every single request on the list…
>>> 
>>> These are Jeremy's instructions you're following. Maybe he needs to update 
>>> them so that this problem is not encountered.
>> 
>> I updated the guide to include instructions that will get cctools and ld64 
>> rebuilt with the +llvm37 variant before removing llvm-3.4
>> 
>> sudo port -v upgrade -n -f --enforce-variants cctools -llvm33 -llvm34 
>> +llvm37 configure.compiler=macports-clang-3.7
>> sudo port -v upgrade -n -f --enforce-variants ld64 -llvm33 -llvm34 +llvm37 
>> configure.compiler=macports-clang-3.7
>> 
>> --Jeremy
> 



smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[[ftp83plus]]

libffi or clang?

Don't know for which port to file the ticket. I did:

$ sudo port clean clang-3.7
--->  Cleaning clang-3.7

Then:
$ sudo port -v install clang-3.7
--->  Computing dependencies for clang-3.7..
--->  Dependencies to be installed: cctools clang-3.4 clang-3.3 clang_select 
ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select ncurses zlib xz gettext 
expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm python27 bzip2 db48 libedit 
openssl python2_select python_select sqlite3 libxml2 libunwind-headers libcxx 
libcxxabi llvm-3.7
Error: The following dependencies were not installed: cctools clang-3.4 
clang-3.3 clang_select ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select 
ncurses zlib xz gettext expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm 
python27 bzip2 db48 libedit openssl python2_select python_select sqlite3 
libxml2 libunwind-headers libcxx libcxxabi llvm-3.7
To report a bug, follow the instructions in the guide:
http://guide.macports.org/#project.tickets
Error: Processing of port clang-3.7 failed



El 8 févr. 2016, a las 16:18, Jeremy Huddleston Sequoia escribió:

> 
>> On Feb 8, 2016, at 12:31, [ftp83plus]  wrote:
>> 
>> Not much success: it now fails to install clang-3.7
> 
> Oh, are you failing at the point when installing clang-3.7?  How is that 
> possible?  Your previous email was about an issue *AFTER* that point.
> 
> Regardless, it looks like libffi failed to compile for you, so file a ticket 
> about that.
> 
>> 
>> --->  Cleaning libffi
>> --->  Removing work directory for libffi
>> Error: The following dependencies were not installed: cctools clang-3.4 
>> clang-3.3 clang_select ld64 ld64-136 libmacho-headers llvm-3.4 llvm_select 
>> ncurses zlib xz gettext expat libiconv gperf llvm-3.3 perl5 perl5.22 gdbm 
>> python27 bzip2 db48 libedit openssl python2_select python_select sqlite3 
>> libxml2 libunwind-headers libcxx libcxxabi llvm-3.7
>> To report a bug, follow the instructions in the guide:
>>   http://guide.macports.org/#project.tickets
>> Error: Processing of port clang-3.7 failed
>> 
>> 
>> 
>> 
>> 
>> El 8 févr. 2016, a las 12:45, Jeremy Huddleston Sequoia escribió:
>> 
>>> 
 On Feb 8, 2016, at 03:44, Ryan Schmidt  wrote:
 
 On Feb 8, 2016, at 12:07 AM, [ftp83plus]  wrote:
> 
> Hi, 
> 
> I assumed that because it is extremely rare not to get an answer from 
> either Brandon, Ryan or Adam. I see them having an answer to practically 
> every single request on the list…
 
 These are Jeremy's instructions you're following. Maybe he needs to update 
 them so that this problem is not encountered.
>>> 
>>> I updated the guide to include instructions that will get cctools and ld64 
>>> rebuilt with the +llvm37 variant before removing llvm-3.4
>>> 
>>> sudo port -v upgrade -n -f --enforce-variants cctools -llvm33 -llvm34 
>>> +llvm37 configure.compiler=macports-clang-3.7
>>> sudo port -v upgrade -n -f --enforce-variants ld64 -llvm33 -llvm34 +llvm37 
>>> configure.compiler=macports-clang-3.7
>>> 
>>> --Jeremy
>> 
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Jeremy Huddleston Sequoia]

> On Feb 8, 2016, at 03:44, Ryan Schmidt  wrote:
> 
> On Feb 8, 2016, at 12:07 AM, [ftp83plus]  wrote:
>> 
>> Hi, 
>> 
>> I assumed that because it is extremely rare not to get an answer from either 
>> Brandon, Ryan or Adam. I see them having an answer to practically every 
>> single request on the list…
> 
> These are Jeremy's instructions you're following. Maybe he needs to update 
> them so that this problem is not encountered.

I updated the guide to include instructions that will get cctools and ld64 
rebuilt with the +llvm37 variant before removing llvm-3.4

sudo port -v upgrade -n -f --enforce-variants cctools -llvm33 -llvm34 +llvm37 
configure.compiler=macports-clang-3.7
sudo port -v upgrade -n -f --enforce-variants ld64 -llvm33 -llvm34 +llvm37 
configure.compiler=macports-clang-3.7

--Jeremy

smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Eneko Gotzon]

On Sun, Feb 7, 2016 at 1:05 AM, [ftp83plus]  wrote:

> excuse me for double-post…
>

Your first message was received, but being me just an unskilled user I have
not dared to answer.

sudo port -v uninstall llvm-3.4 clang-3.4
> I get
> Warning: Failed to execute portfile from registry for llvm-3.4 @3.4.2_8
> --->  Unable to uninstall llvm-3.4 @3.4.2_8, the following ports depend on
> it:
> --->cctools @877.5_1+llvm34
> --->ld64-136 @136_2+llvm34
>

Because ld64-136 and cctools depend on llvm-3.4 MacPorts does not uninstall
llvm-3.4 to avoid the two dependent ports become "disconnected" and
therefore not functional.

You can force to uninstall llvm-3.4 but ld64-136 and cctools will be
"disconnected".

I think you also can deactivate ld64-136 and cctools and, subsequently,
uninstall llvm-3.4, but ld64-136 and cctools will be "disconnected".

These are just very basic explanations intended to help you understand what
is happening. Excuse me if they are obvious.

I hope you get a better help, as usually in this (wonderful) list.
-- 
Eneko Gotzon Ares
enekogot...@gmail.com
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Trying to execute LibcxxOnOlderSytems

[[ftp83plus]]

Hello there, 

I am trying to execute the instructions on this page 
https://trac.macports.org/wiki/LibcxxOnOlderSystems, but am stuck at step 4 of 
Bootstrapping 3:
On instruction 
sudo port -v uninstall llvm-3.4 clang-3.4
I get 

Warning: Failed to execute portfile from registry for llvm-3.4 @3.4.2_8
--->  Unable to uninstall llvm-3.4 @3.4.2_8, the following ports depend on it:
--->cctools @877.5_1+llvm34
--->ld64-136 @136_2+llvm34

Not sure I understand the logic fault here…

P
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users