Menu
▾
▴
jazzplusplus-devel — Discussion Forum for Jazz Developers
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
(189) |
Apr
(40) |
May
(8) |
Jun
(6) |
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
(13) |
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(4) |
Feb
(1) |
Mar
(3) |
Apr
|
May
(7) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
| 2006 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
(8) |
Oct
(19) |
Nov
(19) |
Dec
(7) |
| 2007 |
Jan
(6) |
Feb
(6) |
Mar
(3) |
Apr
(6) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
(1) |
| 2008 |
Jan
(19) |
Feb
(1) |
Mar
(40) |
Apr
(31) |
May
(174) |
Jun
(24) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(64) |
Dec
(17) |
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
(5) |
Mar
(1) |
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(11) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Pete S. <pst...@gm...> - 2008-05-18 16:07:26
|
DM = D.B. Moore DM> I'll check the tex2rtf with what I've got DM> (538 if I recall) and recheck later.... The latest is 542, but most of the changes are web related. DM> Where exactly are build instructions for this going? I was thinking on the tex2rtf page. DM> Connectivitively challenged, At least your service provider isn't blocking messages from sourceforge ;-) Hang in there... Pete |
|
From: Pete S. <pst...@gm...> - 2008-05-18 16:03:55
|
D.B. Moore wrote: PS = Pete Stieber PS>>>> I'll try to generate an example soon. PS>>>> I'll post when I'm done. DM = Donald B. Moore. DM>>> Good stuff, I'll check it out as soon as it's up... PS>> Refresh the documentation page in your web browser... PS>> PS>> http://jazzplusplus.sourceforge.net/documentation/ PS>> PS>> Scroll to the very bottom and click con the link PS>> in the line... PS>> PS>> Check out an ancient version of the Jazz++ online PS>> docs by visiting the manual page. PS>> PS>> That's the same content as you would see using PS>> the online help... PS>> PS>> Make sense? DM> ......yes actually....it does...however, just to be DM> sure, here's how I understand it right now... DM> DM> quintessentially. jazz.tex contains -all- the DM> documentation I'd say all of the user documentation. Subversion instructions, how to build the code... that should be on the web site. Once we have binary distributions, only user documentation (history of Jazz++, how to use Jazz++, the new MIDI how to content you are developing...) belongs in the tex file. DM> users can access these docs via a>jazz builtin DM> help context or b> anything else they wish to DM> view the docs generated in the jazz++ build DM> process, whatever format that might be... DM> (and we supply the various doc formats in the DM> binary packages) (which end up in DM> /usr/share/doc/jazz++ or similar) That sounds about right. DM> folks building from release tarballs get all DM> the various doc formats built/converted at DM> compile time. (if they don't want, say, the DM> pdf generation, we could have configure switches DM> like --disable-pdf etc....but my thinking is why DM> bother? the doc generation takes next to no build DM> time, we're not talking about saving oodles of DM> drivespace to justify doc generation exclusions, DM> so it builds the lot and users should be glad DM> and that's that ;-) Instead of --disable-pdf, the configure file will check to make sure pdflatex or pdftex exists on the machine, and complains if it doesn't. DM> the HTML docs generated from jazz.tex form the DM> online (web) documentation as well... Yep. The nice feature is we can use locally installed versions of these same files for the help used by the running Jazz++ binary. DM> the document currently at DM> /web/htdocs/documentation/index.php DM> gets revamped, and actually acts as a DM> contents/navigation page which refers back DM> to (link to) various sections of the HTML docs DM> generated from jazz.tex.... DM> DM> ..and in this way, content of website DM> documentation is (hopefully) DM> always in-sync with the current *release* DM> versions of Jazz++ as they become available.... DM> DM> Did I get it right? (^B I believe we are on the same page of the docs ;-) 1. You send me patches to jazz.tex and updated or new *.png files. 2. I put them in the src/HelpFiles directory. 3. I make sure everything builds properly. 4. I move the content over to the htdocs/manual directory 5. The required files are automatically provided with the distribution. 6. You review and generate new patches. GOTO 1 Pete |
|
From: D.B. M. <db...@ho...> - 2008-05-18 15:15:26
|
Greets, ---------------------------------------- > Date: Sat, 17 May 2008 18:57:46 -0700 > Subject: [jazzplusplus-devel] Tex2RTF build > > Donald, > > I guess we (I guess that means you since you are the documentation > animal ;-) need to generate build instructions for Tex2RTF. Here is how > I do it... > > Change directory to the jazzplusplus/tex2rtf directory and type > autoreconf. I usually checkout the entire svn tree, nit just the trunk, > so I can get the web and tex2rtf directories. > > $ autoreconf > > Create a directory called BuildTex2rtf in parallel with the jazzplusplus > directory. This is also in parallel with my Jazz++ build directory. > The one we call Build in the instructions. > > $ cd ../.. > $ mkdir BuildTex2rtf > > Now I run configure and make in the new directory. > > $ ../jazzplusplus/texx2rtf/configure > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > . > . Just confirming the build here on my custom 64bit thing (no 32bit_compat) ....seems to compile and work fine... Also fine on debian-4.0r1 on x86_32 Onwards ever onwards... Regards, Donald B _________________________________________________________________ Are you paid what you're worth? Find out: SEEK Salary Centre http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=OCT07_endtext_salary&_m=EXT |
|
From: D.B. M. <db...@ho...> - 2008-05-18 13:27:22
|
Greetings,
----------------------------------------
> Date: Sat, 17 May 2008 20:58:35 -0700
> Subject: Re: [jazzplusplus-devel] Tex2RTF build
>
> PS =Pete Stieber
> PS>> We only use the console or non-GUI version of
> PS>> tex2rtf in our builds so I copy
> PS>> BuildTex2rtf/src/tex2rtf to a bin directory
> PS>> under my wxWidgets installation.
>
... < snip>...
> PS>> To be "normal" we should have the user type
> PS>> "make install" as root, or use "sudo make install"
> PS>> for distributions that prefer sudo.
>
> DM> If it's going to go system-wide, yes, they'll need
> DM> root_priv or sudo
> DM>
> DM> If it's only going to be used at compile time
> DM> of Jazz++ buld process, it of course doesn't
> DM> need to go system-wide...
> DM>
> DM> In buildingwx, we use su for install
> DM> in buildingjazz we avoid root_priv
>
> Correct, but the user would need to specify --prefix=... just like in
> the Jazz++ build. I guess we could have them use TestInstall, but all
> of our (actually your ;-)) current instructions assume a
> jazzplusplus/trunk/jazz checkout instead of a jazzplusplus check out
> that would be required to obtain tex2rtf. We would always require two
> separate checkouts to achieve this.
>
...hmmm. Altering the docs is something that doesn't bother me.
(sometimes I think it's more preferable than changing other things)
That said, I possibly think of how many people actually try an svn
co & build overall....right now like. That answer doesn't matter - what
I'm saying is, once people get used to one way of doing things, it's
best not to throw'em a curve ball....(so we take our time here and
don't confuse them and come up with....'the plan'...| -)
I believe the current reality is quite sane, in as much as the current
instructions for an svn build of jazz++ have established a 'this is
how we do it, keeping the svn build stuff 'outside' the system tree
as much as we can....
....for now in these pre-release days, tex2rtf
should probably stay in this created 'bubble'. This way, one uses
pretty much the same configuration stage options for all things
coming from jazz++ svn....
....however, you're right when you talk about a separate tarball
release of tex2rtf itself. If this were the case, I would ask ;
Does the svn build *really* need a tex2rtf linked against the
custom-wx build libs to give us the functionality (of tex2rtf)
we need (for the jazz++ build process)?
If not, then for sure a release of tex2rtf should be made
available ASAP. Then it really *is* 'normal'...ie; download,
unpack, ./configure --prefix=/usr ; make ; su make install
et_voila. It'll link against user's system wx-libs, be in $PATH
and become a small dependency of jazz++ itself. Of course,
if we can get binary packages of this happening, then all
the better....
Imagining a time when you had the time to make tex2rtf
a project of it's own, that's no big deal to link across
to (if you ever find that time ;-)...and remember, we do
have the tex2rtf page to assert all this to the world, and
something like "going to be a project of it's own one day
when I get time to work on it more, but for now a
functional tarball of this utility is being released on
the sourceforge download area for jazz++'..blabla, works
for me...
> DM> Going by your outlay here, the process should
> DM> be wx->tex2rtf->jazz++
>
> Correct. wx is required for tex2rtf. Both wx and tex2rtf are required
> for Jazz++.
>
> DM> Is the plan to have a *release* tarball with all
> DM> this automated?
>
> The release tarball for Jazz++ will not include any tex2rtf stuff other
> than the help files it generates. We may want to generate a separate
> tarball for tex2rtf. Tex2RTF really should be a separate project, but
> I'm having a difficult time working on Jazz++ not alone Tex2RTF...
>
....Uh-huh, and release pkgs are likewise...and of course,
the source tarball has everything except possibly tex2rtf,
(which is available separately), right? (this is me lobbying
my own position & requirements ;-)
> DM> I'll guess yes...do we offer users a switch in release
> DM> form? I'm thinking --enable-tex2rtf builds and installs
> DM> tex2rtf system wide.
>
> I think the last section of reply helps explain what I'm thinking.
>
> DM> I'm in the state of Queensland or +10 (but take that
> DM> with a grain of salt, as I tend to keep rather peculiar
> DM> hours)
>
> Understood. Now I can pull up something like
>
> http://www.worldtimezone.com/
>
> and figure out how "fresh" you are ;-)
>
> It's about 9:00 PM here now.
>
> BTW, I can't thank you enough for all of the help!!!!!
>
It's my pleasure, I'm glad you like my input...output.. ;-)
Regards,
Donald B
_________________________________________________________________
Are you paid what you're worth? Find out: SEEK Salary Centre
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=OCT07_endtext_salary&_m=EXT
|
|
From: D.B. M. <db...@ho...> - 2008-05-18 09:05:44
|
Greetings, Btw, we had one nasty storm here last night, and since then the ADSL here has reverted to pre-14.4 PSTN mode... ...probably a service pit full of water is my guess... a good keyer could probably morse faster... eventually my local svn will finish updating.... I'll check the tex2rtf with what I've got (538 if I recall) and recheck later.... Where exactly are build instructions for this going? Connectivitively challenged, Donald B _________________________________________________________________ Be part of history. Take part in Australia's first e-mail archive with Email Australia. http://emailaustralia.ninemsn.com.au |
|
From: D.B. M. <db...@ho...> - 2008-05-18 06:46:50
|
Greets, ---------------------------------------- > Date: Sat, 17 May 2008 21:59:18 -0700 > Subject: Re: [jazzplusplus-devel] Doccumentation -- a scratchpad of thoughts > > PS = Pete Stieber > PS>> I'll try to generate an example soon. > PS>> I'll post when I'm done. > > DM = Donald B. Moore. > DM> Good stuff, I'll check it out as soon as it's up... > > Refresh the documentation page in your web browser... > > http://jazzplusplus.sourceforge.net/documentation/ > > Scroll to the very bottom and click con the link in the line... > > Check out an ancient version of the Jazz++ online docs by visiting the > manual page. > > That's the same content as you would see using the online help... > > Make sense? > ......yes actually....it does...however, just to be sure, here's how I understand it right now... quintessentially. jazz.tex contains -all- the documentation users can access these docs via a>jazz builtin help context or b> anything else they wish to view the docs generated in the jazz++ build process, whatever format that might be... (and we supply the various doc formats in the binary packages) (which end up in /usr/share/doc/jazz++ or similar) folks building from release tarballs get all the various doc formats built/converted at compile time. (if they don't want, say, the pdf generation, we could have configure switches like --disable-pdf etc....but my thinking is why bother? the doc generation takes next to no build time, we're not talking about saving oodles of drivespace to justify doc generation exclusions, so it builds the lot and users should be glad and that's that ;-) the HTML docs generated from jazz.tex form the online (web) documentation as well... the document currently at /web/htdocs/documentation/index.php gets revamped, and actually acts as a contents/navigation page which refers back to (link to) various sections of the HTML docs generated from jazz.tex.... ..and in this way, content of website documentation is (hopefully) always in-sync with the current *release* versions of Jazz++ as they become available.... Did I get it right? (^B Regards, Donald B _________________________________________________________________ Be part of history. Take part in Australia's first e-mail archive with Email Australia. http://emailaustralia.ninemsn.com.au |
|
From: D.B. M. <db...@ho...> - 2008-05-18 05:11:57
|
---------------------------------------- > Date: Sat, 17 May 2008 21:44:53 -0700 > Subject: Re: [jazzplusplus-devel] Tex2RTF build > > PS = Pete Stieber > PS>> BTW, what time zone are you in (+8, +9, +10, or +11)? > PS>> I'm in the state of California in the U.S.A or -8. > > KC = Kevin Cosgrove > KC> FWIW, I'm in your timezone, in Portland OR. > > I'm on the central coast... Lompoc, CA. > > Thanks for the info Kevin. It's good to know someone might be awake > when I am. Although if Donald has really odd hour, he might be awake > too ;-) No might about it...I am certainly nearly always awake then. It's quieter at night....better for the concentration... > He certainly is keeping me busy with his documentation > updates... But it's a good busy ;-) > That's reassuring....I always worry about (and like to avoid) a situation where my output -burdens- people...hit me with a stick or something if you need to ;-) Regards, Donald B _________________________________________________________________ Are you paid what you're worth? Find out: SEEK Salary Centre http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=OCT07_endtext_salary&_m=EXT |
|
From: Pete S. <pst...@gm...> - 2008-05-18 04:59:22
|
PS = Pete Stieber PS>> I'll try to generate an example soon. PS>> I'll post when I'm done. DM = Donald B. Moore. DM> Good stuff, I'll check it out as soon as it's up... Refresh the documentation page in your web browser... http://jazzplusplus.sourceforge.net/documentation/ Scroll to the very bottom and click con the link in the line... Check out an ancient version of the Jazz++ online docs by visiting the manual page. That's the same content as you would see using the online help... Make sense? Pete |
|
From: Pete S. <pst...@gm...> - 2008-05-18 04:44:56
|
PS = Pete Stieber PS>> BTW, what time zone are you in (+8, +9, +10, or +11)? PS>> I'm in the state of California in the U.S.A or -8. KC = Kevin Cosgrove KC> FWIW, I'm in your timezone, in Portland OR. I'm on the central coast... Lompoc, CA. Thanks for the info Kevin. It's good to know someone might be awake when I am. Although if Donald has really odd hour, he might be awake too ;-) He certainly is keeping me busy with his documentation updates... But it's a good busy ;-) Pete |
|
From: Pete S. <pst...@gm...> - 2008-05-18 04:41:45
|
PS = Pete Stieber PS>> I just received an announcement about PS>> "Mandriva Linux 2008 Spring". I take it PS>> this would be newer than the 2008.0 version PS>> I loaded. Is that true? KC = Kevin Cosgrove KC> 2008 Spring is also known as 2008.1. Yeah. I started downloading the DVD. The download is 80% complete with about 43 min to go. PS>> Should I give it a try? KC> I like 2008.1. The only trouble I had with it KC> was that I had to blacklist a couple things in KC> the modules startup stuff. That computer is KC> turned off right now, or I could tell you exactly KC> what I did. It works well. I don't know how it KC> does for jazz tho. I could find out. Would you KC> rather me try to build jazz there first? Since I'm having a heck of a time with 2008.0, I'm going to 1. Attempt to upgrade the BIOS for the ASUS A7N8X Deluxe MB I'm running it on, but to be honest, I've run Win 98, 2000, XP, Fedora 3, 4, and 5 without the need for this, so I doubt it will help. 2. Wipe out the disk that has 2008.0 with 2008.1 and start over. I tried to use that disk today and it refuses to recognize my USB keyboard/mouse. The POST recognized it, but not 2008.0. If you could give it a try this would be greatly appreciated. I can't remember if I've mentioned this, but I've ordered a drive bay for my new Dell box plus 5 SATA drive cases so I can swap out drives to try different OSs. Fedora 9 is out and I want to give it a try too. 1. Windows XP 2. Windows Vista 3. Mandriva 4. Ubuntu 5. Fedora I figured VMware would have problems with sound drivers. Thanks Kevin, Pete |
|
From: Kevin C. <ke...@co...> - 2008-05-18 04:06:06
|
On 17 May 2008 at 18:57, Pete Stieber <pst...@gm...> wrote: > BTW, what time zone are you in (+8, +9, +10, or +11)? I'm in the state > of California in the U.S.A or -8. FWIW, I'm in your timezone, in Portland OR. -- Kevin |
|
From: Kevin C. <ke...@co...> - 2008-05-18 04:04:38
|
On 17 May 2008 at 15:02, Pete Stieber <pst...@gm...> wrote: > I just received an announcement about "Mandriva Linux 2008 Spring". I > take it this would be newer that the 2008.0 version I loaded. Is that true? 2008 Spring is also known as 2008.1. > Should I give it a try? I like 2008.1. The only trouble I had with it was that I had to blacklist a couple things in the modules startup stuff. That computer is turned off right now, or I could tell you exactly what I did. It works well. I don't know how it does for jazz tho. I could find out. Would you rather me try to build jazz there first? Thanks.... -- Kevin |
|
From: Pete S. <pst...@gm...> - 2008-05-18 03:58:39
|
PS =Pete Stieber PS>> We only use the console or non-GUI version of PS>> tex2rtf in our builds so I copy PS>> BuildTex2rtf/src/tex2rtf to a bin directory PS>> under my wxWidgets installation. DM = D.B. Moore DM> ....where exactly did you copy the file to? DM> DM> Here? (relative to linux) /usr/local/wx287/bin Wherever you have wx-config installed. $ which wx-config /usr/local/wx287/bin/wx-config On one machine I'm using... $ which wx-config /home/pstieber/wxBuilds/wx287/bin/wx-config On another. The which command uses you PATH environment variable like bash would. PS>> To be "normal" we should have the user type PS>> "make install" as root, or use "sudo make install" PS>> for distributions that prefer sudo. DM> If it's going to go system-wide, yes, they'll need DM> root_priv or sudo DM> DM> If it's only going to be used at compile time DM> of Jazz++ buld process, it of course doesn't DM> need to go system-wide... DM> DM> In buildingwx, we use su for install DM> in buildingjazz we avoid root_priv Correct, but the user would need to specify --prefix=... just like in the Jazz++ build. I guess we could have them use TestInstall, but all of our (actually your ;-)) current instructions assume a jazzplusplus/trunk/jazz checkout instead of a jazzplusplus check out that would be required to obtain tex2rtf. We would always require two separate checkouts to achieve this. DM> Going by your outlay here, the process should DM> be wx->tex2rtf->jazz++ Correct. wx is required for tex2rtf. Both wx and tex2rtf are required for Jazz++. DM> Is the plan to have a *release* tarball with all DM> this automated? The release tarball for Jazz++ will not include any tex2rtf stuff other than the help files it generates. We may want to generate a separate tarball for tex2rtf. Tex2RTF really should be a separate project, but I'm having a difficult time working on Jazz++ not alone Tex2RTF... DM> I'll guess yes...do we offer users a switch in release DM> form? I'm thinking --enable-tex2rtf builds and installs DM> tex2rtf system wide. I think the last section of reply helps explain what I'm thinking. DM> I'm in the state of Queensland or +10 (but take that DM> with a grain of salt, as I tend to keep rather peculiar DM> hours) Understood. Now I can pull up something like http://www.worldtimezone.com/ and figure out how "fresh" you are ;-) It's about 9:00 PM here now. BTW, I can't thank you enough for all of the help!!!!! Pete |
|
From: D.B. M. <db...@ho...> - 2008-05-18 03:49:52
|
---------------------------------------- > Date: Sat, 17 May 2008 20:05:31 -0700 > Subject: Re: [jazzplusplus-devel] Doccumentation -- a scratchpad of thoughts > > DM = D.B. Moore > DM> Call it sentimentality on my part if you like, but > DM> I figure a copy of the original jazz.tex file should > DM> always remain, in tact, for historical purposes... > > It will because it us under version control. On your Linux box, try the > following command in the jazzplusplus/trunk/jazz/src/HelpFiles directory... > > $ svn log jazz.tex > > This lists all of the log messages associates with jazz.tex. Note the > revision numbers. Let's say you wanted to retrieve the original version > from Subversion. That would be version... 56. Just for fun, change > directory to your home directory and retrieve that version of jazz.tex > using... > > $ cd > $ mkdir Junk > $ svn co -r 56 > https://jazzplusplus.svn.sourceforge.net/svnroot/jazzplusplus/trunk/jazz/src/HelpFiles > Junk > > That last line should all be on one line. Know you have the original, > 486 and all, mentioned in tex2rtf. I'm keeping a copy of the pdf > generated by Tex2RTF around for a reference. > Great, thanks for the brief svn tute Pete...(and for remembering I'm new to svn....;-) > DM> Anyhow, reworking jazz.tex is almost tantamount > DM> to a rewrite. I've got no problem with that, > DM> and for sure some passages of the old text > DM> may find their way into the new draft....but > DM> ....are we happy with the formal and layout of > DM> the old jazz.tex documentation? > > Here's how I look at it. You are doing a fabulous job with the docs. > Feel free to re-write as you see fit. When it comes to Jazz++ > functionality, assume we are trying to recreate what the old version > did. I'm sure this is documented in the old version. I have changed a > few things (I want to use my new knob control instead of sliders... see > the Metronome dialog), but not much. > okay, thanks for the pointers > DM> A lot of the htdocs are near a point where they'll be > DM> 'frozen' for a time - they probably won't change until > DM> the code reaches a point closer to an 'official' release. > > Exactly. > > DM> The reason I concluded to just continue adding to the > DM> web/htdocs/documentation path, was to merely make these > DM> additions 'visible', rather than obscured in jazz.tex > DM> right now, ....because we havn't discussed a plan here, > DM> or how things will be done....etc etc etc.. > > That makes sense, but here's what I was thinking... > > I simply post the HTML output of the Tex2RTF build on the web site and > you link to it. It will definitely look different than the main web > site, but it should. I concur.... > > I'll try to generate an example soon. I'll post when I'm done. > > Pete > Good stuff, I'll check it out as soon as it's up... Regards, Donald B _________________________________________________________________ Never miss another e-mail with Hotmail on your mobile. http://www.livelife.ninemsn.com.au/article.aspx?id=343869 |
|
From: D.B. M. <db...@ho...> - 2008-05-18 03:25:47
|
---------------------------------------- > Date: Sat, 17 May 2008 19:04:56 -0700 > Subject: Re: [jazzplusplus-devel] Thoughts about the linux kernel - observed trends > > RV = Robert Vogel > RV> Hi Donald, > RV> > RV> Your mp3 sounds pretty good to me...except it's > RV> a little scratchy. Perhaps that could be filtered out? > >PS=Pete >PS=I though that was illustrating the latency problem. Am I incorrect? > Absolutely not, you're spot on Pete...... Bob, that 'scratchy' sound you refer to **IS** an example of softsynth latency problems. It is in no way the same sound artifact as one would hear replaying an old scratched vinyl record - and it cannot be filtered out. (one can see all this if the waveform is examined in audacity) > RV> Jazz++ performs pretty well with a small number of > RV> tracks, but I did notice if rendering a 16 track > RV> file it does break up some. > > Hey Robert. By default, the instructions walk you through a debug > build. At the configure step, remove the --enable-debug option and see > if that helps. Is this with external MIDI synth? It'd be interesting to know if the softsynth gags on 16tracks...I'll check this later myself > > RV> The metronome seems to work now...although the > RV> sound is not right. Definitely not a drum sound. > > Try the "Settings | Metronome..." dialog to change the sound used. > > > Pete Regards, Donald B _________________________________________________________________ It's simple! Sell your car for just $30 at CarPoint.com.au http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%2Ecom%2Fcgi%2Dbin%2Fa%2Fci%5F450304%2Fet%5F2%2Fcg%5F801459%2Fpi%5F1004813%2Fai%5F859641&_t=762955845&_r=tig_OCT07&_m=EXT |
|
From: D.B. M. <db...@ho...> - 2008-05-18 03:09:50
|
Greets, Pete wrote; ---------------------------------------- > Date: Sat, 17 May 2008 18:57:46 -0700 > Subject: [jazzplusplus-devel] Tex2RTF build > > Donald, > > I guess we (I guess that means you since you are the documentation > animal ;-) need to generate build instructions for Tex2RTF. Here is how > I do it... > > Change directory to the jazzplusplus/tex2rtf directory and type > autoreconf. I usually checkout the entire svn tree, nit just the trunk, > so I can get the web and tex2rtf directories. > > $ autoreconf > > Create a directory called BuildTex2rtf in parallel with the jazzplusplus > directory. This is also in parallel with my Jazz++ build directory. > The one we call Build in the instructions. > > $ cd ../.. > $ mkdir BuildTex2rtf > > Now I run configure and make in the new directory. > > $ ../jazzplusplus/texx2rtf/configure > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > . > . > . > config.status: creating src/Makefile > config.status: creating src/config.h > config.status: executing depfiles commands > [pstieber@maggie BuildTex2rtf]$ make 2>&1 | tee BuildLog > Making all in src > make[1]: Entering directory `/home/pstieber/Jazz++/BuildTex2rtf/src' > make all-am > make[2]: Entering directory `/home/pstieber/Jazz++/BuildTex2rtf/src' > g++ -DHAVE_CONFIG_H -I. -I../../jazzplusplus/tex2rtf/src -Wall > -Wno-unknown-pragmas > -I/usr/local/wx287/lib/wx/include/gtk2-ansi-release-static-2.8 > -I/usr/local/wx287/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES > -D__WXGTK__ -DNDEBUG -O0 -MT htmlutil.o -MD -MP -MF .deps/htmlutil.Tpo > -c -o htmlutil.o ../../jazzplusplus/tex2rtf/src/htmlutil.cpp > . > . > . > 0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 > -lXinerama -lXxf86vm -lSM -lpng -ljpeg -ltiff -lexpat -lwxregex-2.8 -lz > -ldl -lm > make[2]: Leaving directory `/home/pstieber/Jazz++/BuildTex2rtf/src' > make[1]: Leaving directory `/home/pstieber/Jazz++/BuildTex2rtf/src' > make[1]: Entering directory `/home/pstieber/Jazz++/BuildTex2rtf' > make[1]: Nothing to be done for `all-am'. > make[1]: Leaving directory `/home/pstieber/Jazz++/BuildTex2rtf' > Yep, I'll verify this again (did a similar thing here myself a day or two back) and make sure it's all sane... > We only use the console or non-GUI version of tex2rtf in our builds so I > copy BuildTex2rtf/src/tex2rtf to a bin directory under my wxWidgets > installation. ....where exactly did you copy the file to? Here? (relative to linux) /usr/local/wx287/bin > > To be "normal" we should have the user type "make install" as root, or > use "sudo make install" for distributions that prefer sudo. > If it's going to go system-wide, yes, they'll need root_priv or sudo If it's only going to be used at compile time of Jazz++ buld process, it of course doesn't need to go system-wide... In buildingwx, we use su for install in buildingjazz we avoid root_priv Going by your outlay here, the process should be wx->tex2rtf->jazz++ Is the plan to have a *release* tarball with all this automated? I'll guess yes...do we offer users a switch in release form? I'm thinking --enable-tex2rtf builds and installs tex2rtf system wide no switch = build tex2rtf in tree only for the jazz++ doc conversions None of this matters right now, and *YES* I do recognize the stance might be to put tex2rtf out there into the world and I'm all for that.... ..but whenever that word "normal" stares me in the face...well, I have got to speculate what's normal... ;-) > Pete > > BTW, what time zone are you in (+8, +9, +10, or +11)? I'm in the state > of California in the U.S.A or -8. > I'm in the state of Queensland or +10 (but take that with a grain of salt, as I tend to keep rather peculiar hours) Regards, Donald B _________________________________________________________________ Never miss another e-mail with Hotmail on your mobile. http://www.livelife.ninemsn.com.au/article.aspx?id=343869 |
|
From: Pete S. <pst...@gm...> - 2008-05-18 03:05:36
|
DM = D.B. Moore DM> Call it sentimentality on my part if you like, but DM> I figure a copy of the original jazz.tex file should DM> always remain, in tact, for historical purposes... It will because it us under version control. On your Linux box, try the following command in the jazzplusplus/trunk/jazz/src/HelpFiles directory... $ svn log jazz.tex This lists all of the log messages associates with jazz.tex. Note the revision numbers. Let's say you wanted to retrieve the original version from Subversion. That would be version... 56. Just for fun, change directory to your home directory and retrieve that version of jazz.tex using... $ cd $ mkdir Junk $ svn co -r 56 https://jazzplusplus.svn.sourceforge.net/svnroot/jazzplusplus/trunk/jazz/src/HelpFiles Junk That last line should all be on one line. Know you have the original, 486 and all, mentioned in tex2rtf. I'm keeping a copy of the pdf generated by Tex2RTF around for a reference. DM> Anyhow, reworking jazz.tex is almost tantamount DM> to a rewrite. I've got no problem with that, DM> and for sure some passages of the old text DM> may find their way into the new draft....but DM> ....are we happy with the formal and layout of DM> the old jazz.tex documentation? Here's how I look at it. You are doing a fabulous job with the docs. Feel free to re-write as you see fit. When it comes to Jazz++ functionality, assume we are trying to recreate what the old version did. I'm sure this is documented in the old version. I have changed a few things (I want to use my new knob control instead of sliders... see the Metronome dialog), but not much. DM> A lot of the htdocs are near a point where they'll be DM> 'frozen' for a time - they probably won't change until DM> the code reaches a point closer to an 'official' release. Exactly. DM> The reason I concluded to just continue adding to the DM> web/htdocs/documentation path, was to merely make these DM> additions 'visible', rather than obscured in jazz.tex DM> right now, ....because we havn't discussed a plan here, DM> or how things will be done....etc etc etc.. That makes sense, but here's what I was thinking... I simply post the HTML output of the Tex2RTF build on the web site and you link to it. It will definitely look different than the main web site, but it should. I'll try to generate an example soon. I'll post when I'm done. Pete |
|
From: D.B. M. <db...@ho...> - 2008-05-18 02:27:24
|
Greetings, As Pete said - "I was hoping this stuff would end up in jazz.tex" On the night, I had thought "this stuff should go in jazz.tex" I read through jazz.tex ..all of it. It's worth doing, it remarks a far gone time...(even if that was less than 20 years ago). Shiny pearls like this ; For MIDI-only operation a 486 CPU (or equivalent) is sufficient in most cases. For satisfactory audio operation a Pentium CPU with 32 MBytes RAM is recommended. Call it sentimentality on my part if you like, but I figure a copy of the original jazz.tex file should always remain, in tact, for historical purposes... Anyhow, reworking jazz.tex is almost tantamount to a rewrite. I've got no problem with that, and for sure some passages of the old text may find their way into the new draft....but....are we happy with the formal and layout of the old jazz.tex documentation? A lot of the htdocs are near a point where they'll be 'frozen' for a time - they probably won't change until the code reaches a point closer to an 'official' release. The reason I concluded to just continue adding to the web/htdocs/documentation path, was to merely make these additions 'visible', rather than obscured in jazz.tex right now, ....because we havn't discussed a plan here, or how things will be done....etc etc etc.. What Pete said is right -- all this stuff *should* be in jazz.tex, the htdocs should be generated from that (to ensure that consistency between online and in-tree documentation).... Comments please, how are we going to approach this? Regards, Donald B _________________________________________________________________ Never miss another e-mail with Hotmail on your mobile. http://www.livelife.ninemsn.com.au/article.aspx?id=343869 |
|
From: Pete S. <pst...@gm...> - 2008-05-18 02:04:59
|
RV = Robert Vogel RV> Hi Donald, RV> RV> Your mp3 sounds pretty good to me...except it's RV> a little scratchy. Perhaps that could be filtered out? I though that was illustrating the latency problem. Am I incorrect? RV> Jazz++ performs pretty well with a small number of RV> tracks, but I did notice if rendering a 16 track RV> file it does break up some. Hey Robert. By default, the instructions walk you through a debug build. At the configure step, remove the --enable-debug option and see if that helps. RV> The metronome seems to work now...although the RV> sound is not right. Definitely not a drum sound. Try the "Settings | Metronome..." dialog to change the sound used. Pete |
|
From: Pete S. <pst...@gm...> - 2008-05-18 01:57:50
|
Donald, I guess we (I guess that means you since you are the documentation animal ;-) need to generate build instructions for Tex2RTF. Here is how I do it... Change directory to the jazzplusplus/tex2rtf directory and type autoreconf. I usually checkout the entire svn tree, nit just the trunk, so I can get the web and tex2rtf directories. $ autoreconf Create a directory called BuildTex2rtf in parallel with the jazzplusplus directory. This is also in parallel with my Jazz++ build directory. The one we call Build in the instructions. $ cd ../.. $ mkdir BuildTex2rtf Now I run configure and make in the new directory. $ ../jazzplusplus/texx2rtf/configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p . . . config.status: creating src/Makefile config.status: creating src/config.h config.status: executing depfiles commands [pstieber@maggie BuildTex2rtf]$ make 2>&1 | tee BuildLog Making all in src make[1]: Entering directory `/home/pstieber/Jazz++/BuildTex2rtf/src' make all-am make[2]: Entering directory `/home/pstieber/Jazz++/BuildTex2rtf/src' g++ -DHAVE_CONFIG_H -I. -I../../jazzplusplus/tex2rtf/src -Wall -Wno-unknown-pragmas -I/usr/local/wx287/lib/wx/include/gtk2-ansi-release-static-2.8 -I/usr/local/wx287/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -DNDEBUG -O0 -MT htmlutil.o -MD -MP -MF .deps/htmlutil.Tpo -c -o htmlutil.o ../../jazzplusplus/tex2rtf/src/htmlutil.cpp . . . 0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 -lXinerama -lXxf86vm -lSM -lpng -ljpeg -ltiff -lexpat -lwxregex-2.8 -lz -ldl -lm make[2]: Leaving directory `/home/pstieber/Jazz++/BuildTex2rtf/src' make[1]: Leaving directory `/home/pstieber/Jazz++/BuildTex2rtf/src' make[1]: Entering directory `/home/pstieber/Jazz++/BuildTex2rtf' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `/home/pstieber/Jazz++/BuildTex2rtf' We only use the console or non-GUI version of tex2rtf in our builds so I copy BuildTex2rtf/src/tex2rtf to a bin directory under my wxWidgets installation. To be "normal" we should have the user type "make install" as root, or use "sudo make install" for distributions that prefer sudo. Pete BTW, what time zone are you in (+8, +9, +10, or +11)? I'm in the state of California in the U.S.A or -8. |
|
From: Robert V. <vo...@ct...> - 2008-05-18 01:47:36
|
On Fri, 2008-05-16 at 05:11 +0000, D.B. Moore wrote: > Greets, > > > Date: Thu, 15 May 2008 22:31:41 -0400 > > Subject: Re: [jazzplusplus-devel] Thoughts about the linux kernel - observed trends > > > > On Fri, 2008-05-16 at 02:03 +0000, D.B. Moore wrote: > >> Greetings, > >> > > (snip) > >> > >> > >> I think what I eventually might do, is put some sound files up > >> on our site, which **audibly** demonstrate to users artifacts > >> of sound quality directly related to linux kernel latency issues. > >> > >> That'd be about the best thing to do...IMHO....to help users > >> conclude whether or not they need a better (faster) kernel > >> for their setup. Hope this helps... > >> > >> Regards, > >> > >> Donald B > >> > >> > > > > I tried Jazz++ a couple of ways, both quite good: > > > > * my ux16 USB midi interface hitches to a Motif ES8 which together has > > excellent sound quality. > > > > Good to hear...(another pun ;) No timing issues? Don't be scared to be verbose > if what you're doing relates directly to Jazz++'s performance in the real world. > > > > * The software synth I like is ZynAddSubFX produces its own pleasing > > sound. I use Hydrogen for its drum set. Rosegarden does this, and I > > think Jazz++ can too. (I didn't run Hydrogen from it yet.) > > If you do, be sure to let us know if it works okay. I do know about zyn & lv2, > in fact I've just installed that kit here on my box - but as is common with a lot > of us here, I haven't yet found the time to play with it....but I will get to it... > > > > > Probably I need to modify the kernel to hear how good the native midi > > is. > > > > You just know I'm going to ask what makes you think that, don't you? ;-) > > > Subsequent to my previous posting, and carrying my notion forward > about putting soundfiles somewhere that people can listen to and then > conclude whether or not they have linux kernel latency issues with their > softsynth setup.... > > Pete, can you put this attached mp3 file in..'some appropriate location' > for me please? I'm thinking about a yet undiscussed 'FAQ' area, and > anywhere else kernel latency issues are touched on, it'd be handy to > be able to link back to this location...I'm sure you get the idea here ;-) > > Bob, listen to the attached mp3 and the sound of the softsynth loosing > the plot entirely, until timelag detection code realizes something gone > terribly wrong and realigns the datastream with where the hardware > is 'right now' as it were. . > > This was rendered a few years ago now on a x86_32 with an AMD > athlon 3000+ CPU using AMS on one of my own linux builds. IIRC > the timing glitche started out as a 0.002 second deviance, rising to > 0.09 second deviance before the code kicked itself in the pants. > > Remember I said this area was a minefield?...yeah, well some of these > timing related issues are not entirely the kernel or the software's > fault -- it can actually be related to the motherboard chipset being used > and/or the state of play with a particular chipset's driver (in linux). > A good example is what you hear in this mp3, which is going to be > heard a -lot- more by folks with a VIA chipset mainboard (x86), > because this is a known issue with linux/VIA chipsets, and it doesn't > affect just the things we're talking about here - DMA and interrupt > issues with VIA chipsets can plague the video, fb, any manner of things.. > > ....and, just as an example of HOW weird and obscure this can get, > I have a VIA epia-tc10000 board here that initially gave me all sorts > of heck, and I did hours and hours of mucking around with it before > I discovered the effective fix was actually to email the VIA techsupp > crowd about it, who replied with a link to a beta version BIOS image > ...so the problem was in BIOS all along, and seemingly only affected > use with a linux kernel...go figure... > > Oh...and for the record, what you're hearing in this sound snippet, > (the sound you're supposed to hear :), is a free running AMS patch > I did up for an arty friend who wanted some kind of eerie spacey > sort of ambiance as a sound prop for her display installation. I used > to call this patch "Trapped on a Dalek spaceship with the BBC > Radiophonic Orchestra" ;-) > > Regards, > > Donald B > > Hi Donald, Your mp3 sounds pretty good to me...except it's a little scratchy. Perhaps that could be filtered out ? I am running the standard Debian kernel using a dual-core 3.0 Ghz processor. I'm thinking that it would be better if I went with the 64studio distribution or, even beyond that, upgrade to a 64 bit processor, but that will be a few months away. Jazz++ performs pretty well with a small number of tracks, but I did notice if rendering a 16 track file it does break up some. The metronome seems to work now...although the sound is not right. Definitely not a drum sound. Aconnectgui, when I try to do additional configuration, locks up badly. So much that I couldn't kill it and at one point had to forcibly power down. There has to be a problem with it. Bob |
|
From: D.B. M. <db...@ho...> - 2008-05-18 01:43:24
|
Greetings, ---------------------------------------- > Date: Sat, 17 May 2008 15:27:25 -0700 > Subject: Re: [jazzplusplus-devel] configure.ac update -please test- > > DM> Same env as before..ie; vkeybd not running but > DM> with jack/fluidsynth/qsynth running and ready to go. > DM> > DM> Test build @ revision 527 (complete session); > DM> > DM> WARNING: The output device index is out of range! > DM> > DM> Program received signal SIGSEGV, Segmentation fault. > DM> [Switching to Thread 140569115023072 (LWP 11874)] > DM> 0x0000000000426cea in tAlsaPlayer::SetSoftThru > DM> (this=0xb68010, on=1, idev=0, odev=0) at > DM> ../../jazz/src/AlsaPlayer.cpp:224 > DM> 224 thru->SetSource(iaddr[ithru].client, iaddr[ithru].port); > DM> > DM> Hope this helps, regards > > It does. > > After you last crash report I guessed that there were no value inputs on > your machine, and I believe I fixed the cause of that initial crash. > The debug output that reads... > > Input device count: 0 > INFO: input device is -1, so selecting one. > no device found! > Input device is: -1 > > Shows me we are now getting past that problem. > > Now you have discovered another place where the code attempts to set the > ALSA thru for the input device, but there are no input devices > available. I'll bet this is the same problem Kevin C. is having. > Unfortunately the Mandriva box I attempt debugging on hangs completely > when I run Jazz++. ..that's curious.. > > I'm hoping Kevin will reply to my Mandriva post indicating if the > "Spring version" of Mandriva may help me out. > > Otherwise, I'm applying blind patches (i.e. patches that haven't been > tested on anything). > > I'll see what I can do. I wasn't actually aware your mandriva was that broken by jazz. Or is that the other way around?... ;-) I'm pretty prompt testing things however...so patch on... Regards, Donald B _________________________________________________________________ Are you paid what you're worth? Find out: SEEK Salary Centre http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=OCT07_endtext_salary&_m=EXT |
|
From: D.B. M. <db...@ho...> - 2008-05-18 01:27:37
|
---------------------------------------- > Date: Sat, 17 May 2008 14:47:37 -0700 > Subject: Re: [jazzplusplus-devel] Patch -- htdocs - added content to documentation > > DM = D.B. Moore > DM> This patch adds content to the documentation page of > DM> the website. I'll be adding content here for a while... > DM> > DM> In a perfect world, this area should be navigated with > DM> the help of a contents menu. For now, just keep adding > DM> to it in small sectional installments as aligned with > DM> the small patch premise agreed on before.... > DM> > DM> I'll start a separate discussion in another thread soon > DM> regarding the documentation directions... > > Applied with some slight modifications, but I was hoping this stuff > would end up as part of the online docs. Since we can generate HTML > with that content, I can simply upload it to the web site. This is exactly one of the things that separate thread was going to touch on....damn good crystal ball you've got your end ;-) > I have > Tex2RTF building on a Linux box and the Mac. Maybe we can focus on that > so you can start adding this type of content to jazz/src/HelpFiles/jazz.tex. > > okay...it's were it was destined for anyhow....a discussion will ensue Regards, Donald B _________________________________________________________________ Search for local singles online @ Lavalife - Click here http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30290&_t=764581033&_r=email_taglines_Search_OCT07&_m=EXT |
|
From: Pete S. <pst...@gm...> - 2008-05-17 22:27:30
|
DM> Same env as before..ie; vkeybd not running but DM> with jack/fluidsynth/qsynth running and ready to go. DM> DM> Test build @ revision 527 (complete session); DM> DM> (gdb) run DM> Starting program: /root/Jazz++/TestInstall/bin/jazz DM> warning: no loadable sections found in added symbol-file DM> system-supplied DSO at 0x7fff30bfe000 DM> [Thread debugging using libthread_db enabled] DM> [New Thread 140725286655712 (LWP 11863)] DM> JZProject::ReadConfiguration() ConfFileNameAndPath: DM> "/root/Jazz++/TestInstall/share/Jazz++/jazz.cfg" DM> JZConfiguration::LoadConfig: DM> "/root/Jazz++/TestInstall/share/Jazz++/jazz.cfg" DM> Include synthesizer configuration file "gs.jzi" DM> FindFile: Immediate hit on file "gs.jzi" DM> Include file "gsdrmset.jzi" DM> FindFile: Immediate hit on file "gsdrmset.jzi" DM> Include file "gmdrmnam.jzi" DM> FindFile: Immediate hit on file "gmdrmnam.jzi" DM> Include file "gsvoices.jzi" DM> FindFile: Immediate hit on file "gsvoices.jzi" DM> Include file "ctrlnam.jzi" DM> FindFile: Immediate hit on file "ctrlnam.jzi" DM> created client:port = 131:0 DM> Input device count: 0 DM> INFO: input device is -1, so selecting one. DM> no device found! DM> Input device is: -1 DM> INFO: output device is -1, so selecting one. DM> DM> //pops 'select output device' dialog window DM> // candidates -- DM> client 128 qjackctl DM> fluid synth (11837) Synth input port (11837.0) DM> //selecting fluid synth entry, click on OK DM> DM> DM> WARNING: The output device index is out of range! DM> DM> Program received signal SIGSEGV, Segmentation fault. DM> [Switching to Thread 140569115023072 (LWP 11874)] DM> 0x0000000000426cea in tAlsaPlayer::SetSoftThru DM> (this=0xb68010, on=1, idev=0, odev=0) at DM> ../../jazz/src/AlsaPlayer.cpp:224 DM> 224 thru->SetSource(iaddr[ithru].client, iaddr[ithru].port); DM> DM> Hope this helps, regards It does. After you last crash report I guessed that there were no value inputs on your machine, and I believe I fixed the cause of that initial crash. The debug output that reads... Input device count: 0 INFO: input device is -1, so selecting one. no device found! Input device is: -1 Shows me we are now getting past that problem. Now you have discovered another place where the code attempts to set the ALSA thru for the input device, but there are no input devices available. I'll bet this is the same problem Kevin C. is having. Unfortunately the Mandriva box I attempt debugging on hangs completely when I run Jazz++. I'm hoping Kevin will reply to my Mandriva post indicating if the "Spring version" of Mandriva may help me out. Otherwise, I'm applying blind patches (i.e. patches that haven't been tested on anything). I'll see what I can do. Pete |
|
From: Pete S. <pst...@gm...> - 2008-05-17 22:03:05
|
Hey Kevin C., I just received an announcement about "Mandriva Linux 2008 Spring". I take it this would be newer that the 2008.0 version I loaded. Is that true? Should I give it a try? Pete |
86 messages has been excluded from this view by a project administrator.
