bugGNU GRUB - Bugs: bug #50093, Build failure with flex 2.6.3

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #50093: Build failure with flex 2.6.3

Submitter:  felix <felix_s>
Submitted:  Thu 19 Jan 2017 12:16:21 PM UTC
 
Category:  Compilation Severity:  Major
Priority:  5 - Normal Item Group:  None
Status:  None Privacy:  Public
Assigned to:  None Originator Name: 
Open/Closed:  Closed Release:  Git master
Release:  Reproducibility:  Every Time
Planned Release:  None

Tue 24 Jan 2017 05:09:42 PM UTC, comment #4: 

This is fixed in current flex git, so closing.

Andrei Borzenkov <arvidjaar>
Project Member
Thu 19 Jan 2017 06:22:04 PM UTC, comment #3: 

Regarding issue itself - it appears bug in flex, introduced in 2.6.3. The conflicting defines are under %if-not-reentrant, and grub has "%option reentrant" in its yylex.l. Other projects are affected as well.

https://github.com/westes/flex/issues/162

Andrei Borzenkov <arvidjaar>
Project Member
Thu 19 Jan 2017 05:44:24 PM UTC, comment #2: 

Thank you, but please, either file separate bugs for separate issues, or use grub-devel for such reports (even better, send patch to grub-devel).

Andrei Borzenkov <arvidjaar>
Project Member
Thu 19 Jan 2017 04:33:37 PM UTC, comment #1: 

Completely tangentially, there's a typo in configure.ac, line 280 (stray quotation mark).

felix <felix_s>
Thu 19 Jan 2017 12:16:21 PM UTC, original submission:  

Building GRUB with flex 2.6.3 generates an error message about macros yyalloc, yyfree and yyrealloc being redefined.

Adding #undefs in yylex.l fixes it.

felix <felix_s>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by arvidjaar (Posted a comment)
  • -email is unavailable- added by felix_s (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

     

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-01-24 arvidjaar Open/ClosedOpen Closed

    Back to the top


    Powered by Savane 3.9