Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Mon, 28 Jan 2002 11:26:07 +0100
From: Corinna Vinschen <cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cannot find -ly?
Message-ID: <20020128112607.C11608@cygbert.vinschen.de>
Mail-Followup-To: cygwin@cygwin.com
References: <1011978313.30334.ezmlm@cygwin.com> <20020127201703.27468.qmail@web20406.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020127201703.27468.qmail@web20406.mail.yahoo.com>
User-Agent: Mutt/1.3.22.1i

On Sun, Jan 27, 2002 at 12:17:03PM -0800, y z wrote:
> Hi,
> 
> I want to compile with GCC in combination with FLEX
> and BISON. I have already got lex.yy.c and y.tab.c,
> but when I compiled with the following command: gcc
> y.tab.c -ll -ly, it always shows an error
> information:
> /usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5
> /../../../../i686-pc-cygwin/bin/ld: cannot find -ll   
>                    
> collect2: ld returned 1 exit status                 
>    
>                  
> I don't know why it cannot find -ll and -ly.  
> who knows how to resolve this problem?    

Typically you don't need them.  There's no such thing as a liby.a
for bison and there's a substitute for libl.a called libfl.a but
you should try linking without it.  Just write your own main()
and yywrap() functions.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

