From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin list <cygwin@cygwin.com>
Subject: Re: GCC Compiler can't seem to find linker
Date: Tue, 04 Jul 2017 06:35:00 -0000 [thread overview]
Message-ID: <CAEhDDbD=R8G6kWVkMDikTyNfiqM7vFWP_dXC4dq95jLBW7_MMA@mail.gmail.com> (raw)
In-Reply-To: <f6a81778d5f45db0a05f72baea2842a3@openmailbox.org>
Hi,
On Mon, Jul 3, 2017 at 11:52 PM, starz0rdesign wrote:
> Hello.
>
> I'm having a bit of an issue trying to compile LibArchive 3.3.1 for Windows.
> I have Mingw64 with GCC7.1 installed to prevent the Cygwin installer from
> linking it's DLL.
Maybe you should ask on the Mingw mailing list.
> At the end of the make process I seem to get this error:
> make all-am
> make[1]: Entering directory '/home/nobodyimportant/libarchive-3.3.1'
> CCLD libarchive.la
It would be helpful to show the full command line. Add V=1 to the make
invocation:
make V=1 (other make parameters, if any)
> C:/Program
> Files/mingw-w64/x86_64-7.1.0-posix-seh-rt_v5-rev0/mingw64/bin/../lib
> /gcc/x86_64-w64-mingw32/7.1.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
> cannot
> find -link
This doesn't mean that the compiler didn't find the linker. This error
message means that the linker (ld.exe) didn't find a library, namely
libink.a
Csaba
--
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds
--
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
next prev parent reply other threads:[~2017-07-04 6:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 21:52 starz0rdesign
2017-07-04 6:35 ` Csaba Raduly [this message]
2017-07-06 4:13 starz0rdesign
2017-07-06 5:50 ` Mark Geisert
2017-07-06 6:50 starz0rdesign
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='CAEhDDbD=R8G6kWVkMDikTyNfiqM7vFWP_dXC4dq95jLBW7_MMA@mail.gmail.com' \
--to=rcsaba@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).