search

westes / flex

The Fast Lexical Analyzer - scanner generator for lexing in C and C++
Other
3.62k stars 536 forks source link

During compile of 2.6.4 stage1flex fails to open a trivial file #417

Open blastwave opened 5 years ago

blastwave commented 5 years ago

Very strange behavior during the compile with Oracle Studio C99 compiler and I am fairly sure that the compiler has nothing to do with it.

What I see is stage1flex being created in the ./src directory and that is no issue.

Then the next step is :

./stage1flex -o stage1scan.c ./scan.l stage1flex: can't open ./scan.l gmake[2]: [Makefile:1696: stage1scan.c] Error 1 gmake[2]: Leaving directory '/usr/local/build/flex-2.6.4_SunOS5.10_sparc64vii+.001/src' gmake[1]: [Makefile:546: all] Error 2 gmake[1]: Leaving directory '/usr/local/build/flex-2.6.4_SunOS5.10_sparc64vii+.001/src' gmake: *** [Makefile:533: all-recursive] Error 1

However the input file certainly exists and I can reproduce manually :

corv $ ls -ladb ./src/scan.l -rw-r--r-- 1 dclarke devl 27707 May 3 2017 ./src/scan.l corv $ corv $ ./src/stage1flex -o /tmp/stage1scan.c ./src/scan.l stage1flex: can't open ./src/scan.l corv $

No idea why that is happening.

corv $ ./src/stage1flex --version stage1flex 2.6.4

Nice but doesn't "work" in a sane way.

Dennis

Explorer09 commented 5 years ago

@zmajeed Pull #399 corrects the Automake version requirement, so you can apply that if you don't want to build the latest version of Automake.

By the way, thanks for testing things out. (Does the issue still happen on @blastwave 's OS and compile tools? I'm waiting for a reply.)

blastwave commented 5 years ago

I made trivial changes to scan.c and misc.c as posted earlier. All other problems are gone and I will do atest on Debian Linux x86_64, and i686 and arm and ppc64 to verify on FreeBSD x86_64 and FreeBSD ppc64 at some point this week. That will be done with gcc 8.3.0 and Clang/LLVM.

blastwave commented 5 years ago

I don't recall where we are with this but I have 2.6.4 built and installed and all is well. Can we close this thing and maybe kick out a 2.6.5 ??

blastwave commented 4 years ago

Just a follow up but here in 2020 the same problem exists and even worse so if I use the git repo. Would be nice to work out the portability issues and make a new release. I am happy to test and work on this as flex is, you know, pretty essential.