Description of problem: Anjuta x86_64 crashes when creating a new project. Version-Release number of selected component (if applicable): anjuta-1.2.2-5 How reproducible: Always Steps to Reproduce: 1.Start Anjuta 2.Create a new project 3.When finished Anjuta creates the project; AFAICS it tries to run autogen.sh for it. Then it crahes. Additional info: Backtrace attached. Problem reported by Dawid Zamirski <dzrudy>: https://www.redhat.com/archives/fedora-extras-list/2005-February/msg00059.html I can confirm this. Did not look at the package from dag yet.
Created attachment 110602 [details] anjuta-backtrace
Don't ask me why: But removing the "--enable-final" from the configure fixes this problem.
In configure.in: dnl Enable release builds AC_ARG_ENABLE(final, [ --enable-final Build release executables (GCC only)], CFLAGS="$CFLAGS -DNDEBUG -O0 -g" CXXFLAGS="$CXXFLAGS -DNDEBUG -O0 -g") In the build log of current CVS version: gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -O2 -g -pipe -m32 -march=i386 -mtune=pentium4 -DNDEBUG -O0 -g -c args.c Depending on where they ifdef NDEBUG and how they use it (e.g. for asserts), it might make sense to get it back into the CFLAGS when building without --enable-final.
Phillip( or Michael), how to proceed? I suggest to create an update that builds on x86_64 without "--enable-final" and fix the real issue later?
Created attachment 110927 [details] spec patch proposal Feel free to apply something like this if you agree.
>Created an attachment (id=110927) >spec patch proposal >Feel free to apply something like this if you agree. Commited and build requested. Tested on i386 an x86_86, works fine.