From: Aere G. <Aere@Dvorak-Keyboards.com> - 2013-01-08 22:57:47
Attachments:
AereMidi-Keyboard-Demo.rg
AereMidi-Keyboard-Demo.mid
|
All: I have a continuing need to export Rosegarden (.rg) sequence files in standard MIDI format. Last week I reported that the version of Rosegarden that you get with Ubuntu 12.10 fails to export MIDI files. Today I downloaded the very latest subversion trunk version of Rosegarden, and tried the same test. It too, does not successfully output standard MIDI (.mid) files. It doesn't crash, and no error message is produced, but the exported standard MIDI file (when played with a MIDI player), is very different from the original Rosegarden (.rg) file. I have attached two files. The first is the Rosegarden (.rg) file loaded into the latest version of Rosegarden. You can play it, and look at it with an editor, such as the matrix editor. It exhibits no problems. The second file, is the standard MIDI (.mid) file exported from it, by the latest version of Rosegarden. You can import it (or load it) into Rosegarden, and play it, and/or look at it with an editor. This version looks fine, and will play fine. /However/, if you attempt to play that same file using a MIDI player (such as pmidi, or (in my case) the Java sequencer), the standard MIDI file is clearly very different from the original '.rg' file (many missing notes in the solo part). When you play it with pmidi, the following error message appears: "Left over note, finishing". -- Sincerely, Aere |
From: D. M. M. <ros...@gm...> - 2013-01-09 12:15:27
|
I have no clue what's going on with this, and would have little hope of fixing it if I tried. I reposted your email as a bug report and added your attachments. -- D. Michael McIntyre |
From: Tom B. (Tehom) <te...@pa...> - 2013-01-09 23:26:00
|
Aere: Thanks for the report and the files. I think I hear what's happening. It's not that notes are missing but that repeated notes get immediate noteoffs. It sounds like they are seeing their predecessor's noteoff just after their own noteOn. I will look at what the ordering is and what it needs to be. Possibly just changing the ordering of notes/noteoffs will fix it. Tom Breton (Tehom) |
From: Tom B. (Tehom) <te...@pa...> - 2013-01-10 01:52:20
|
> I think I hear what's happening. It's not that notes are missing but that > repeated notes get immediate noteoffs. It sounds like they are seeing > their predecessor's noteoff just after their own noteOn. > > I will look at what the ordering is and what it needs to be. Possibly > just changing the ordering of notes/noteoffs will fix it. I've found the problem and I think I can fix it. We were already producing noteOff/noteOn in the right order; I traced it. Then SortingInserter would resort the list and change the order of events. So despite initially making them in the right order, we were writing them in reverse order. This is definitely the cause; I just listened to a MIDI export that does the right thing. But what I have right now is not a fix, just a cheap trick with the MidiEvent comparison operator. I will code a real fix for it. I will also incorporate fixes for two minor bugs that I tripped over while diagnosing this: * http://home.roadrunner.com/~jgglatt/tech/midispec.htm tells me noteoffs should have a "dumb" velocity of 64, not 127. * Our conversion from timeT to RealTime wasn't consistent wrt segment delay. Tom Breton (Tehom) |
From: Tom B. (Tehom) <te...@pa...> - 2013-01-10 02:51:06
|
OK, I have coded a proper fix. SortingInserter now does the right thing. This changed it a lot internally but nothing else changed. As I mentioned, I will also (in separate commits) push fixes for two minor bugs I tripped over. Also tripped over something I don't understand: Why is MappedEventList a multiset rather than a list? Is it really searched more often than it's appended to or traversed? I don't want to fiddle with it, though. Tom Breton (Tehom) |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2013-01-10 03:57:46
|
On 01/09/2013 07:51 PM, Tom Breton (Tehom) wrote: > OK, I have coded a proper fix. SortingInserter now does the right thing. > This changed it a lot internally but nothing else changed. > > As I mentioned, I will also (in separate commits) push fixes for two minor > bugs I tripped over. > > Also tripped over something I don't understand: Why is MappedEventList a > multiset rather than a list? Is it really searched more often than it's > appended to or traversed? I don't want to fiddle with it, though. > > Tom Breton (Tehom) > > > Tom: Thank you very much for your amazingly quick work! By having committed it already, does that mean that if I were to get the latest trunk svn source, and rebuild it on my machine, that I would get the fixed version, or would I get the version of the last release? -- Sincerely, Aere |
From: Tom B. (Tehom) <te...@pa...> - 2013-01-10 04:00:57
|
> Thank you very much for your amazingly quick work! You're welcome! Getting a good bug report and demo files made it easier. > By having committed it already, does that mean that if I were to get the > latest trunk svn source, and rebuild it on my machine, that I would get > the fixed version, or would I get the version of the last release? As of about 10 minutes ago, the fixed version. Tom Breton (Tehom) |
From: D. M. M. <ros...@gm...> - 2013-01-10 10:06:17
|
On 01/09/2013 11:00 PM, Tom Breton (Tehom) wrote: > As of about 10 minutes ago, the fixed version. That was fast! I didn't see a commit note, but it looks like there was some big cleanup thing where you got rid of a bunch of unused parameters and other cruft in a couple dozen random places. Making warnings go away? How major is this .mid problem, and how important is this fix? Does it demand an immediate 13.01 release? If this was broken in 12.04, probably not. Unless encouraged otherwise, I'll keep aiming at 12.02 out toward the early part of February. -- D. Michael McIntyre |
From: Tom B. (Tehom) <te...@pa...> - 2013-01-10 17:47:52
|
> On 01/09/2013 11:00 PM, Tom Breton (Tehom) wrote: > >> As of about 10 minutes ago, the fixed version. > > That was fast! > > I didn't see a commit note, but it looks like there was some big cleanup > thing where you got rid of a bunch of unused parameters and other cruft > in a couple dozen random places. Making warnings go away? Yes, since I was on trunk (normally I'm dog-food-testing my experimental stuff), I cleaned up warnings that had escaped my eye last time. What remains is not so trivial to fix. > How major is this .mid problem, and how important is this fix? Does it > demand an immediate 13.01 release? I don't use MIDI export enough to say. The bug is that in MIDI export, repeated notes were clipped to essentially zero time. Tom Breton (Tehom) |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2013-01-10 15:52:10
|
On 01/10/2013 03:06 AM, D. Michael McIntyre wrote: > On 01/09/2013 11:00 PM, Tom Breton (Tehom) wrote: > >> As of about 10 minutes ago, the fixed version. > That was fast! > > I didn't see a commit note, but it looks like there was some big cleanup > thing where you got rid of a bunch of unused parameters and other cruft > in a couple dozen random places. Making warnings go away? > > How major is this .mid problem, and how important is this fix? Does it > demand an immediate 13.01 release? > > If this was broken in 12.04, probably not. Unless encouraged otherwise, > I'll keep aiming at 12.02 out toward the early part of February. > Michael: Without the ability to export '.mid' files, you can't provide MIDI files from Rosegarden, which can be played using MIDI players, or imported into other sequence editors. In music education, providing MIDI files is advantageous, because the software knows the notes in the music, and can compare it with what the student plays, and it can even figure out the key-signature. All of this wouldn't be possible with audio files (and audio files are orders-of-magnitude larger). I reported the problem because I had no way of exporting '.mid' files from Rosegarden. The first thing I tried was using Ubuntu-Studio 12.04. That didn't work either. Anticipating a long wait for a solution, I invested the time learning to do what I needed using MusE, which does work fine, but my expertise is in Rosegarden, so I'm essentially starting over if I use MusE. I'm very glad there is a quick solution. I will download it and re-build it, then try it again. Hopefully, it will work, and I can capitalize on my Rosegarden expertise. -- Sincerely, Aere |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2013-01-10 17:51:47
|
On 01/10/2013 08:52 AM, Aere Greenway wrote: > On 01/10/2013 03:06 AM, D. Michael McIntyre wrote: >> On 01/09/2013 11:00 PM, Tom Breton (Tehom) wrote: >> >>> As of about 10 minutes ago, the fixed version. >> That was fast! >> >> I didn't see a commit note, but it looks like there was some big cleanup >> thing where you got rid of a bunch of unused parameters and other cruft >> in a couple dozen random places. Making warnings go away? >> >> How major is this .mid problem, and how important is this fix? Does it >> demand an immediate 13.01 release? >> >> If this was broken in 12.04, probably not. Unless encouraged otherwise, >> I'll keep aiming at 12.02 out toward the early part of February. >> > Michael: > > Without the ability to export '.mid' files, you can't provide MIDI files > from Rosegarden, which can be played using MIDI players, or imported > into other sequence editors. > > In music education, providing MIDI files is advantageous, because the > software knows the notes in the music, and can compare it with what the > student plays, and it can even figure out the key-signature. All of > this wouldn't be possible with audio files (and audio files are > orders-of-magnitude larger). > > I reported the problem because I had no way of exporting '.mid' files > from Rosegarden. The first thing I tried was using Ubuntu-Studio > 12.04. That didn't work either. > > Anticipating a long wait for a solution, I invested the time learning to > do what I needed using MusE, which does work fine, but my expertise is > in Rosegarden, so I'm essentially starting over if I use MusE. > > I'm very glad there is a quick solution. > > I will download it and re-build it, then try it again. Hopefully, it > will work, and I can capitalize on my Rosegarden expertise. > > -- Sincerely, Aere > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122712 > _______________________________________________ > Rosegarden-devel mailing list > Ros...@li... - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel > All: It turns out, that what I tested-with in reporting the problem, was not the very latest version of Rosegarden (as I claimed). Instead, it was actually the latest release (12.12.25). This morning, I obtained the svn source for the latest Rosegarden code (I was careful to do that this time), revision 13178. Unfortunately, it did not build successfully. Thinking I was going to be using this new version of Rosegarden a lot, I did not include the parameter to turn-on debug. It got a long way into the build, then stopped with the following error: g++ -c -g0 -O2 -Wall -pipe -DNDEBUG -DBUILD_RELEASE -DNO_TIMING -DHAVE_LIBJACK -DHAVE_ALSA -DHAVE_LIBSNDFILE -DHAVE_LIRC -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtCore -I/usr/include/qt4 -I/usr/include/alsa -DLITTLE_ENDIAN=1 -D'VERSION="13.02"' -D'CODENAME="Handel"' -DUNSTABLE=1 -Isrc -D'BUILDKEY="0afb108718"' src/gui/application/LircClient.cpp -o src/gui/application/LircClient.o In file included from /usr/include/c++/4.6/algorithm:63:0, from /usr/include/qt4/QtCore/qglobal.h:68, from /usr/include/qt4/QtCore/qnamespace.h:45, from /usr/include/qt4/QtCore/qobjectdefs.h:45, from /usr/include/qt4/QtCore/qobject.h:47, from /usr/include/qt4/QtCore/QObject:1, from src/gui/application/LircClient.h:27, from src/gui/application/LircClient.cpp:22: /usr/include/c++/4.6/bits/stl_algo.h:1439:74: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-4.6/README.Bugs> for instructions. The bug is not reproducible, so it is likely a hardware or OS problem. make: *** [src/gui/application/LircClient.o] Error 1 Where I hadn't tried a non-debug version when I built it last time, I started the process over again (starting at the "make distclean" step. This time, I included the "--enable-debug" parameter. The build proceeded without error, getting past where it crashed before, but a few minutes after, terminated abnormally with the following error information: g++ -c -Wall -Woverloaded-virtual -Wextra -Wformat-nonliteral -Wformat-security -Winit-self -Wswitch-enum -g -pipe -DDEBUG -DBUILD_DEBUG -DWANT_TIMING -DHAVE_LIBJACK -DHAVE_ALSA -DHAVE_LIBSNDFILE -DHAVE_LIRC -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtCore -I/usr/include/qt4 -I/usr/include/alsa -DLITTLE_ENDIAN=1 -D'VERSION="13.02"' -D'CODENAME="Handel"' -DUNSTABLE=1 -Isrc -D'BUILDKEY="0afb108718"' src/gui/dialogs/AudioManagerDialog.cpp -o src/gui/dialogs/AudioManagerDialog.o In file included from /usr/include/qt4/QtGui/qabstractitemdelegate.h:46:0, from /usr/include/qt4/QtGui/qabstractitemview.h:48, from /usr/include/qt4/QtGui/qheaderview.h:45, from /usr/include/qt4/QtGui/QHeaderView:1, from src/gui/studio/DeviceManagerDialogUi.h:21, from src/gui/application/RosegardenMainWindow.h:29, from src/gui/editors/segment/TrackButtons.h:24, from src/gui/editors/segment/TrackEditor.h:23, from src/gui/application/RosegardenMainViewWidget.h:26, from src/gui/dialogs/AudioManagerDialog.cpp:39: /usr/include/qt4/QtGui/qstyleoption.h:701:20: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-4.6/README.Bugs> for instructions. The bug is not reproducible, so it is likely a hardware or OS problem. make: *** [src/gui/dialogs/AudioManagerDialog.o] Error 1 So I guess I'll have to keep learning how to use MusE, for the time being. -- Sincerely, Aere |
From: Tom B. (Tehom) <te...@pa...> - 2013-01-10 18:35:53
|
> It got a long way into the build, then stopped with the following error: > > g++ -c -g0 -O2 -Wall -pipe -DNDEBUG -DBUILD_RELEASE -DNO_TIMING > -DHAVE_LIBJACK -DHAVE_ALSA -DHAVE_LIBSNDFILE -DHAVE_LIRC > -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml > -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtCore > -I/usr/include/qt4 -I/usr/include/alsa -DLITTLE_ENDIAN=1 > -D'VERSION="13.02"' -D'CODENAME="Handel"' -DUNSTABLE=1 -Isrc > -D'BUILDKEY="0afb108718"' src/gui/application/LircClient.cpp -o > src/gui/application/LircClient.o > In file included from /usr/include/c++/4.6/algorithm:63:0, > from /usr/include/qt4/QtCore/qglobal.h:68, > from /usr/include/qt4/QtCore/qnamespace.h:45, > from /usr/include/qt4/QtCore/qobjectdefs.h:45, > from /usr/include/qt4/QtCore/qobject.h:47, > from /usr/include/qt4/QtCore/QObject:1, > from src/gui/application/LircClient.h:27, > from src/gui/application/LircClient.cpp:22: > /usr/include/c++/4.6/bits/stl_algo.h:1439:74: internal compiler error: > Segmentation fault > Please submit a full bug report, > with preprocessed source if appropriate. > See <file:///usr/share/doc/gcc-4.6/README.Bugs> for instructions. > The bug is not reproducible, so it is likely a hardware or OS problem. > make: *** [src/gui/application/LircClient.o] Error 1 That's odd. g++ (like gcc) is not supposed to crash no matter what you feed it. I looked at LircClient.cpp and LircClient.h and there is no actual RG code involved before #include <QObject>. Tom Breton (Tehom) |
From: Colin F. <col...@go...> - 2013-01-10 18:42:03
|
On 10/01/13 17:51, Aere Greenway wrote: > It got a long way into the build, then stopped with the following error: > > g++ -c -g0 -O2 -Wall -pipe -DNDEBUG -DBUILD_RELEASE -DNO_TIMING > -DHAVE_LIBJACK -DHAVE_ALSA -DHAVE_LIBSNDFILE -DHAVE_LIRC > -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml > -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtCore > -I/usr/include/qt4 -I/usr/include/alsa -DLITTLE_ENDIAN=1 > -D'VERSION="13.02"' -D'CODENAME="Handel"' -DUNSTABLE=1 -Isrc > -D'BUILDKEY="0afb108718"' src/gui/application/LircClient.cpp -o > src/gui/application/LircClient.o > In file included from /usr/include/c++/4.6/algorithm:63:0, > from /usr/include/qt4/QtCore/qglobal.h:68, > from /usr/include/qt4/QtCore/qnamespace.h:45, > from /usr/include/qt4/QtCore/qobjectdefs.h:45, > from /usr/include/qt4/QtCore/qobject.h:47, > from /usr/include/qt4/QtCore/QObject:1, > from src/gui/application/LircClient.h:27, > from src/gui/application/LircClient.cpp:22: > /usr/include/c++/4.6/bits/stl_algo.h:1439:74: internal compiler error: > Segmentation fault > Please submit a full bug report, > with preprocessed source if appropriate. > See <file:///usr/share/doc/gcc-4.6/README.Bugs> for instructions. > The bug is not reproducible, so it is likely a hardware or OS problem. > make: *** [src/gui/application/LircClient.o] Error 1 > > Where I hadn't tried a non-debug version when I built it last time, I > started the process over again (starting at the "make distclean" step. > This time, I included the "--enable-debug" parameter. > > The build proceeded without error, getting past where it crashed before, > but a few minutes after, terminated abnormally with the following error > information: > > g++ -c -Wall -Woverloaded-virtual -Wextra -Wformat-nonliteral > -Wformat-security -Winit-self -Wswitch-enum -g -pipe -DDEBUG > -DBUILD_DEBUG -DWANT_TIMING -DHAVE_LIBJACK -DHAVE_ALSA -DHAVE_LIBSNDFILE > -DHAVE_LIRC -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml > -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtCore > -I/usr/include/qt4 -I/usr/include/alsa -DLITTLE_ENDIAN=1 > -D'VERSION="13.02"' -D'CODENAME="Handel"' -DUNSTABLE=1 -Isrc > -D'BUILDKEY="0afb108718"' src/gui/dialogs/AudioManagerDialog.cpp -o > src/gui/dialogs/AudioManagerDialog.o > In file included from /usr/include/qt4/QtGui/qabstractitemdelegate.h:46:0, > from /usr/include/qt4/QtGui/qabstractitemview.h:48, > from /usr/include/qt4/QtGui/qheaderview.h:45, > from /usr/include/qt4/QtGui/QHeaderView:1, > from src/gui/studio/DeviceManagerDialogUi.h:21, > from src/gui/application/RosegardenMainWindow.h:29, > from src/gui/editors/segment/TrackButtons.h:24, > from src/gui/editors/segment/TrackEditor.h:23, > from src/gui/application/RosegardenMainViewWidget.h:26, > from src/gui/dialogs/AudioManagerDialog.cpp:39: > /usr/include/qt4/QtGui/qstyleoption.h:701:20: internal compiler error: > Segmentation fault > Please submit a full bug report, > with preprocessed source if appropriate. > See <file:///usr/share/doc/gcc-4.6/README.Bugs> for instructions. > The bug is not reproducible, so it is likely a hardware or OS problem. > make: *** [src/gui/dialogs/AudioManagerDialog.o] Error 1 > > So I guess I'll have to keep learning how to use MusE, for the time being. > Aere, This sort of error (especially if it's not consistent) can quite often be a symptom of flaky hardware - bad memory, failing or overstressed power supply, overheating, that kind of thing. You might be able to confirm this by booting into memtest - if that shows errors after running for a while, you've certainly got a hardware problem. You may very well have one even if it doesn't show an error, too, but it's certainly worth checking. Hope that helps, Colin. |
From: Ted F. <te...@te...> - 2013-01-10 18:30:34
|
On 01/10/2013 12:51 PM, Aere Greenway wrote: > This morning, I obtained the svn source for the latest Rosegarden code > (I was careful to do that this time), revision 13178. > Unfortunately, it did not build successfully. Just to be sure, try the following in the rg directory: $ svn update $ make distclean $ sh ./bootstrap.sh If you are running 32-bit Ubuntu: $ ./configure --enable-debug --with-qtlibdir=/usr/lib/i386-linux-gnu For 64-bit Ubuntu: $ ./configure --enable-debug --with-qtlibdir=/usr/lib/x86_64-linux-gnu Then finally try the make again $ make Hopefully that works. Ted. |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2013-01-10 18:36:33
|
On 01/10/2013 11:30 AM, Ted Felix wrote: > On 01/10/2013 12:51 PM, Aere Greenway wrote: >> This morning, I obtained the svn source for the latest Rosegarden code >> (I was careful to do that this time), revision 13178. >> Unfortunately, it did not build successfully. > Just to be sure, try the following in the rg directory: > > $ svn update > $ make distclean > $ sh ./bootstrap.sh > > If you are running 32-bit Ubuntu: > > $ ./configure --enable-debug --with-qtlibdir=/usr/lib/i386-linux-gnu > > For 64-bit Ubuntu: > > $ ./configure --enable-debug --with-qtlibdir=/usr/lib/x86_64-linux-gnu > > Then finally try the make again > > $ make > > Hopefully that works. > > Ted. > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122712 > _______________________________________________ > Rosegarden-devel mailing list > Ros...@li... - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel > Ted: Thanks for the ideas. I'll try it again this afternoon. It appears your WIKI on using the Eclipse IDE to work on Rosegarden (which I'm using, except I get the source the way you normally get the source, since I do not have a SourceForge user-ID), does not include the "svn update" step. -- Sincerely, Aere |
From: Ted F. <te...@te...> - 2013-01-10 23:46:09
|
On 01/10/2013 01:36 PM, Aere Greenway wrote: > It appears your WIKI on using the Eclipse IDE to work on Rosegarden > (which I'm using, except I get the source the way you normally get the > source, since I do not have a SourceForge user-ID), does not include the > "svn update" step. I just threw that in to make sure. Since you say you've already got the latest code, that should be a no-op. If your code is outdated, svn update will bring it up to the most current version in svn. Ted. |
From: D. M. M. <ros...@gm...> - 2013-01-10 22:11:25
|
On 01/10/2013 10:52 AM, Aere Greenway wrote: > I will download it and re-build it, then try it again. Hopefully, it > will work, and I can capitalize on my Rosegarden expertise. The trouble you're having building it could indeed be due to bad memory or something. The compiler crashing like that left and right is just completely bizarre, and something I've NEVER seen in 10 years here. Building Rosegarden does dial the stress level on your computer all the way up to the maximum; especially the link step. Ubuntu 32-bit or 64-bit? We don't normally provide binary packages, but a bunch of us have access to Ubuntu 12.04, and could probably come up with an exception in this case. Especially if the answer is 64-bit. -- D. Michael McIntyre |
From: H. S. T. <hs...@qu...> - 2013-01-10 22:33:21
|
On Thu, Jan 10, 2013 at 05:11:15PM -0500, D. Michael McIntyre wrote: > On 01/10/2013 10:52 AM, Aere Greenway wrote: > > > I will download it and re-build it, then try it again. Hopefully, > > it will work, and I can capitalize on my Rosegarden expertise. > > The trouble you're having building it could indeed be due to bad > memory or something. The compiler crashing like that left and right > is just completely bizarre, and something I've NEVER seen in 10 years > here. Building Rosegarden does dial the stress level on your computer > all the way up to the maximum; especially the link step. Nah, it's building mozilla or firefox that _really_ cranks it up to the max. Or my day job project, where a particular component takes *20* minutes to link (I'm not exaggerating -- every time it gets to that step, all disk I/O and RAM is completely hogged and X11 stops responding, so I just go take a stroll around the block and back). But yeah. If the compiler is crashing like that, it's very likely due to faulty RAM (or if you're very *very* unlucky, your motherboard malfunctioning). I've seen that on one of my old computers before. > Ubuntu 32-bit or 64-bit? We don't normally provide binary packages, > but a bunch of us have access to Ubuntu 12.04, and could probably come > up with an exception in this case. Especially if the answer is > 64-bit. [...] I have a 64-bit Debian system, which is compatible with 64-bit Ubuntu. I can try to make a binary if need be. T -- We are in class, we are supposed to be learning, we have a teacher... Is it too much that I expect him to teach me??? -- RL |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2013-01-10 23:55:17
|
On 01/10/2013 11:36 AM, Aere Greenway wrote: > On 01/10/2013 11:30 AM, Ted Felix wrote: >> On 01/10/2013 12:51 PM, Aere Greenway wrote: >>> This morning, I obtained the svn source for the latest Rosegarden code >>> (I was careful to do that this time), revision 13178. >>> Unfortunately, it did not build successfully. >> Just to be sure, try the following in the rg directory: >> >> $ svn update >> $ make distclean >> $ sh ./bootstrap.sh >> >> If you are running 32-bit Ubuntu: >> >> $ ./configure --enable-debug --with-qtlibdir=/usr/lib/i386-linux-gnu >> >> For 64-bit Ubuntu: >> >> $ ./configure --enable-debug --with-qtlibdir=/usr/lib/x86_64-linux-gnu >> >> Then finally try the make again >> >> $ make >> >> Hopefully that works. >> >> Ted. >> >> ------------------------------------------------------------------------------ >> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, >> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current >> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft >> MVPs and experts. ON SALE this month only -- learn more at: >> http://p.sf.net/sfu/learnmore_122712 >> _______________________________________________ >> Rosegarden-devel mailing list >> Ros...@li... - use the link below to unsubscribe >> https://lists.sourceforge.net/lists/listinfo/rosegarden-devel >> > Ted: > > Thanks for the ideas. > > I'll try it again this afternoon. > > It appears your WIKI on using the Eclipse IDE to work on Rosegarden > (which I'm using, except I get the source the way you normally get the > source, since I do not have a SourceForge user-ID), does not include the > "svn update" step. > Ted, and all: Good news! I followed your instructions, and the build succeeded this time. In the "make distclean" step this time, there were a lot more '.o' files removed than before. Or maybe I just got lucky this time.. Anyway, I now have a usable Rosegarden, with a lot of things fixed. I generated it on Ubuntu, tested it there, and also tested it on Lubuntu (my primary system). I am thinking that the executable can be used on any Ubuntu variant (with the same components/libraries installed), as long as it is the 32-bit version (which I generated). If that is a reasonable assumption, then it should work on my friend's Ubuntu system (which I will upgrade for him soon). I hope this is reasonable, because what comes with Ubuntu 12.04 has a lot of problems. -- Sincerely, Aere |
From: Ted F. <te...@te...> - 2013-01-11 00:27:48
|
On 01/10/2013 06:55 PM, Aere Greenway wrote: > I followed your instructions, and the build succeeded this time. The key thing that I noticed was that configure.ac had changed recently (I saw it go by when I did an svn update). That requires a complete rebuild from the very start (make distclean, etc...). Otherwise all sorts of very evil things can happen. Including compiler internal errors if things are really hosed. > I generated it on Ubuntu, tested it there, and also tested it on Lubuntu > (my primary system). I am thinking that the executable can be used on > any Ubuntu variant (with the same components/libraries installed), as > long as it is the 32-bit version (which I generated). Should work fine. I've had luck taking binaries to other distros as well. > If that is a reasonable assumption, then it should work on my friend's > Ubuntu system (which I will upgrade for him soon). I hope this is > reasonable, because what comes with Ubuntu 12.04 has a lot of problems. Certainly worth a try. Ted. |