Opened 8 years ago

Last modified 4 months ago

#51921 assigned defect

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

Reported by: danielta Owned by: nerdling (Jeremy Lavergne)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: jwhowse4, hapaguy (Brian Kurt Fujikawa), persramd@…, petrov@…, mojca (Mojca Miklavec), udbraumann, neo954 (Gᴏɴɢ Jie), jgonzale (Juan Gonzalez), lukewmo (Luke Mo), cjones051073 (Chris Jones), AlainT, Asoehn, jcinaz, kencu (Ken), DaveStrickland (Dave Strickland), cooljeanius (Eric Gallager), gregyao, TheLastLovemark
Port: libiodbc

Description (last modified by nerdling (Jeremy Lavergne))

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

Attachments (3)

libiodbc_main.log (25.7 KB) - added by danielta 8 years ago.
main.log
libiodbc-3.52.12-success.log.xz (24.4 KB) - added by nerdling (Jeremy Lavergne) 8 years ago.
succcessful build and install
main.log (493.8 KB) - added by danielta 8 years ago.
clean_main.log

Download all attachments as: .zip

Change History (27)

Changed 8 years ago by danielta

Attachment: libiodbc_main.log added

main.log

comment:1 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from macports-tickets@… to snc@…
Summary: libiodbc returned: command execution failedlibiodbc @3.52.12: error: use of undeclared identifier 'liburl'

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

comment:2 Changed 8 years ago by 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.

Changed 8 years ago by nerdling (Jeremy Lavergne)

succcessful build and install

comment:3 Changed 8 years ago by nerdling (Jeremy Lavergne)

Cc: ryandesign@… added

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

Changed 8 years ago by danielta

Attachment: main.log added

clean_main.log

comment:4 in reply to:  3 Changed 8 years ago by 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

Version 1, edited 8 years ago by danielta (previous) (next) (diff)

comment:5 Changed 8 years ago by nerdling (Jeremy Lavergne)

Cc: ryandesign@… removed
Description: modified (diff)
Status: newassigned
Summary: libiodbc @3.52.12: error: use of undeclared identifier 'liburl'libiodbc @3.52.12 +x11: error: use of undeclared identifier 'liburl'
Version: 2.3.4

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.

comment:6 Changed 8 years ago by nerdling (Jeremy Lavergne)

Cc: jwhowse4@… added

Has duplicate #51946.

comment:7 Changed 8 years ago by hapaguy (Brian Kurt Fujikawa)

Cc: brian.fujikawa@… added

Cc Me!

comment:8 Changed 8 years ago by persramd@…

Cc: persramd@… added

Cc Me!

comment:9 Changed 8 years ago by petrov@…

Cc: petrov@… added

Cc Me!

comment:10 Changed 8 years ago by mojca (Mojca Miklavec)

Cc: mojca@… added

Cc Me!

comment:11 Changed 8 years ago by udbraumann

Cc: braumann@… added

Cc Me!

comment:12 Changed 8 years ago by neo954 (Gᴏɴɢ Jie)

Cc: gongjie.jie@… added

Cc Me!

comment:13 Changed 7 years ago by 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

comment:14 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: riccardobrasca jgonzale added

Has duplicate #55002.

comment:15 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: lukewmo cjones051073 AlainT Asoehn added

Has duplicate #59471.

comment:16 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: jcinaz added

Has duplicate #59687.

comment:17 Changed 4 years ago by riccardobrasca

Cc: riccardobrasca removed

comment:18 Changed 4 years ago by 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

comment:19 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: kencu DaveStrickland cooljeanius added

Has duplicate #62571.

comment:20 Changed 2 years ago by ryrrah

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

comment:21 Changed 21 months ago by 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.

Last edited 4 months ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:22 Changed 21 months ago by 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….

Edit - Looks like I have it installed both ways on my M1, both with and without the x11 variant. Will have to experiment a bit to see what gtk versions were or were not installed when I built it with x11 active, I guess:

 % port -v installed libiodbc
The following ports are currently installed:
  libiodbc @3.52.15_2+libodbc+universal requested_variants='+universal-x11' platform='darwin 22' archs='arm64 x86_64' date='2022-12-30T16:28:08-0800'
  libiodbc @3.52.15_2+libodbc+universal+x11 (active) requested_variants='+universal' platform='darwin 22' archs='arm64 x86_64' date='2023-01-29T21:11:42-0800'
Last edited 21 months ago by kencu (Ken) (previous) (diff)

comment:23 Changed 21 months ago by kencu (Ken)

ah, way back here: #38433

comment:24 Changed 4 months ago by ryandesign (Ryan Carsten Schmidt)

Cc: gregyao TheLastLovemark added

Has duplicates #66466, #70427.

Note: See TracTickets for help on using tickets.