libiodbc @3.52.12 +x11: error: use of undeclared identifier 'liburl'

[danielta]

The buildbot successfully built +x11 archive, but it actually lacks any GTK components.

Hi, upgrading the outdated ports, it stops at libiodbc with several errors. the first is:

:info:build drvconn.c:501:7: error: use of undeclared identifier 'liburl'

followed by other undeclared symbols. Please see attached log.

cheers

[danielta]

main.log

[ryandesign (Ryan Carsten Schmidt)]

Agreed, libiodbc 3.52.12 fails to build for me too on El Capitan.

[nerdling (Jeremy Lavergne)]

I need a full build log: this installs fine for me locally, and the build bot hasn't caught up to provide any missing pieces.

[nerdling (Jeremy Lavergne)]

succcessful build and install

[nerdling (Jeremy Lavergne)]

Buildbot just confirmed: successful build on El Capitan. Now I definitely need clean build/complete logs from either of you :-)

​https://build.macports.org/builders/buildports-elcapitan-x86_64/builds/2654/steps/compile/logs/progress

[danielta]

clean_main.log

[danielta]

I've run

port clean  libiodbc
port install  libiodbc

the problem is still there. there is also a broken link in download:

:msg:archivefetch --->  Attempting to fetch libiodbc-3.52.12_0+x11.darwin_15.x86_64.tbz2 from https://packages.macports.org/libiodbc
:debug:archivefetch Fetching archive failed:: The requested URL returned error: 404 Not Found

see complete log attached. I'm running on El Captain 10.11.6.

any idea? thanks for you time. cheers d

Replying to snc@…:

Buildbot just confirmed: successful build on El Capitan. Now I definitely need clean build/complete logs from either of you :-)

​https://build.macports.org/builders/buildports-elcapitan-x86_64/builds/2654/steps/compile/logs/progress

[nerdling (Jeremy Lavergne)]

The broken link during archivefetch is MacPorts looking for a pre-built archive. It should become available once the buildbot is finished (which has occurred, so it has become a workaround on the next clean run of sudo port install libiodbc).

It looks like the difference between the build logs is GTK. The buildbot didn't actually build any GTK code; so another workaround is to build with the variant disabled sudo port install libiodbc -x11.

Notice the side effect of the buildbot: the archive claims +x11 but it actually built as if -x11.

[nerdling (Jeremy Lavergne)]

Has duplicate #51946.

[hapaguy (Brian Kurt Fujikawa)]

Cc Me!

[persramd@…]

Cc Me!

[petrov@…]

Cc Me!

[mojca (Mojca Miklavec)]

Cc Me!

[udbraumann]

Cc Me!

[neo954 (Gᴏɴɢ Jie)]

Cc Me!

[kencu (Ken)]

I just had to install this using sudo port install libiodbc -x11 to get it to build with clang-3.9 on 10.6.8 / libc++ as well. Otherwise there were screenfulls of errors similar to 55002

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #55002.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #59471.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #59687.

[Liontooth (David Liontooth)]

Just confirming this works:

sudo port install -t libiodbc

as suggested by nerdling, the maintainer. It's very slow, but doesn't complain:

$ sudo port install -t libiodbc
--->  Computing dependencies for libiodbc
--->  Fetching archive for libiodbc
--->  Attempting to fetch libiodbc-3.52.14_2+libodbc+x11.darwin_19.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/libiodbc
--->  Attempting to fetch libiodbc-3.52.14_2+libodbc+x11.darwin_19.x86_64.tbz2 from https://cph.dk.packages.macports.org/libiodbc
--->  Attempting to fetch libiodbc-3.52.14_2+libodbc+x11.darwin_19.x86_64.tbz2 from http://fco.it.packages.macports.org/libiodbc
--->  Fetching distfiles for libiodbc
--->  Verifying checksums for libiodbc
--->  Extracting libiodbc
Warning: The following existing file was hidden from the build system by trace mode:
  /private/var/select/sh
--->  Applying patches to libiodbc
Warning: The following existing file was hidden from the build system by trace mode:
  /private/var/select/sh
--->  Configuring libiodbc
Warning: The following existing files were hidden from the build system by trace mode:
  /opt/local/bin/ar
  /opt/local/bin/gawk
  /opt/local/bin/ggrep
  /opt/local/bin/gmkdir
  /opt/local/bin/gsed
  /opt/local/bin/lipo
  /opt/local/bin/nm
  /opt/local/bin/objdump
  /opt/local/bin/otool
  /opt/local/bin/pkg-config
  /opt/local/bin/ranlib
  /opt/local/bin/strip
  /private/var/select/sh
--->  Building libiodbc
Warning: The following existing files were hidden from the build system by trace mode:
  /opt/local/bin/ar
  /opt/local/bin/lipo
  /opt/local/bin/ranlib
  /opt/local/bin/strip
  /private/var/select/sh
--->  Staging libiodbc into destroot
Warning: The following existing files were hidden from the build system by trace mode:
  /opt/local/bin/ranlib
  /private/var/select/sh
  /var/root/.CFUserTextEncoding
--->  Installing libiodbc @3.52.14_2+libodbc+x11
--->  Deactivating libiodbc @3.52.13_1+x11
--->  Cleaning libiodbc
--->  Activating libiodbc @3.52.14_2+libodbc+x11

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #62571.

[ryrrah]

On Ventura, will only build using sudo port install libiodbc -x11

[Liontooth (David Liontooth)]

This library gets called when I install KDE and fails as above with the OP error:

sudo port install kde4-baseapps kdelibs4 kde4-runtime

A workaround on Apple silicon M2 with Ventura 13.1 (22C65) is to first issue

sudo port install libiodbc -x11 +universal

I haven't verified that Konqueror will build or work, but it gets you past the libiodbc error.

[kencu (Ken)]

anyone know why +x11 is a default variant here?

Everyone seems to have to manually force it off to build this, for years now, if gtk is installed at least, which it often is….

[kencu (Ken)]

ah, way back here: #38433