Menu
▾
▴
#196 Git: Build failure on Linux
make extensions
make -C auto
make[1]: Entering directory /usr/entwickeln/glew/auto'
perl -e "s/GLEW_MAJOR/1/g;s/GLEW_MINOR/9/g;s/GLEW_MICRO/0/g;" -p src/glew.rc > ../build/glew.rc
perl -e "s/GLEW_MAJOR/1/g;s/GLEW_MINOR/9/g;s/GLEW_MICRO/0/g;" -p src/glewinfo.rc > ../build/glewinfo.rc
perl -e "s/GLEW_MAJOR/1/g;s/GLEW_MINOR/9/g;s/GLEW_MICRO/0/g;" -p src/visualinfo.rc > ../build/visualinfo.rc
make[1]: Leaving directory/usr/entwickeln/glew/auto'
make -j4 'POPT=-fomit-frame-pointer -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g' LIBDIR=/usr/lib LDFLAGS.EXTRA= STRIP=
mkdir lib
make: *** No rule to make target src/glew.c', needed bytmp/linux/default/shared/glew.o'. Stop.
make: *** Waiting for unfinished jobs...
Discussion
That's odd.
Was this from a git clone, or the .tgz.
Any other system information that might be relevant? Internet connection?
I have the very same error, for me it was downloaded from Git, I can't do anything without glew (ok, maybe I could, but that's too tiresome) so please Gentle Man help me.
Can you check if it's the -j4 in particular that's causing the problem?
Same happens to me; building from the git repo on Windows using gcc.
it looks like the git repo is missing at least src/glew.c
Same issue. The git repository is no longer tracking the include directory as well as src/glew.c and src/glewinfo.c
Temporary workaround is to download a tar ball and copy the missing files to your clone directory.
Can confirm..this is pretty annoying that the git clone doesn't build because it is missing files that the snapshot has.
The generated source files have not traditionally been part of the repository.
Perhaps we ought to have a separate repository for that.
Closing as not-a-bug.
I'm open to having a repo for daily rebuilds of GLEW.
But it's not on the top of my TODO list.
Uhm. It is definitely a bug when somebody is unable to build the library by checking out the code. At the very least, add documentation in the README explaining how to generate the generated source code.