cctools fails to install on my 10.7.5

[Franco Vaccari]

I wanted to make a fresh installation of MacPorts on a iMac running 10.7.5. 
What I did:

- removed old MacPorts as per guide instructions
- removed old Xcode.app from Applications
- installed Xcode 4.6.3 and the command line tools
- agreed to sudo xcodebuild -licence 
- sudo xcode-select -switch /Applications/Xcode.app
- installed MacPorts 2.6.2
- started installing my usual suite of packages

Successfully installed mpstats as first package, and then others. Failure 
happened along the process when trying to install cctools (log attached). 

Is there something wrong with my configuration? If it looks ok, I’ll go on and 
file a ticket for this.

xcodebuild -version:
Xcode 4.6.3
Build version 4H1503

sudo port
Password:
MacPorts 2.6.2
Entering shell mode... ("help" for help, "quit" to quit)
[...]> install cctools
--->  Computing dependencies for cctools
--->  Fetching archive for cctools
--->  Attempting to fetch cctools-927.0.2_1+llvm34.darwin_11.x86_64.tbz2 from 
http://fco.it.packages.macports.org/mirrors/macports-packages/cctools
--->  Attempting to fetch cctools-927.0.2_1+llvm34.darwin_11.x86_64.tbz2 from 
http://lil.fr.packages.macports.org/cctools
--->  Attempting to fetch cctools-927.0.2_1+llvm34.darwin_11.x86_64.tbz2 from 
http://nue.de.packages.macports.org/cctools
--->  Building cctools
Error: Failed to build cctools: command execution failed

Thanks for any suggestion you may have

Franco



cctools.log.gz
Description: GNU Zip compressed data

Re: cctools fails to install on my 10.7.5

[Franco Vaccari]

Adding to my previous post

sudo port install cctools +xcode 

properly installed cctools. Is this expected, and should be the default variant 
on 10.7.5?

Thanks

Franco

> On 26 Feb 2020, at 11:29, Franco Vaccari  wrote:
> 
> I wanted to make a fresh installation of MacPorts on a iMac running 10.7.5. 
> What I did:
> 
> - removed old MacPorts as per guide instructions
> - removed old Xcode.app from Applications
> - installed Xcode 4.6.3 and the command line tools
> - agreed to sudo xcodebuild -licence 
> - sudo xcode-select -switch /Applications/Xcode.app
> - installed MacPorts 2.6.2
> - started installing my usual suite of packages
> 
> Successfully installed mpstats as first package, and then others. Failure 
> happened along the process when trying to install cctools (log attached). 
> 
> Is there something wrong with my configuration? If it looks ok, I’ll go on 
> and file a ticket for this.
> 
> xcodebuild -version:
> Xcode 4.6.3
> Build version 4H1503
> 
> sudo port
> Password:
> MacPorts 2.6.2
> Entering shell mode... ("help" for help, "quit" to quit)
> [...]> install cctools
> --->  Computing dependencies for cctools
> --->  Fetching archive for cctools
> --->  Attempting to fetch cctools-927.0.2_1+llvm34.darwin_11.x86_64.tbz2 from 
> http://fco.it.packages.macports.org/mirrors/macports-packages/cctools
> --->  Attempting to fetch cctools-927.0.2_1+llvm34.darwin_11.x86_64.tbz2 from 
> http://lil.fr.packages.macports.org/cctools
> --->  Attempting to fetch cctools-927.0.2_1+llvm34.darwin_11.x86_64.tbz2 from 
> http://nue.de.packages.macports.org/cctools
> --->  Building cctools
> Error: Failed to build cctools: command execution failed
> 
> Thanks for any suggestion you may have
> 
> Franco
> 
> 
> 

Uninstall instructions in documentation

[S. L. Garwood via macports-users]

The documentation at https://guide.macports.org  
has incorrect information for uninstalling MacPorts under Catalina (MacOS 
10.15.3).
- the ‘dscl' commands to remove the macports user and group does not work.
- the whole string of ‘rm’ commands doesn’t work.

To whom should I report this?

Re: cctools fails to install on my 10.7.5

[Ken Cunningham]

Please confirm:

$ echo "macOS $(sw_vers -productVersion) $(sw_vers -buildVersion)"; echo 
"Xcode $(xcodebuild -version | awk -v ORS=' ' '{print $NF}')"

macOS 10.7.5 11G63
Xcode 4.6.3 4H1503 


(I know your Xcode has the correct signature.)

Re: cctools fails to install on my 10.7.5

[Franco Vaccari]

Here it is:

macOS 10.7.5 11G63b
Xcode 4.6.3 4H1503 

The only difference is the trailing “b” in macOS. I don’t know its meaning, for 
sure it’s not “b for beta”, as I’ve never played with beta systems.



> On 26 Feb 2020, at 19:48, Ken Cunningham  
> wrote:
> 
> Please confirm:
> 
> $ echo "macOS $(sw_vers -productVersion) $(sw_vers -buildVersion)"; echo 
> "Xcode $(xcodebuild -version | awk -v ORS=' ' '{print $NF}')"
> 
> macOS 10.7.5 11G63
> Xcode 4.6.3 4H1503 
> 
> 
> (I know your Xcode has the correct signature.)

Re: cctools fails to install on my 10.7.5

[Ken Cunningham]

> Here it is:
> 
> macOS 10.7.5 11G63b
> Xcode 4.6.3 4H1503 
> 
> The only difference is the trailing “b” in macOS. I don’t know its meaning, 
> for sure it’s not “b for beta”, as I’ve never played with beta systems.
> 
> 

I'm not sure about the "b", but the issue seems to be you can't build anything 
with c++ it appears, even though our build lines are identical:


You:

/usr/bin/clang++ -Os -stdlib=libc++  -arch x86_64 
-I/opt/local/libexec/llvm-3.4/include  -DNDEBUG -D_GNU_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -O3  -g 
-fno-common  -I/opt/local/include 
-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/cctools-927.0.2/../ld64-450.3/src/abstraction
 
-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/cctools-927.0.2/../ld64-450.3/src/other
 
-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/cctools-927.0.2/include
 -stdlib=libc++ -c -o \
:info:build ./PruneTrie.o ./PruneTrie.cpp
:info:build In file included from ./PruneTrie.cpp:24:
:info:build In file included from /usr/bin/../lib/c++/v1/vector:261:
:info:build In file included from /usr/bin/../lib/c++/v1/__bit_reference:15:
:info:build In file included from /usr/bin/../lib/c++/v1/algorithm:591:
:info:build /usr/bin/../lib/c++/v1/type_traits:165:12: error: unknown type name 
'_LIBCPP_CONSTEXPR'
:info:build static _LIBCPP_CONSTEXPR const _Tp  value = __v;


Me:
/usr/bin/clang++ -Os -stdlib=libc++  -arch x86_64 
-I/opt/local/libexec/llvm-3.4/include  -DNDEBUG -D_GNU_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -O3  -g 
-fno-common  -I/opt/local/include 
-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/cctools-927.0.2/../ld64-450.3/src/abstraction
 
-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/cctools-927.0.2/../ld64-450.3/src/other
 
-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/cctools-927.0.2/include
 -stdlib=libc++ -c -o \
./PruneTrie.o ./PruneTrie.cpp



Please try building a very simple c++ "hello, world" program with 

/usr/bin/clang++ -stdlib=libc++ 

and see if your c++ compiler is working at all --- 

If not, there's your issue --- and you'd need to reinstall something. We can't 
do much if your /usr/bin/clang++ is broken.

If it works -- well then I don't know just yet -- we'd have to see...

Ken

Re: cctools fails to install on my 10.7.5

[Franco Vaccari]

A little digging around and the “b” was associated to a supplemental update, 
and that shouldn’t matter much here.

And definitely I can’t compile anything there. I’m afraid Xcode update was not 
as smooth as it should have been. Will look how to clean that...

/usr/bin/clang++ -stdlib=libc++ hello.cpp
In file included from hello.cpp:1:
In file included from /usr/bin/../lib/c++/v1/iostream:38:
In file included from /usr/bin/../lib/c++/v1/ios:216:
In file included from /usr/bin/../lib/c++/v1/__locale:15:
In file included from /usr/bin/../lib/c++/v1/string:434:
In file included from /usr/bin/../lib/c++/v1/algorithm:591:
/usr/bin/../lib/c++/v1/type_traits:165:12: error: unknown type name 
'_LIBCPP_CONSTEXPR'
static _LIBCPP_CONSTEXPR const _Tp  value = __v;
   ^
/usr/bin/../lib/c++/v1/type_traits:165:30: error: expected member name or ';' 
after
  declaration specifiers
static _LIBCPP_CONSTEXPR const _Tp  value = __v;
 ^
/usr/bin/../lib/c++/v1/type_traits:169:9: error: unknown type name 
'_LIBCPP_CONSTEXPR'
_LIBCPP_CONSTEXPR operator value_type() const {return value;}
^
/usr/bin/../lib/c++/v1/type_traits:169:63: error: use of undeclared identifier 
'value'
_LIBCPP_CONSTEXPR operator value_type() const {return value;}
  ^
/usr/bin/../lib/c++/v1/type_traits:173:1: error: unknown type name 
'_LIBCPP_CONSTEXPR'
_LIBCPP_CONSTEXPR const _Tp integral_constant<_Tp, __v>::value;
^
/usr/bin/../lib/c++/v1/type_traits:173:19: error: expected unqualified-id
_LIBCPP_CONSTEXPR const _Tp integral_constant<_Tp, __v>::value;
  ^
/usr/bin/../lib/c++/v1/type_traits:730:2: error: is_base_of not implemented.
#error is_base_of not implemented.
 ^
/usr/bin/../lib/c++/v1/type_traits:400:56: error: no member named 'value' in
  'std::__1::is_integral'
: public integral_constant::value  ||
 ~~^
/usr/bin/../lib/c++/v1/type_traits:941:19: note: in instantiation of template 
class
  'std::__1::is_arithmetic' requested here
 (is_arithmetic<_A2>::value || is_void<_A2>::value) &&
  ^
/usr/bin/../lib/c++/v1/type_traits:949:22: note: in instantiation of default 
argument for
  '__promote' required here
typedef typename __promote<_A1>::type __type1;
 ^~
/usr/bin/../lib/c++/v1/type_traits:949:38: error: expected a qualified name 
after 'typename'
typedef typename __promote<_A1>::type __type1;
 ^
/usr/bin/../lib/c++/v1/type_traits:949:42: error: expected ';' at end of 
declaration list
typedef typename __promote<_A1>::type __type1;
 ^
/usr/bin/../lib/c++/v1/type_traits:941:39: error: no member named 'value' in
  'std::__1::is_arithmetic'
 (is_arithmetic<_A2>::value || is_void<_A2>::value) &&
  ^
/usr/bin/../lib/c++/v1/type_traits:950:22: note: in instantiation of default 
argument for
  '__promote' required here
typedef typename __promote<_A2>::type __type2;
 ^~
/usr/bin/../lib/c++/v1/type_traits:950:38: error: expected a qualified name 
after 'typename'
typedef typename __promote<_A2>::type __type2;
 ^
/usr/bin/../lib/c++/v1/type_traits:950:42: error: expected ';' at end of 
declaration list
typedef typename __promote<_A2>::type __type2;
 ^
/usr/bin/../lib/c++/v1/type_traits:941:39: error: no member named 'value' in
  'std::__1::is_arithmetic'
 (is_arithmetic<_A2>::value || is_void<_A2>::value) &&
  ^
/usr/bin/../lib/c++/v1/type_traits:951:38: error: expected a qualified name 
after 'typename'
typedef typename __promote<_A3>::type __type3;
 ^
/usr/bin/../lib/c++/v1/type_traits:951:42: error: expected ';' at end of 
declaration list
typedef typename __promote<_A3>::type __type3;
 ^
/usr/bin/../lib/c++/v1/type_traits:953:22: error: use of undeclared identifier 
'__type1'
typedef decltype(__type1() + __type2() + __type3()) type;
 ^
/usr/bin/../lib/c++/v1/__config:291:32: note: expanded from macro 'decltype'
#define decltype(x) __typeof__(x)
   ^
In file included from hello.cpp:1:
In file included from /usr/bin/../lib/c++/v1/iostream:38:
In file included from /usr/bin/../lib/c++/v1/ios:216:
In file included from /usr/bin/../lib/c++/v1/__locale:15:
In file included from /usr/bin/../lib/c++/v1/string:434:
In file included from /usr/bin/../lib/c++/v1/algorithm:591:
/usr/bin/../lib/c++/v1/type_traits:953:34: error: use of undeclared identifier 
'__type2'
typedef decltype(__type1() + __type2() + __type3()) type;
  

Re: cctools fails to install on my 10.7.5

[Franco Vaccari]

I’ve reinstalled the latest Command Line Tools released for Lion and clang++ is 
now 

Apple clang version 4.1 (tags/Apple/clang-421.11.66) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin11.4.2
Thread model: posix

while before it was

Apple clang version 4.0 (tags/Apple/clang-421.0.60) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin11.4.2
Thread model: posix

and cctools finally installs properly

So problem solved and sorry for the noise…

Thanks Ken for the hint!

Franco

> On 26 Feb 2020, at 22:33, Franco Vaccari  wrote:
> 
> A little digging around and the “b” was associated to a supplemental update, 
> and that shouldn’t matter much here.
> 
> And definitely I can’t compile anything there. I’m afraid Xcode update was 
> not as smooth as it should have been. Will look how to clean that…
> 
> 
> 20 errors generated.
> 
> 
>> On 26 Feb 2020, at 22:03, Ken Cunningham  
>> wrote:
>> 
>>> Here it is:
>>> 
>>> macOS 10.7.5 11G63b
>>> Xcode 4.6.3 4H1503 
>>> 
>>> The only difference is the trailing “b” in macOS. I don’t know its meaning, 
>>> for sure it’s not “b for beta”, as I’ve never played with beta systems.
>>> 
>>> 
>> 
>> I'm not sure about the "b", but the issue seems to be you can't build 
>> anything with c++ it appears, even though our build lines are identical:
>> 
>> 
>> You:
>> 
>> /usr/bin/clang++ -Os -stdlib=libc++  -arch x86_64 
>> -I/opt/local/libexec/llvm-3.4/include  -DNDEBUG -D_GNU_SOURCE 
>> -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -O3  
>> -g -fno-common  -I/opt/local/include 
>> -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/cctools-927.0.2/../ld64-450.3/src/abstraction
>>  
>> -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/cctools-927.0.2/../ld64-450.3/src/other
>>  
>> -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/cctools-927.0.2/include
>>  -stdlib=libc++ -c -o \
>> :info:build  ./PruneTrie.o ./PruneTrie.cpp
>> :info:build In file included from ./PruneTrie.cpp:24:
>> :info:build In file included from /usr/bin/../lib/c++/v1/vector:261:
>> :info:build In file included from /usr/bin/../lib/c++/v1/__bit_reference:15:
>> :info:build In file included from /usr/bin/../lib/c++/v1/algorithm:591:
>> :info:build /usr/bin/../lib/c++/v1/type_traits:165:12: error: unknown type 
>> name '_LIBCPP_CONSTEXPR'
>> :info:build static _LIBCPP_CONSTEXPR const _Tp  value = __v;
>> 
>> 
>> Me:
>> /usr/bin/clang++ -Os -stdlib=libc++  -arch x86_64 
>> -I/opt/local/libexec/llvm-3.4/include  -DNDEBUG -D_GNU_SOURCE 
>> -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -O3  
>> -g -fno-common  -I/opt/local/include 
>> -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/cctools-927.0.2/../ld64-450.3/src/abstraction
>>  
>> -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/cctools-927.0.2/../ld64-450.3/src/other
>>  
>> -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/cctools-927.0.2/include
>>  -stdlib=libc++ -c -o \
>>  ./PruneTrie.o ./PruneTrie.cpp
>> 
>> 
>> 
>> Please try building a very simple c++ "hello, world" program with 
>> 
>> /usr/bin/clang++ -stdlib=libc++ 
>> 
>> and see if your c++ compiler is working at all --- 
>> 
>> If not, there's your issue --- and you'd need to reinstall something. We 
>> can't do much if your /usr/bin/clang++ is broken.
>> 
>> If it works -- well then I don't know just yet -- we'd have to see...
>> 
>> Ken
> 

Problem with uninstall instructions

[kkh2]

I am using the uninstall instructions given here:

https://guide.macports.org/chunked/installing.macports.uninstalling.html

I got as far as this command:

$ dscl -p . -delete /Users/macports


After I typed in my password, it responded:

Data source (.) is not valid.

I am using macOS 10.13.6 (my hardware allows no higher version, and my
finances allow no higher hardware).

What should I do?

Thank you.

K

Re: Problem with uninstall instructions

[Dave Horsfall]

On Wed, 26 Feb 2020, k...@cornell.edu wrote:

[...]


  $ dscl -p . -delete /Users/macports


Just a quick side-track: is there a pointer somewhere to these obscure 
commands?  It seems that I come across a new one with each new thread on 
this list...


[...]


I am using macOS 10.13.6 (my hardware allows no higher version, and my
finances allow no higher hardware).


Me too, stuck on Sierra on an early Pro :-(  High Sierra *may* work, 
though...


-- Dave

Re: Problem with uninstall instructions

[Bill Cole]

On 26 Feb 2020, at 19:54, Dave Horsfall wrote:

Just a quick side-track: is there a pointer somewhere to these obscure 
commands?  It seems that I come across a new one with each new thread 
on this list...


Well, which "obscure" commands are you looking for? 'man dscl' will give 
you extensive instructions for dscl, and hitting tab a couple of times 
at a shell prompt will offer to show you a list of a few thousand 
available commands, assuming your shell has completion active and 
configured normally.


--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not For Hire (currently)

Re: opensp fails to build ==> fix

[Ken Cunningham]

> On Feb 25, 2020, at 9:35 AM, Uli Wienands  wrote:
> 
> So trying opensp using clang 5 did work. In fact, it just pulled the binary 
> that I guess Josh made; so thanks for that.
> 
> But not all is well; resuming the rev-upgrade I now get stuck at boost. It is 
> actually mentioned on the port page that it fails on 10.6. Per the log it 
> seems to fail near the end running something called b2. I tried clang 5 again 
> but no luck this time (probably to be expected since the compiles didn't seem 
> to generate any complaints).
> 
> Anyway; attached is the log.
> 
> With many thanks,
> 
> Uli

The error in the log shows this:

:info:build Undefined symbols for architecture x86_64:
:info:build   "___cxa_thread_atexit", referenced from:
:info:build   boost::context::detail::ecv1_activation_record::current() in 
execution_context.o
:info:build   
boost::context::detail::ecv1_activation_record_initializer::ecv1_activation_record_initializer()
 in execution_context.o
:info:build   
boost::context::detail::ecv1_activation_record_initializer::ecv1_activation_record_initializer()
 in execution_context.o
:info:build   
boost::context::detail::ecv1_activation_record_initializer::~ecv1_activation_record_initializer()
 in execution_context.o
:info:build   
boost::context::detail::ecv1_activation_record_initializer::~ecv1_activation_record_initializer()
 in execution_context.o
:info:build   boost::context::v1::execution_context::current() in 
execution_context.o
:info:build ld: symbol(s) not found for architecture x86_64


If I’m right, you’ve been caught by the libcxx bootstrapping issue I have yet 
to fix.

Once you have 10.6.8 with libcxx installed, and then any version of clang >= 
5.0, do this:


sudo port -v -n upgrade --enforce-variants libcxx +emulated_tls

and you should be good to go thereafter.

I have to either fix this somehow, put in in the port notes, or otherwise find 
a way to automate this step…

Ken