This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: flex and dos source files. How is flex built for cygwin
On Mon, 22 Nov 2004, Peter Rehley wrote:
> On Nov 22, 2004, at 9:21 AM, Igor Pechtchanski wrote:
>
> > On Sat, 20 Nov 2004, Peter Rehley wrote:
> >
> > > On Nov 20, 2004, at 10:19 AM, Reini Urban wrote:
> > >
> > > [snip]
> > > > ok thanks, for confirmation.
> > > > so cgf should repackage it. it's obviously a bug.
> > >
> > > I think so also because this isn't the behavior that occurs on linux
> > > or BSD.
> >
> > Umm, which behavior are you talking about? The automatic conversion
> > of CRLF line endings to LF? This is Cygwin-specific behavior, and has
> > nothing to do with Linux or BSD. It's there to avoid complaints from
> > people who use, say, notepad on binary mounts to edit their .flex
> > files.
>
> I suspected as much.
So you probably suspect the answer to your repackaging suggestion as well:
it's not going to be repackaged.
> [snip]
> > > Modified build commands would be
> > > ./configure; make LDFLAGS="/usr/lib/automode.o"
> >
> > <PEDANTIC>
> > The above should really be
> > ./configure; make LDLIBS="/usr/lib/automode.o"
> > ^^^^
> make LIBS="-lintl /usr/lib/automode.o". There is no LDLIBS in the flex
> source, and when setting LIBS the -lintl is needed because the LIBS in the
> Makefile had that value.
It *is* LDLIBS. See "make -pf/dev/null | grep -C2 '^%: %.o'". BTW, this
is not Cygwin-specific.
> > It may not matter for linking in a .o file, but it certainly will matter if
> > a -l form is used (as you tried earlier).
> > </PEDANTIC>
HTH,
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/