Opened 8 days ago

Closed 7 days ago

Last modified 7 days ago

#71214 closed defect (duplicate)

Sequoia 15.1 db48 port install error

Reported by: sandiway Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port:

Description

Upgraded to Sequoia 15.1 on m3 MacBook Pro. Did the

sudo rm -rf /Library/Developer/CommandLineTools

And installed

Command_Line_Tools_for_Xcode_16.1.dmg

when db62 threw the CPP header error:

:info:build In file included from ../lang/cxx/cxx_channel.cpp:13: :info:build ./db_cxx.h:59:10: fatal error: 'iostream.h' file not found :info:build 59 | #include <iostream.h> :info:build | ~ :info:build 1 error generated.

Deleted everything (all ports) and started again from scratch.

port install swi-prolog gets past db62 and a lot of other ports installed fine.

However, somehow db48 is also required. And that fails.

---> Building db48 Error: Failed to build db48: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_db48/db48/main.log for details.

:info:build libtool: compile: /usr/bin/clang++ -stdlib=libc++ -c -I. -I../dist/.. -I/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX15.sdk -pipe -Os -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX15.sdk -arch arm64 ../dist/../cxx/cxx_mpool.cpp -fno-common -DPIC -o .libs/cxx_mpool.o :info:build In file included from ../dist/../cxx/cxx_mpool.cpp:13: :info:build ./db_cxx.h:59:10: fatal error: 'iostream.h' file not found :info:build 59 | #include <iostream.h> :info:build | ~

This seems like the same error with iostream.h

db62 got past it but not db48.

BTW, port installed reports lots of ports did succeed.

The following ports are currently installed:

autoconf @2.72_0 (active) automake @1.17_0 (active) bison @3.8.2_2 (active) bison-runtime @3.8.2_0 (active) brotli @1.1.0_0 (active) bzip2 @1.0.8_0 (active) cmake @3.29.5_0 (active) cmake-bootstrap @3.9.6_0 (active) curl @8.10.1_1+brotli+http2+idn+psl+ssl+zstd (active) curl-ca-bundle @8.10.1_0 (active) db62 @6.2.32_0+sql (active) expat @2.6.3_0 (active) gettext @0.22.5_0 (active) gettext-runtime @0.22.5_0 (active) gettext-tools-libs @0.22.5_0 (active) gmp @6.3.0_0 (active) gperf @3.1_0 (active) gperftools @2.15_0 (active) icu @74.2_0 (active) libarchive @3.7.6_0 (active) libb2 @0.98.1_1 (active) libcxx @5.0.1_5 (active) libedit @20240808-3.1_0 (active) libffi @3.4.6_1 (active) libiconv @1.17_0 (active) libidn2 @2.3.7_0 (active) libjpeg-turbo @3.0.4_0 (active) libmcrypt @2.5.8_2 (active) libpsl @0.21.5-20240306_0 (active) libtextstyle @0.22.5_0 (active) libtool @2.5.3_0 (active) libunistring @1.2_0 (active) libxml2 @2.13.4_0 (active) libyaml @0.2.5_0 (active) lz4 @1.10.0_0 (active) lzo2 @2.10_0 (active) m4 @1.4.19_1 (active) ncurses @6.5_0 (active) nghttp2 @1.64.0_0 (active) openssl @3_21 (active) openssl3 @3.4.0_0 (active) pcre2 @10.44_0 (active) pkgconfig @0.29.2_0 (active) python3_select @0.1_0 (active) python3_select-310 @0.1_1 (active) python310 @3.10.15_0+lto+optimizations (active) python_select @0.3_10 (active) python_select-310 @0.3_1 (active) re2c @3.1_0 (active) readline @8.2.013_0 (active) sqlite3 @3.47.0_0 (active) xz @5.6.3_0 (active) zlib @1.3.1_0 (active) zstd @1.5.6_0 (active)

Change History (6)

comment:1 Changed 7 days ago by jmroot (Joshua Root)

Resolution: duplicate
Status: newclosed

comment:2 in reply to:  1 Changed 7 days ago by sandiway

Replying to jmroot:

#70750 ProblemHotlist#clts16

Did you read what I wrote previously? I did clean out the CLTS, and this directory no longer exists.

(base) ~$ cd /Library/Developer/CommandLineTools/usr/include/

(base) include$ ls

FlexLexer.h module.modulemap swift

I installed the .dmg CLTS from Apple Developer as instructed. I even killed Macports and restarted from scratch installing ports. So how is this a duplicate problem (although it looks like it)? Please help me understand.

(base) ~$ xcode-select -print-path /Applications/Xcode.app/Contents/Developer

Last edited 7 days ago by sandiway (previous) (diff)

comment:3 Changed 7 days ago by jmroot (Joshua Root)

Looks like you may have forgotten to run sudo port clean db48?

comment:4 Changed 7 days ago by sandiway

Appreciate for the fast response. Sorry. My bad.

But I didn't have db48 installed! - as I nuked all the installs earlier using:

sudo port -fp uninstall installed

But somehow it goes through now. Don't quite understand why given I ran uninstall installed

But thanks!

$ sudo port clean db48 ---> Cleaning db48

(base) ~$ sudo port install db48 ---> Fetching archive for db48 ---> Attempting to fetch db48-4.8.30_5.darwin_24.arm64.tbz2 from https://packages.macports.org/db48 ---> Attempting to fetch db48-4.8.30_5.darwin_24.arm64.tbz2 from http://mirror.fcix.net/macports/packages/db48 ---> Attempting to fetch db48-4.8.30_5.darwin_24.arm64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/db48 ---> Fetching distfiles for db48 ---> Verifying checksums for db48 ---> Extracting db48 ---> Applying patches to db48 ---> Configuring db48 ---> Building db48 ---> Staging db48 into destroot ---> Installing db48 @4.8.30_5 ---> Activating db48 @4.8.30_5 ---> Cleaning db48 ---> Updating database of binaries ---> Scanning binaries for linking errors ---> No broken files found. ---> No broken ports found. ---> Some of the ports you installed have notes:

db48 has the following notes:

The Java and Tcl bindings are now provided by the db48-java and db48-tcl subports.

Last edited 7 days ago by sandiway (previous) (diff)

comment:5 Changed 7 days ago by jmroot (Joshua Root)

port clean removes the build directory, while port uninstall only removes the installed files that are the end result of the build. If you have a partially completed build that was started with a broken toolchain, it is likely to fail again if you try to continue it. Several people in #70750 reported that the fix for the CLTs didn't work, but it turned out that they hadn't cleaned the failing ports after applying the fix.

comment:6 Changed 7 days ago by sandiway

I see now. Again, thank you!

Note: See TracTickets for help on using tickets.