|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
|
|
Compile with debug issueI've enabled debug using: ./configure --enable-debug
When I run make clean, I get: g++ -c -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtCore -I/usr/include/qt4 -DQT3_SUPPORT -DLITTLE_ENDIAN=1 @MINIMAL_CFLAGS@ data/data.cpp -o data/data.o g++: @MINIMAL_CFLAGS@: No such file or directory make: *** [data/data.o] Error 1 Is this something in my configuration? (I'm running Ubuntu 9.04) or have I done something wrong? Chris ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@... - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel |
|
|
Re: Compile with debug issueIt seems that rerunning sh ./bootstrap.sh then ./configure
--enable-debug fixes this problem. I don't know what bootstrap does. Is this normal? ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@... - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel |
|
|
Re: Compile with debug issueOn Fri, Jul 3, 2009 at 3:17 PM, Chris Fryer<chrisf1874@...> wrote:
> It seems that rerunning sh ./bootstrap.sh then ./configure > --enable-debug fixes this problem. > > I don't know what bootstrap does. Is this normal? bootstrap.sh regenerates the configure script from configure.ac and acinclude.m4. You need to re-run it when one of those has changed. Unfortunately, we're (or at least, I'm) not very good at remembering to notify the list when this has happened. The change that caused your problem happened a little while ago, but it doesn't actually show until you next have to run configure; then it breaks. Chris ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@... - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel |
|
|
Re: Compile with debug issueOn Fri, Jul 3, 2009 at 5:51 PM, Chris
Cannam<cannam@...> wrote: > Unfortunately, we're (or at least, I'm) not very good at remembering > to notify the list when this has happened. The change that caused > your problem happened a little while ago, but it doesn't actually show > until you next have to run configure; then it breaks. p.s. Sorry! Chris ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@... - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel |
|
|
Re: Compile with debug issueOn Friday 03 July 2009, Chris Cannam wrote:
> bootstrap.sh regenerates the configure script from configure.ac and > acinclude.m4. You need to re-run it when one of those has changed. > > Unfortunately, we're (or at least, I'm) not very good at remembering > to notify the list when this has happened. I'm not very good at this either, though I try to make a habit of mentioning the fact in the commit log. This is why I wrote the distclean target too. After a distclean, you have to re-run bootstrap.sh, because it puts the tree back to a freshly checked out state as much as possible. It's probably a pretty safe practice anytime you notice any weird @VARIABLE@ garbage, just do a distclean and start over, and that ought to take care of it. -- D. Michael McIntyre ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@... - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel |
|
|
Re: Compile with debug issueOn Fri, Jul 3, 2009 at 10:18 PM, D. Michael
McIntyre<rosegarden.trumpeter@...> wrote: > This is why I wrote the distclean target too. After a distclean, you have to > re-run bootstrap.sh, because it puts the tree back to a freshly checked out > state as much as possible. We could always make a Makefile target depend on configure.ac and acinclude.m4. It wouldn't necessarily have to do anything much, besides print a message. Or it could just re-run bootstrap. Not proposing to write and, more importantly, test that myself at the moment, but it doesn't sound hard... Chris ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@... - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel |
| Free embeddable forum powered by Nabble | Forum Help |