internal error in flex

Bug #1106865 reported by Leif Lindholm
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linaro AArch64 cross-distro work
Fix Released
Low
Unassigned
Linaro OpenEmbedded
Fix Released
Undecided
Unassigned

Bug Description

Reduced test case from attempted open-mpi build - relevant source file attached.

$ flex keyval_lex.l
flex: fatal internal error, exec failed

Builds successfully on amd64 with same flex version (2.5.35).

Revision history for this message
Leif Lindholm (leif-lindholm) wrote :
Revision history for this message
Leif Lindholm (leif-lindholm) wrote :

Environment: linaro-sdk-oe #132.

Revision history for this message
Riku Voipio (riku-voipio) wrote :

flex tries to execute:

/data/oe/build/tmp-eglibc/sysroots/x86_64-linux/usr/bin/m4

As workaround you can:

mkdir -p /data/oe/build/tmp-eglibc/sysroots/x86_64-linux/usr/bin/
ln -s /usr/bin/m4 /data/oe/build/tmp-eglibc/sysroots/x86_64-linux/usr/bin/

So this is a bug how OE builds flex.

Revision history for this message
Riku Voipio (riku-voipio) wrote :

Where, of course, /data/oe/build is whatever has been used as the build directory when building the linaro-image-sdk.

Revision history for this message
Riku Voipio (riku-voipio) wrote :

Marcin,

please have a look at:

meta/recipes-devtools/bison/bison_2.7.bb
meta/recipes-devtools/flex/flex.inc

M4 path should only be hardcoded for the flex-native and bison-native, now also flex and bison installed to target get M4 path hardcoded to staging directory.

Changed in linaro-oe:
status: New → Triaged
Changed in linaro-aarch64:
status: New → Triaged
Changed in linaro-oe:
assignee: nobody → Marcin Juszkiewicz (hrw)
Revision history for this message
Marcin Juszkiewicz (hrw) wrote :

fix sent to ML

Changed in linaro-oe:
status: Triaged → In Progress
Marcin Juszkiewicz (hrw)
Changed in linaro-oe:
status: In Progress → Fix Released
Changed in linaro-aarch64:
status: Triaged → Fix Released
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.