Hallo,
for me devel_0_37 currently fails to compile correctly. Using a fresh checkout (rm -f src/*) doing a configure && make results in a whole lot of errors like:
x_acoustics.o(.text+0x1c7): In function `dbtorms': : undefined reference to `exp' x_acoustics.o(.text+0x4de): In function `mtof_float': : undefined reference to `exp' x_acoustics.o(.text+0x57c): In function `ftom_float': : undefined reference to `log' x_acoustics.o(.text+0x609): In function `rmstodb_float': : undefined reference to `log' x_acoustics.o(.text+0x6b9): In function `powtodb_float': : undefined reference to `log' x_acoustics.o(.text+0x78c): In function `dbtopow_float': : undefined reference to `exp' x_acoustics.o(.text+0x84c): In function `dbtorms_float': : undefined reference to `exp' collect2: ld returned 1 exit status make: *** [../bin/pd] Error 1
when doing the final linking of ../bin/pd
This is because of a missing "-lm", which I can add to makefile, but where do I add this to makefile.in or the configure stuff and how comes it is suddenly missing?
Also I really wonder again, how current devel_0_37 is, as it still shows the "exp shadowed" warnings in vexp.c, which are already fixed in MSP-pd-0.37-1
Could it be, that CVS seriously lags behind? I see in some directories, the newest imports are 2 months (Feb.) old, whereas the latest MSP-Pd was released on March 4 including several bug fixes IIRC.
Ciao
This is because of a missing "-lm", which I can add to makefile, but where do I add this to makefile.in or the configure stuff and how comes it is suddenly missing?
wait ... there might be a problem if --enable-icc is not set ... i changed the configure script ... can you check it, again? it should be fixed now ...
cheers...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
Hallo, Tim Blechmann hat gesagt: // Tim Blechmann wrote:
This is because of a missing "-lm", which I can add to makefile, but where do I add this to makefile.in or the configure stuff and how comes it is suddenly missing?
wait ... there might be a problem if --enable-icc is not set ... i changed the configure script ... can you check it, again? it should be fixed now ...
Ah, thanks, -lm is included LIBS again. Now it might only be "old". ;)
Ciao
guenter is the merge-master for merging miller's versions into the CVS and it sounds like he has been really busy recently. I am sure that he will get to it when he has the time. Hopefully soon he won't need to do these merges and we all can work from the same CVS.
.hc
On Thursday, Apr 22, 2004, at 07:23 America/New_York, Frank Barknecht wrote:
Hallo,
for me devel_0_37 currently fails to compile correctly. Using a fresh checkout (rm -f src/*) doing a configure && make results in a whole lot of errors like:
x_acoustics.o(.text+0x1c7): In function `dbtorms': : undefined reference to `exp' x_acoustics.o(.text+0x4de): In function `mtof_float': : undefined reference to `exp' x_acoustics.o(.text+0x57c): In function `ftom_float': : undefined reference to `log' x_acoustics.o(.text+0x609): In function `rmstodb_float': : undefined reference to `log' x_acoustics.o(.text+0x6b9): In function `powtodb_float': : undefined reference to `log' x_acoustics.o(.text+0x78c): In function `dbtopow_float': : undefined reference to `exp' x_acoustics.o(.text+0x84c): In function `dbtorms_float': : undefined reference to `exp' collect2: ld returned 1 exit status make: *** [../bin/pd] Error 1
when doing the final linking of ../bin/pd
This is because of a missing "-lm", which I can add to makefile, but where do I add this to makefile.in or the configure stuff and how comes it is suddenly missing?
Also I really wonder again, how current devel_0_37 is, as it still shows the "exp shadowed" warnings in vexp.c, which are already fixed in MSP-pd-0.37-1
Could it be, that CVS seriously lags behind? I see in some directories, the newest imports are 2 months (Feb.) old, whereas the latest MSP-Pd was released on March 4 including several bug fixes IIRC.
Ciao
Frank Barknecht _ ______footils.org__
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev
________________________________________________________________________ ____
Using ReBirth is like trying to play an 808 with a long stick. -David Zicarelli
guenter is the merge-master for merging miller's versions into the CVS and it sounds like he has been really busy recently. I am sure that he will get to it when he has the time. Hopefully soon he won't need to do these merges and we all can work from the same CVS.
i added the support for the icc compiler to the autoconf script and made small mistake ... it should compile fine, again ...
cheers...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
Hallo, Tim Blechmann hat gesagt: // Tim Blechmann wrote:
guenter is the merge-master for merging miller's versions into the CVS and it sounds like he has been really busy recently. I am sure that he will get to it when he has the time. Hopefully soon he won't need to do these merges and we all can work from the same CVS.
i added the support for the icc compiler to the autoconf script and made small mistake ... it should compile fine, again ...
Yes, it does, no problem. If I knew a bit more autoconf I wouldn't have bothered the list. The slightly out of date Pd is something else, which I probably won't have time to look into before LAConf2 as well - especially as I've never done this before.
The merging sure is lots of tedious work which I don't envy Guenther and Thomas.
Ciao
On Thu, 22 Apr 2004, Frank Barknecht wrote:
The merging sure is lots of tedious work which I don't envy Guenther and Thomas.
Thats true, above all its unthankfull. The maximum you get is complaints. I don't mean bug reports, but people tend to think that it is sort of and obligation, the last time I did the merge there was not a single thank you, only complaints. I admit that I am a bit a whiner here, but if you spend your sunday afternoon trying to do something for the community and it is not appreciated, you start to think that the community probably doesn't want this to be done.
Guenter
Hallo, guenter geiger hat gesagt: // guenter geiger wrote:
On Thu, 22 Apr 2004, Frank Barknecht wrote:
The merging sure is lots of tedious work which I don't envy Guenther and Thomas.
Thats true, above all its unthankfull. The maximum you get is complaints. I don't mean bug reports, but people tend to think that it is sort of and obligation, the last time I did the merge there was not a single thank you, only complaints. I admit that I am a bit a whiner here, but if you spend your sunday afternoon trying to do something for the community and it is not appreciated, you start to think that the community probably doesn't want this to be done.
I sure didn't want to sound like I'm complaining, as I have lots of respect for you (and "xovo") doing the merging and am really grateful for it. It just wasn't clear to me at what stage the code on CVS is.
I also wonder, how you approach the merging technically, so that others (like me) can help out with this. I could of course compare what is in the CVS with MSP-Pd file by file, but how do I find out, which parts are just new changes in the MSP verison, and what is a feature added by some of the other developers like Thomas, Tim or you?
Is there a list of those patches somewhere?
Ciao
I also wonder, how you approach the merging technically, so that others (like me) can help out with this. I could of course compare what is in the CVS with MSP-Pd file by file, but how do I find out, which parts are just new changes in the MSP verison, and what is a feature added by some of the other developers like Thomas, Tim or you?
Is there a list of those patches somewhere?
i doubt that, although it would probably a good idea to add a cvs_changes.txt file for the changes from miller's branch ...
i could add something like that to the cvs soon, containing my changes ... (probably sunday afternoon) ... i hope other developers add their changes to this file ... maybe something like that helps us not to forget the changes on the cvs (as it happend from devel_0_37 to devel_0_37) and miller to add certain features to his branch ...
cheers...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
On Fri, 23 Apr 2004, Tim Blechmann wrote:
I also wonder, how you approach the merging technically, so that others (like me) can help out with this. I could of course compare what is in the CVS with MSP-Pd file by file, but how do I find out, which parts are just new changes in the MSP verison, and what is a feature added by some of the other developers like Thomas, Tim or you?
I generally extract the differences between Millers versions and merge them into the devel branch. This is not always easy, especially if the diffs conflict. You need to know quite a bit about the working of Pd in some cases. You have to take special care about the parts that got included into Millers version from the CVS.
Is there a list of those patches somewhere?
i doubt that, although it would probably a good idea to add a cvs_changes.txt file for the changes from miller's branch ...
That would be a good idea. Up to now the only documentation we have is in the CVS logs.
Guenter
i could add something like that to the cvs soon, containing my changes ... (probably sunday afternoon) ... i hope other developers add their changes to this file ... maybe something like that helps us not to forget the changes on the cvs (as it happend from devel_0_37 to devel_0_37) and miller to add certain features to his branch ...
cheers...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev
Is there a list of those patches somewhere?
i doubt that, although it would probably a good idea to add a cvs_changes.txt file for the changes from miller's branch ...
That would be a good idea. Up to now the only documentation we have is in the CVS logs.
i added a file containing my changes to the cvs ... it would be nice, if all the developers who have been working on the devel_0_37 branch would add their changes to this file, too...
cheers...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
Hallo, Tim Blechmann hat gesagt: // Tim Blechmann wrote:
Is there a list of those patches somewhere?
i doubt that, although it would probably a good idea to add a cvs_changes.txt file for the changes from miller's branch ...
That would be a good idea. Up to now the only documentation we have is in the CVS logs.
i added a file containing my changes to the cvs ... it would be nice, if all the developers who have been working on the devel_0_37 branch would add their changes to this file, too...
And maybe we also should collect the patches themselves? There is a patch collector at SF: http://sourceforge.net/tracker/?group_id=55736&atid=478072
Ciao
And maybe we also should collect the patches themselves? There is a patch collector at SF: http://sourceforge.net/tracker/?group_id=55736&atid=478072
what patches are supposed to be there? patches on top of the devel branch or the diffs between miller's and the devel branch? anyway, we should start to use at least the bug and the feature request tracker ...
cheers...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
Hallo, Tim Blechmann hat gesagt: // Tim Blechmann wrote:
And maybe we also should collect the patches themselves? There is a patch collector at SF: http://sourceforge.net/tracker/?group_id=55736&atid=478072
what patches are supposed to be there? patches on top of the devel branch or the diffs between miller's and the devel branch?
Well, I'd say, everything that was applied to the CVS, to make it easier, to try them out when merging another version, for example with "patch --dry-run < ..."
Ciao
hi frank,
Well, I'd say, everything that was applied to the CVS, to make it easier, to try them out when merging another version, for example with "patch --dry-run < ..."
i see your point ... but we should be able to get these from the cvs changelog as well ... i'm not familiar with all the possibilities cvs offers, but we should be able to extract these information from there ...
well, it's probably a good idea to discuss this at the lad conference ... see you there...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
Guenter,
some, like myself, don't really understand who is doing what in terms of real work. (or how and why the merges are happening)
so, I guess I'd just like to say 'vielen vielen dank, amigo' I can imagine what kind of work it is.
best -august.
On Fri, 23 Apr 2004, guenter geiger wrote:
On Thu, 22 Apr 2004, Frank Barknecht wrote:
The merging sure is lots of tedious work which I don't envy Guenther and Thomas.
Thats true, above all its unthankfull. The maximum you get is complaints. I don't mean bug reports, but people tend to think that it is sort of and obligation, the last time I did the merge there was not a single thank you, only complaints. I admit that I am a bit a whiner here, but if you spend your sunday afternoon trying to do something for the community and it is not appreciated, you start to think that the community probably doesn't want this to be done.
Guenter
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev
On Friday, Apr 23, 2004, at 04:02 America/New_York, guenter geiger wrote:
On Thu, 22 Apr 2004, Frank Barknecht wrote:
The merging sure is lots of tedious work which I don't envy Guenther and Thomas.
Thats true, above all its unthankfull. The maximum you get is complaints. I don't mean bug reports, but people tend to think that it is sort of and obligation, the last time I did the merge there was not a single thank you, only complaints. I admit that I am a bit a whiner here, but if you spend your sunday afternoon trying to do something for the community and it is not appreciated, you start to think that the community probably doesn't want this to be done.
Guenter
I can't imagine Pd without the work that you have done. So you are owed, and hopefully receive, much gratitude from me. I just try to do my bit in return and aim to reduce the tedious work for all involved.
That said, have I mentioned the CVS? ;) Wouldn't it be great if everyone maintained their own code there? ;) Thanks to all who do...
-The CVS cheerleader. ________________________________________________________________________ ____
"[W]e have invented the technology to eliminate scarcity, but we are deliberately throwing it away to benefit those who profit from scarcity." -John Gilmore