Hello. On Tue, 2014-04-01 at 12:03, Florian Schaefer wrote: > > thanks for taking your time. I actually tried among the first things > > rm -rf efl > git clone git://git.enlightenment.org/core/efl.git > > No help. But I took your clue to look again at my all-inclusive compile > command line: > > export CPPFLAGS="$CPPFLAGS -march=pentium-m -I/opt/e/include"; export > LDFLAGS="$LDFLAGS -L/opt/e/lib"; export PATH="$PATH:/opt/e/bin"; export > PKG_CONFIG_PATH="/opt/e/lib/pkgconfig"; ./autogen.sh --prefix=/opt/e > --disable-static --enable-xinput22 --enable-multisense --enable-systemd > --enable-image-loader-webp --enable-harfbuzz && make clean && make -j4 > && make install > > Playing around with it a bit I found the problem: I am first calling > autogen and then "make clean". It seems that "make clean" removes > something that it should better not touch. > > So is this a bug with the Makefile? I cannot imagine that a make clean > should render a project not compilable any more unless reconfigured. And > I was actually using above compile line (with varying options for > autogen) since the first bits of E17 appeared and never encountered this > kind of trouble.
Its odd that you have the make clean in between but a normal make clean should not require a new configure or autogen run. I was able to reproduce this. Please fill a bug on phab.enlightenment.org and assign it to me. I will have a look when I have a moment. regards Stefan Schmidt ------------------------------------------------------------------------------ _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
