Flex compilation issue...
otqzyrn02 at sneakemail.com
Wed Jun 1 09:45:55 PDT 2005
> -----Original Message-----
> Sent: Wednesday, June 01, 2005 12:36 PM
> Subject: Re: Flex compilation issue...
> On Tue, May 31, 2005 at 08:33:58PM -0600, Archaic wrote:
> > On Tue, May 31, 2005 at 05:22:46PM -0500, Randy McMurchy wrote:
> > >
> > > If Flex is required to build itself, then it probably should be
> > > put back into the book in Chapter 5. I'm cc'ing the -dev list with
> > > this message, so the dev guys can determine if it really needs to
> > > be added back.
> > I'm going to run a trunk build tonight with flex removed
> and see what
> > happens. This is a known solid host so any error should denote a
> > problem.
> Flex does not seem necessary. But just to make sure, I will layout my
> differences. First, I haven't updated my scripts to fsf
> binutils so I am
> still building flex, m4, and bison in chapter5. After the binutils
> installation in chapter6 I rm'd all flex libs and bins and flex built
> fine. 38 tests passed, 0 failed.
> According to the OP's error, a .l file was modified.
> /bin/sh /working/flex-2.5.31/missing --run flex scan.l
> /working/flex-2.5.31/missing: line 46: flex: command not found
> First, I find no occurence of 'run flex' in my logs, and second where
> did /working come from?
> Want control, education, and security from your operating system?
> Hardened Linux From Scratch
> FAQ: http://www.linuxfromscratch.org/faq/
> Unsubscribe: See the above information page
Well, you won't find that "run flex" in your logs unless something "bad"
happens. :) As it did with me...
Secondly, /working is where I unpack everything to work in (I still keep
sources in the /sources directory). I just untar everything in /working, I
find it keeps things a lot neater and easier to find. :)
More information about the lfs-dev