• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Build error … lex: not found

Scheduled Pinned Locked Moved Development
1 Posts 1 Posters 2.7k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G
    gmckinney
    last edited by Oct 6, 2007, 8:04 PM Sep 29, 2007, 3:22 PM

    Hi all,

    I have installed the pfSense 1.2-BETA-1-Testing-Snapshot-05-02-07-pfSense development system on an ALEX board (pc-engines) with a 8-Gig CF card and 256-megs of RAM installed on the board (Works very well too) but I am getting an error during the developer bootstrap operation that is supposed to build the system to check for a sane installation.

    The error reported is listed in the Subject line, ie:  lex: no found

    I attempted to correct the error by using pkg-add to download and install flex (the lex replacement) but that did not work - flex was installed but the system still does not "find" lex to perform the build.

    Here is a "small" snippet of the error messages seen:

    lex -t   /usr/src/sys/dev/aic7xxx/aicasm/aicasm_scan.l > aicasm_scan.c
    lex: not found
    *** Error code 127

    The above error is in the stage 2.3: build tools section and appears in all the build versions the system attempts…

    I have not worked in the 'bsd' environment for about eight years so I am still coming back up to speed but any suggestions on correction of this error would be greatly appreciated!!!

    gm...

    [edited]

    Well - I just downloaded the development iso image - uncomressed it - burned it to a CD rom disk and installeded it on a clean (totally wiped) hard drive… and it built the system correctly!

    Unless someone fixed a problem in the development system I really have no clue as to what happened!  This correctly built system is running on the SAME hardware it had failed on previously!

    Anyone have any explanation???

    gm....

    1 Reply Last reply Reply Quote 0
    1 out of 1
    • First post
      1/1
      Last post
    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
      This community forum collects and processes your personal information.
      consent.not_received