MinGW - Minimalist GNU for Windows

2009/5/14 Yara Fredmann <yfredmann@...>:
> Dear all,
>
> I've searched the list of questions but couldn't find an answer to my
> question. In addition the SF search engine provides results for all the
> products and not for answers in their mailing lists. Please accept my
> apologies if my question was repeated.
>
> I'm using the Flex, Fast lexical analyzer generator.
>
> However, to compile the resulting file, lex.yy.c, I could not figure it out
> of what the exact link library to include in the gcc command line options,
> or whether I have to set up my PATH environment library before. Therefore, I
> copied the file libfl.a into the current working directory where the
> lex.yy.c is located, and I issued the command
>
> d:\workspace\htiny\scand\lexscan>gcc lex.yy.c -llibfl
> C:\MinGW\bin\..\lib\gcc\mingw32\3.4.5\..\..\..\..\mingw32\bin\ld.exe: cannot
> find -llibfl
> collect2: ld returned 1 exit status
>
> or  -llibfl.a
>
> Where I copied libfl.a into the same directory where the program lex.yy.c is
> located.
>
> Any input is much appreciated. Thank you.
>
> Yacov

Yacov,

copy the lib into mingw/lib, or use command line
'd:\workspace\htiny\scand\lexscan>gcc lex.yy.c libf.a'

Cheers,
Kai


-- 
|  (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination

Yara Fredmann wrote:
> d:\workspace\htiny\scand\lexscan>gcc lex.yy.c -llibfl

http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/Link-Options.html#Link-Options
http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/Directory-Options.html#Directory-Options

You need to use -lfl and possibly add a directory to library search path
with -L <directory>. Remember that -L is an option specifier and should be
before input files on the command line whereas -l denotes a library file
and needs to be at the very end.

I'm pretty sure there's a FAQ entry about this somewhere.
If not, there's at least *the manual*..


-- 
Tuomo

... <@Longcat> Could a blue screen of death constitute being defenestrated?
    <Edible> Thrown out of Windo-
    <Edible> ...
    * Edible goes to cry.                      -- http://bash.org/?756448

> Where I copied libfl.a into the same directory where the program lex.yy.c is
> located.
>

d:\workspace\htiny\scand\lexscan>gcc lex.yy.c libfl.a
or
d:\workspace\htiny\scand\lexscan>gcc lex.yy.c -I./ -llibfl

Thanks Kai, it works.
It differs from the NIX-systems in the -l (hyphen ell) option.




________________________________
From: Kai Tietz <ktietz70@...>
To: MinGW Users List <mingw-users@...>
Sent: Thursday, May 14, 2009 7:28:31 PM
Subject: Re: [Mingw-users] GCC with Flex Link Library

2009/5/14 Yara Fredmann <yfredmann@...>:
> Dear all,
>
> I've searched the list of questions but couldn't find an answer to my
> question. In addition the SF search engine provides results for all the
> products and not for answers in their mailing lists. Please accept my
> apologies if my question was repeated.
>
> I'm using the Flex, Fast lexical analyzer generator.
>
> However, to compile the resulting file, lex.yy.c, I could not figure it out
> of what the exact link library to include in the gcc command line options,
> or whether I have to set up my PATH environment library before. Therefore, I
> copied the file libfl.a into the current working directory where the
> lex.yy.c is located, and I issued the command
>
> d:\workspace\htiny\scand\lexscan>gcc lex.yy.c -llibfl
> C:\MinGW\bin\..\lib\gcc\mingw32\3.4.5\..\..\..\..\mingw32\bin\ld.exe: cannot
> find -llibfl
> collect2: ld returned 1 exit status
>
> or  -llibfl.a
>
> Where I copied libfl.a into the same directory where the program lex.yy.c is
> located.
>
> Any input is much appreciated. Thank you.
>
> Yacov

Yacov,

copy the lib into mingw/lib, or use command line
'd:\workspace\htiny\scand\lexscan>gcc lex.yy.c libf.a'

Cheers,
Kai


-- 
|  (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
MinGW-users mailing list
MinGW-users@...

This list observes the Etiquette found at 
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) Thread hijacking
3) HTML/MIME encoded mail
4) Improper quoting
5) Improper trimming
_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

Yara Fredmann wrote:
> Thanks Kai, it works.
> It differs from the NIX-systems in the -l (hyphen ell) option.

Only if your Unix system has a library named "liblibfl.a" because
that is what you pointed your linker to.


Also, please read points 1 and 5 of the following:

> Most annoying abuses are:
> 1) Top posting
> 2) Thread hijacking
> 3) HTML/MIME encoded mail
> 4) Improper quoting
> 5) Improper trimming



-- 
Tuomo

... Everybody won. The developer's change worked. The business didn't
    have to run its usual expensive testing cycle. Dave executed the
    deployment perfectly (aside from jumping the gun on production).
    And Dave took the opportunity to update the documentation (and
    increase the font size of the headings).
    The moral? Always deploy changes straight to production without
    testing them.
    Wait, that can't be right.
                   -- on http://thedailywtf.com/Articles/
                           Application-Lifecycle-Mismanagement.aspx

Dear Latto,

I do know exactly what I'm asking! You do NOT know what you're answering.
Besides this mailing list is not for uNIX-systems; it's for Windows. Read point number 2 in the list you pointed to.

Yacov




________________________________
From: Tuomo Latto <djv@...>
To: MinGW Users List <mingw-users@...>
Sent: Tuesday, May 19, 2009 2:52:38 PM
Subject: Re: [Mingw-users] GCC with Flex Link Library

Yara Fredmann wrote:
> Thanks Kai, it works.
> It differs from the NIX-systems in the -l (hyphen ell) option.

Only if your Unix system has a library named "liblibfl.a" because
that is what you pointed your linker to.


Also, please read points 1 and 5 of the following:

> Most annoying abuses are:
> 1) Top posting
> 2) Thread hijacking
> 3) HTML/MIME encoded mail
> 4) Improper quoting
> 5) Improper trimming



-- 
Tuomo

.... Everybody won. The developer's change worked. The business didn't
    have to run its usual expensive testing cycle. Dave executed the
    deployment perfectly (aside from jumping the gun on production).
    And Dave took the opportunity to update the documentation (and
    increase the font size of the headings).
    The moral? Always deploy changes straight to production without
    testing them.
    Wait, that can't be right.
                   -- on http://thedailywtf.com/Articles/
                           Application-Lifecycle-Mismanagement.aspx


------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects
_______________________________________________
MinGW-users mailing list
MinGW-users@...

This list observes the Etiquette found at 
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) Thread hijacking
3) HTML/MIME encoded mail
4) Improper quoting
5) Improper trimming
_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

Quoting Yara Fredmann <yfredmann@...>:

> Dear Latto,
>
> I do know exactly what I'm asking! You do NOT know what you're answering.
> Besides this mailing list is not for uNIX-systems; it's for Windows.  
> Read point number 2 in the list you pointed to.
>

Stop top posting.

The point trying to be made is that -llibfl will look for liblibfl.a  
and not libfl.a.  You need to specify -lfl instead to find libfl.a  
regardless if it is UNIX or Windows.  BTW, many people use UNIX to  
build WINDOWS applications.

--
Earnie
MinGW Administrator

On Wednesday 20 May 2009 09:26:51 Yara Fredmann wrote:
> I do know exactly what I'm asking!

Really?  All the evidence of your posting to this thread would 
suggest exactly the opposite!

> You do NOT know what you're answering.

Oh, I think Tuomo, (not Latto, as you addressed him), knew exactly 
what he was answering; in fact, he was right on the money, in his 
correction of *your* error.  In summary, you said:--

> I issued the command
>
>    gcc lex.yy.c -llibfl

and gcc failed to find libfl.a, (as it also did when you specified 
it as `-llibfl.a').  You went on to say that this command *worked* 
when you ran it on *nix.  Well, pay attention: if it *did* work on 
*nix, then it didn't find libfl.a; it found liblibfl.a, (unless 
your *nix system is *seriously* screwed up).  This is exactly what 
Tuomo *correctly* pointed out, for the correct form of the command, 
identically on *both* *nix and MinGW, is (as Tuomo said):--

   gcc lex.yy.c -lfl

*provided* you have installed libfl.a into a *standard* library 
directory, (which for MinGW, means C:\mingw\lib, if you have 
installed in the standard location).  If you haven't done this, 
then you need to add a `-L path/to/lib', as Tuomo also suggested.

> Besides this mailing list is not for uNIX-systems; 

No, it isn't.  However...

> it's for Windows.

...neither is it for this!  It *is* for MinGW and MSYS; the former 
is a *nixy style compiler suite for MS-Windows, while the latter is 
a *nixy CLI environment for the same platform.

> Read point number 2 in the list you pointed to. 

And what, exactly, did you intend by this?  The list to which you 
refer is:--

> Most annoying abuses are:
> 1) Top posting
> 2) Thread hijacking
> 3) HTML/MIME encoded mail
> 4) Improper quoting
> 5) Improper trimming

You have accused Tuomo of a type 2 offence, which he is not, (there 
is no thread being hijacked here).  However, *you* have, yet again, 
flagrantly committed all of type 1,3,4 and 5 offences; an excellent 
strategy, if your aim is to make yourself gravely unpopular on this 
mailing list, ultimately leading to your posts being ignored, (or, 
if you piss me off enough, bounced).

-- 

Regards,
Keith (list moderator).

On Tuesday 19 May 2009 10:14:12 notmmao wrote:
>> I copied libfl.a into the same directory where the program
>> lex.yy.c is
>>
>> located.
>
> d:\workspace\htiny\scand\lexscan>gcc lex.yy.c libfl.a

Yep, that would work, (provided the command is run with the 
directory in which both lex.yy.c and libfl.a are to be found, set 
as `current directory').  However...
 
> or
> d:\workspace\htiny\scand\lexscan>gcc lex.yy.c -I./ -llibfl

...this will *not* work; (`-I' is for headers, *not* libraries, and 
`-llibfl' refers to liblibfl.a, *not* to libfl.a).  The correct 
form of the latter command is:--

   gcc lex.yy.c -L. -lfl

(`-L.' adds current directory to the library search path, and `-lfl' 
refers to libfl.a, in the first directory where it can be found, in 
that path, (which will be the current directory in this case)).

-- 

Regards,
Keith.