Opened 9 years ago
Last modified 7 years ago
#1089 closed task
Flex 2.6.4 — at Version 6
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | major | Milestone: | CLFS Standard 3.1.0 |
Component: | BOOK | Version: | CLFS Standard GIT |
Keywords: | Cc: | berzerkula@…, jonathan@…, chris@…, cross-lfs@… |
Description (last modified by )
New Version
Download https://github.com/westes/flex/releases/download/v2.6.4/flex-2.6.4.tar.lz
- Update url location in XML
- Now requires Bison to build.
- Swap the build order of Bison and Flex in the final-system
- Will be test suite failures for Bison due to the absence of Flex
- Add Bison to /tools
- Flex doesn't appear to store the location for the Bison executable in its installed files so there shouldn't be any problems.
- Swap the build order of Bison and Flex in the final-system
For Ch 6 Option of installing Bison:
- Unsure if we'll need 32-bit and 64-bit for multilib
./configure \ --prefix=/tools \ --build=${CLFS_HOST} \ --host=${CLFS_TARGET} make make install
For Ch 10
- Check if M4=m4 is required in Ch 10 when installing Bison during Ch 6
- Use the following instead of a wrapper script:
ln -sv flex /usr/bin/lex
Change History (6)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
I put Bison into /tools and then built Flex with no problems and passed all it's tests, this is with a GCC-5.3.0 toolchain. However previously it didn't work on many tries before when building GCC snapshots this way. My suspect is/was a library linking problem with libstdc++, I've been removing .la files from the build as i go with redundant static libs and seems to be cleaner.
comment:3 by , 8 years ago
Milestone: | → CLFS Standard 3.1.0 |
---|---|
Summary: | Flex 2.6.0 → Flex 2.6.3 |
Version: | → CLFS Standard GIT |
comment:4 by , 8 years ago
Description: | modified (diff) |
---|
comment:5 by , 8 years ago
Description: | modified (diff) |
---|
comment:6 by , 8 years ago
Description: | modified (diff) |
---|---|
Summary: | Flex 2.6.3 → Flex 2.6.4 |
Note:
See TracTickets
for help on using tickets.
I've tried putting Bison into /tools - Flex still failed. I think it needs libraries from Bison, so the best solution would still be to swap Flex and Bison in the final-system, and add a note to the Bison page that some tests will fail due to Flex's absence.