public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Compile gsoap as shared library - undefined references
Date: Mon, 01 Jul 2019 12:47:00 -0000	[thread overview]
Message-ID: <378469b3-97de-b0bb-6664-d6f9db0dc8ee@gmail.com> (raw)
In-Reply-To: <CAC6GFCs8_My9Gp_9DQmRt2AQ0zOt4kvgFUNatz5Z2HEA6UDswQ@mail.gmail.com>

Am 01.07.2019 um 11:09 schrieb Wilhelm Eger:
> Hello there!
>
> This is my first post to the cygwin mailing list. Hence, I hope, this
> is the right place to post my problem. It seems to be a mixture of
> packaging / compiling / linking / porting problem. However, I was
> thinking that starting in this list is more appropriate than in e.g.
> the packagers list.
>
> I would like to compile gsoap as a shared library to use it in another
> project (kopano-core). Please note that static linking works fine.
> However, I would like to achieve a shared library of gsoap. gsoap
> itself provides only static compilation. However, the major
> distributions deliver it as shared library. That's where I have
> started:
>
> gSoap: https://sourceforge.net/projects/gsoap2/
> OpenSuse Patches for shared library:
> https://build.opensuse.org/package/show/home:mrbadguy/gsoap
>
> Please find my respective patches plus cygport package attached to this mail.
>
> Unfortunately, the package does not build. In fact, it fails at
> linking the shared library due to undefined references. Please not
> that I have updated the OpenSuse patches by adding '-no-undefined' to
> the libtool chain. Further, I have added 'mcmodel=large' to the CFLAGS
> to work around relocation problems.
>
> Still, undefined references are found:

> /bin/sh ../libtool  --tag=CC   --mode=link gcc      -mcmodel=large
> -DCYGWIN -ggdb -O2 -pipe -Wall -Werror=format-security
> -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector-strong
> --param=ssp-buffer-size=4 -D_GNU_SOURCE -Wno-attributes
> -fdebug-prefix-map=/home/eger/gsoap-shared/gsoap-2.8.84-1.x86_64/build=/usr/src/debug/gsoap-2.8.84-1
> -fdebug-prefix-map=/home/eger/gsoap-shared/gsoap-2.8.84-1.x86_64/src/gsoap-2.8=/usr/src/debug/gsoap-2.8.84-1
> -release 2.8.84 -Wl,--version-script=gsoap.sym -no-undefined     -o
> libgsoap.la -rpath /usr/lib libgsoap_la-stdsoap2.lo libgsoap_la-dom.lo
> libtool: link: gcc -shared  .libs/libgsoap_la-stdsoap2.o
> .libs/libgsoap_la-dom.o    -mcmodel=large -ggdb -O2
> -fstack-protector-strong -Wl,--version-script=gsoap.sym   -o
> .libs/cyggsoap-2-8-84.dll -Wl,--enable-auto-image-base -Xlinker
> --out-implib -Xlinker .libs/libgsoap.dll.a
> .libs/libgsoap_la-stdsoap2.o:stdsoap2.c:(.rdata$.refptr.soap_fault_detail[.refptr.soap_fault_detail]+0x0):
> undefined reference to `soap_fault_detail'

which library provide soap_fault_detail ?

Maybe the package will build multiple dlls and you need to add
the dependencies ?

Marco


---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-07-01 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01  9:10 Wilhelm Eger
2019-07-01 12:47 ` Marco Atzeri [this message]
2019-07-01 13:38   ` Wilhelm Eger
2019-07-01 14:01     ` Marco Atzeri

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=378469b3-97de-b0bb-6664-d6f9db0dc8ee@gmail.com \
    --to=marco.atzeri@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).