public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin@cygwin.com
Subject: Re: autoconf tests for iconv fail with undefined refs
Date: Sat, 19 Feb 2022 16:51:04 +0900	[thread overview]
Message-ID: <20220219165102.C6CA.50F79699@gmail.com> (raw)
In-Reply-To: <32675850-0f12-33f1-9d89-b39b2c754f6f@SystematicSw.ab.ca>

[-- Attachment #1: Type: text/plain, Size: 285 bytes --]

On Fri, 18 Feb 2022 12:33:30 -0700, Brian Inglis
> Any idea why autoconf tests for iconv now fail with undefined refs to iconv{_open,,_close}! STC attached, log, -E output. Tried also with -l iconv.

About libisocodes 1.2.4, these patches (attached) may help cygport-build.

Lem

[-- Attachment #2: 1.2.4-vapidir.patch --]
[-- Type: application/octet-stream, Size: 361 bytes --]

--- origsrc/libisocodes-libisocodes-1.2.4/Makefile.am	2021-08-27 03:04:39.000000000 +0900
+++ src/libisocodes-libisocodes-1.2.4/Makefile.am
@@ -57,7 +57,7 @@
 	--pkg libxml-2.0 \
 	--pkg gee-0.8 \
 	--library=libisocodes \
-	--vapidir=vapi --pkg config \
+	--vapidir=$(srcdir)/vapi --pkg config \
 	--header=libisocodes.h \
 	--gir=libisocodes-$(VERSION).gir
 

[-- Attachment #3: 1.2.4-no-undefined.patch --]
[-- Type: application/octet-stream, Size: 1323 bytes --]

--- origsrc/libisocodes-libisocodes-1.2.4/Makefile.am	2021-08-27 03:04:39.000000000 +0900
+++ src/libisocodes-libisocodes-1.2.4/Makefile.am
@@ -65,7 +65,7 @@ VALAFLAGS = \
 libisocodes_la_CPPFLAGS = -include config.h -DLOCALEDIR=\""$(localedir)"\"
 libisocodes_la_CFLAGS = $(GOBJECT_CFLAGS) $(GLIB_CFLAGS) $(LIBXML_CFLAGS) $(GEE_CFLAGS)
 libisocodes_la_LIBADD = $(GOBJECT_LIBS) $(GLIB_LIBS) $(LIBXML_LIBS) $(GEE_LIBS)
-libisocodes_la_LDFLAGS = -version-info $(LIBISOCODES_LT_VERSION)
+libisocodes_la_LDFLAGS = -version-info $(LIBISOCODES_LT_VERSION) -no-undefined
 
 DISTCLEANFILES = libisocodes.pc
 MAINTAINERCLEANFILES = config.h.in~ libisocodes.h libisocodes.vapi libisocodes-$(VERSION).gir
@@ -94,8 +94,13 @@ libisocodes-$(VERSION).gir: $(lib_LTLIBR
 girdir = $(datadir)/gir-1.0
 gir_DATA = libisocodes-$(VERSION).gir
 
+# We have to extract our own dlname from libisocodes.la; see bgo#658002.
+# This is what g-ir-scanner does.
+libisocodes_dlname = \
+       `$(SED) -n "s/^dlname='\([A-Za-z0-9.+-]\+\)'/\1/p" libisocodes.la`
+
 libisocodes-$(VERSION).typelib: libisocodes-$(VERSION).gir
-	$(G_IR_COMPILER) --shared-library=libisocodes.so --output=$@ $<
+	$(G_IR_COMPILER) --shared-library=$(libisocodes_dlname) --output=$@ $<
 
 typelibdir = $(libdir)/girepository-1.0
 typelib_DATA = libisocodes-$(VERSION).typelib

  parent reply	other threads:[~2022-02-19  7:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 19:33 Brian Inglis
2022-02-19  5:26 ` Lemures Lemniscati
2022-02-19 17:11   ` Brian Inglis
2022-02-19 23:37     ` Lemures Lemniscati
2022-02-19 23:53       ` Brian Inglis
2022-02-20  1:10         ` Lemures Lemniscati
2022-02-19  7:51 ` Lemures Lemniscati [this message]
2022-02-19 15:46   ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220219165102.C6CA.50F79699@gmail.com \
    --to=lemures.lemniscati@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).