public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin@cygwin.com
Subject: Re: ld fails when -L/lib is on the command line
Date: Wed, 13 Oct 2010 07:51:00 -0000	[thread overview]
Message-ID: <AANLkTikRkEjNPoJ2v1xJ34XuWviUrv95J0LJw5MV4=9M@mail.gmail.com> (raw)
In-Reply-To: <20101012205527.GA12942@ednor.casa.cgf.cx>

On Tue, Oct 12, 2010 at 10:55 PM, Christopher Faylor  wrote:
> On Tue, Oct 12, 2010 at 12:55:09PM -0500, Nathan Thern wrote:
>>A complicated project I'm building fails on this call to gcc:
>>gcc -shared <object files> -L<lib_path_in_build_tree> -L/lib
>>-L/usr/lib <build_libs> <std_libs> -o .libs/cyg<lib>.dll
>>-Wl,--enable-auto-image-base -Xlinker --out-implib -Xlinker
>>.libs/lib<lib>.dll.a
>
> You're going to have to clue us in on what "fails" means in this context.

In other words, we need the error message.

Check the makefile. My suspicion is that there is a
-L$(SOME_VARIABLE)/lib there, but the variable is not defined and so
it's expanded to empty.

-- 
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ L w++$ tv+ b++ DI D++ 5++
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

      reply	other threads:[~2010-10-13  7:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12 17:55 Nathan Thern
2010-10-12 20:55 ` Christopher Faylor
2010-10-13  7:51   ` Csaba Raduly [this message]

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='AANLkTikRkEjNPoJ2v1xJ34XuWviUrv95J0LJw5MV4=9M@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).