From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Building the python swig tutorial
Date: Sat, 27 Mar 2021 16:09:32 +0100 [thread overview]
Message-ID: <b0d17d88-6d4e-b2ef-523c-f0956303ded3@t-online.de> (raw)
In-Reply-To: <fe7572cd-0da9-ceb4-8190-510b09ce6808@seanet.com>
Am 27.03.2021 um 13:58 schrieb Brad Bell:
> It appeard that I need to add an non-standard location to a path so that
> the linker can find these files ?
Read those error messages again. It's failing to find things _in_ any
of those files, which means it did in fact find all files it was looking
for just fine.
So no, this is almost certainly no issue with locations of files. It's
an issue of not telling the linker that it's supposed to be looking for
certain libraries in the first place.
But it's virtually impossible to diagnose this sensibly, as you opted
not to show any of the actual command(s) you used.
next prev parent reply other threads:[~2021-03-27 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 12:58 Brad Bell
2021-03-27 15:09 ` Hans-Bernhard Bröker [this message]
2021-03-28 12:22 ` Brad Bell
2021-03-28 15:07 ` Marco Atzeri
2021-03-27 15:36 ` 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=b0d17d88-6d4e-b2ef-523c-f0956303ded3@t-online.de \
--to=hbbroeker@t-online.de \
--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).