Csound › Csound - Dev

Error building 5.16.1 on os x

Classic

List

Threaded

43 messages Options

123

Iain Duncan-2

Error building 5.16.1 on os x

With the tar ball from sourceforge, and the following scons line:

scons useCoreAudio=1 useJack=1 useGettext=0

malloc -I/opt/local/include/boost-1_32 -I/usr/include/python2.6 -I/opt/local/include -I/usr/local/include Opcodes/tl/fractalnoise.cpp

Opcodes/tl/fractalnoise.cpp: In function ‘void* aligned_calloc(size_t, size_t)’:

Opcodes/tl/fractalnoise.cpp:42: error: pointer of type ‘void *’ used in arithmetic

scons: *** [Opcodes/tl/fractalnoise.os] Error 1

scons: building terminated because of errors.

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Csound-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/csound-devel

Remove Ads

joachim-3

Re: Error building 5.16.1 on os x

that's exactly what i just wanted to ask, too.
i just tried building csound for osx 10.5, and got the same error. i
assume you have 10.6 or 10.7?
funny enough, this was no problem on linux.

joachim

Am 11.02.2012 22:43, schrieb Iain Duncan:

> With the tar ball from sourceforge, and the following scons line:
>
> scons useCoreAudio=1 useJack=1 useGettext=0
>
> malloc -I/opt/local/include/boost-1_32 -I/usr/include/python2.6
> -I/opt/local/include -I/usr/local/include Opcodes/tl/fractalnoise.cpp
> Opcodes/tl/fractalnoise.cpp: In function ‘void* aligned_calloc(size_t,
> size_t)’:
> Opcodes/tl/fractalnoise.cpp:42: error: pointer of type ‘void *’ used in
> arithmetic
> scons: *** [Opcodes/tl/fractalnoise.os] Error 1
> scons: building terminated because of errors.
>
>
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>
>
>
> _______________________________________________
> Csound-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Iain Duncan-2

Re: Error building 5.16.1 on os x

On Sat, Feb 11, 2012 at 2:10 PM, joachim heintz <[hidden email]> wrote:

that's exactly what i just wanted to ask, too.
i just tried building csound for osx 10.5, and got the same error. i
assume you have 10.6 or 10.7?

yeah, 10.6.7 actually. And can build csound 5.15.0 without issue.

iain

jpff

Re: Error building 5.16.1 on os x

In reply to this post by joachim-3

I havecorrectewd rhgat in git a few days ago
==John ff

> that's exactly what i just wanted to ask, too.
> i just tried building csound for osx 10.5, and got the same error. i
> assume you have 10.6 or 10.7?
> funny enough, this was no problem on linux.
>
> joachim
>
>
> Am 11.02.2012 22:43, schrieb Iain Duncan:
>> With the tar ball from sourceforge, and the following scons line:
>>
>> scons useCoreAudio=1 useJack=1 useGettext=0
>>
>> malloc -I/opt/local/include/boost-1_32 -I/usr/include/python2.6
>> -I/opt/local/include -I/usr/local/include Opcodes/tl/fractalnoise.cpp
>> Opcodes/tl/fractalnoise.cpp: In function âvoid* aligned_calloc(size_t,
>> size_t)â:
>> Opcodes/tl/fractalnoise.cpp:42: error: pointer of type âvoid *â used
>> in
>> arithmetic
>> scons: *** [Opcodes/tl/fractalnoise.os] Error 1
>> scons: building terminated because of errors.
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Virtualization & Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>>
>>
>>
>> _______________________________________________
>> Csound-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Csound-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

Steven Yi

Re: Error building 5.16.1 on os x

The latest in git has:

inline void *aligned_calloc(size_t nmemb, size_t size)
{
- return (void*)((unsigned long)(calloc((nmemb*size)+15,
- (sizeof(char)))+15) & 0xfffffff0);
+ return (void*)(((unsigned long)(calloc((nmemb*size)+15,
+ (sizeof(char))))+15) & 0xfffffff0);
}

Seems that the source release needs to be redone?

On Sat, Feb 11, 2012 at 10:18 PM, <[hidden email]> wrote:

> I havecorrectewd rhgat in git a few days ago
> ==John ff
>
>> that's exactly what i just wanted to ask, too.
>> i just tried building csound for osx 10.5, and got the same error. i
>> assume you have 10.6 or 10.7?
>> funny enough, this was no problem on linux.
>>
>> joachim
>>
>>
>> Am 11.02.2012 22:43, schrieb Iain Duncan:
>>> With the tar ball from sourceforge, and the following scons line:
>>>
>>> scons useCoreAudio=1 useJack=1 useGettext=0
>>>
>>> malloc -I/opt/local/include/boost-1_32 -I/usr/include/python2.6
>>> -I/opt/local/include -I/usr/local/include Opcodes/tl/fractalnoise.cpp
>>> Opcodes/tl/fractalnoise.cpp: In function â€˜void* aligned_calloc(size_t,
>>> size_t)â€™:
>>> Opcodes/tl/fractalnoise.cpp:42: error: pointer of type â€˜void *â€™ used
>>> in
>>> arithmetic
>>> scons: *** [Opcodes/tl/fractalnoise.os] Error 1
>>> scons: building terminated because of errors.
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Virtualization & Cloud Management Using Capacity Planning
>>> Cloud computing makes use of virtualization - but cloud computing
>>> also focuses on allowing computing to be delivered as a service.
>>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>>>
>>>
>>>
>>> _______________________________________________
>>> Csound-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> Virtualization & Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>> _______________________________________________
>> Csound-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Csound-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Iain Duncan-2

Re: Error building 5.16.1 on os x

On Sat, Feb 11, 2012 at 2:21 PM, Steven Yi <[hidden email]> wrote:

The latest in git has:

inline void *aligned_calloc(size_t nmemb, size_t size)
{
- return (void*)((unsigned long)(calloc((nmemb*size)+15,
- (sizeof(char)))+15) & 0xfffffff0);
+ return (void*)(((unsigned long)(calloc((nmemb*size)+15,
+ (sizeof(char))))+15) & 0xfffffff0);
}

Seems that the source release needs to be redone?

Yeah I guess! I know that having a full on buildbot is a lot of work, but I still maintain that non-building releases just shouldn't be up on sourceforge, it just looks terrible to new users. Has anyone though of at least instituting a policy that before something goes up as a release it gets build on virtualmachines with the bare minimum dependencies installed for at least linux, osx and windows? Virtualbox is free and it's dead easy to set up snapshots of a system in a known state. IMHO it would go a long way in the csound advocacy department.

Perhaps it should at the least go up flagged as beta until it can be reported as built successfully on these test boxes?

iain

Victor Lazzarini

Re: Error building 5.16.1 on os x

In general, we do not have such problems because we are constantly building from GIT and will identify these issues before a source release. However, this time I was occupied elsewhere and only built from GIT after the release was out, and had no problems whatsoever (probably due to the the fixes).

I don't think this is a problem that would affect the csound advocacy department as the number of OSX users building their own Csound is minimal and usually savvy enough to get around small issues like these.

Victor

On 11 Feb 2012, at 22:45, Iain Duncan wrote:

On Sat, Feb 11, 2012 at 2:21 PM, Steven Yi <[hidden email]> wrote:
The latest in git has:

inline void *aligned_calloc(size_t nmemb, size_t size)
{
- return (void*)((unsigned long)(calloc((nmemb*size)+15,
- (sizeof(char)))+15) & 0xfffffff0);
+ return (void*)(((unsigned long)(calloc((nmemb*size)+15,
+ (sizeof(char))))+15) & 0xfffffff0);
}

Seems that the source release needs to be redone?

Yeah I guess! I know that having a full on buildbot is a lot of work, but I still maintain that non-building releases just shouldn't be up on sourceforge, it just looks terrible to new users. Has anyone though of at least instituting a policy that before something goes up as a release it gets build on virtualmachines with the bare minimum dependencies installed for at least linux, osx and windows? Virtualbox is free and it's dead easy to set up snapshots of a system in a known state. IMHO it would go a long way in the csound advocacy department.

Perhaps it should at the least go up flagged as beta until it can be reported as built successfully on these test boxes?

iain

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/_______________________________________________
Csound-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini

Senior Lecturer

Dept. of Music

NUI Maynooth Ireland

tel.: +353 1 708 3545

Victor dot Lazzarini AT nuim dot ie

Iain Duncan-2

Re: Error building 5.16.1 on os x

On Sat, Feb 11, 2012 at 4:50 PM, Victor Lazzarini <[hidden email]> wrote:

In general, we do not have such problems because we are constantly building from GIT and will identify these issues before a source release. However, this time I was occupied elsewhere and only built from GIT after the release was out, and had no problems whatsoever (probably due to the the fixes).

I don't think this is a problem that would affect the csound advocacy department as the number of OSX users building their own Csound is minimal and usually savvy enough to get around small issues like these.

Given that this has happened to twice to me in the last couple of months, once on os x and once on linux ( where it is documented as being 'the recommended way to install csound ). I'd respectfully disagree.

It just shouldn't happen; in most software development circles, the release of a broken build is an unacceptable failure. I realize that the Csound community has a different take on this, and that I'm in a minority here, but when new user/devlopers who come from other software development scenes come to check out csound and this happens, it creates a really negative impression.

I do python web dev for a living, and I download and install dozens of dependencies every day and rebuild stuff every day. Pubic release builds of published tools are *never* broken. No one releasing a package that gets used in the wild let's that happen, they'd lose your users in a flash. I really think there's no good reason for Csound not to hold itself to the same standard, because you never know how many potential developers get turned off and then decide to go off and be SuperCollider guys or use stk, or just write Csound off as some ivory tower dinosaur project. Yes, I hear that complaint. I don't believe that's the case, but I hear it.

Jack is *never* released in a broken state. Paul would flip out if it happened because there are partnerships in place with people like Harrison consoles and the public release needs to always work. If this were going to be hard for the csound to community to achieve, I could understand dismissing my complaints as whining. But it's not, it's just standard practice for heavily used open source software, and it's not hard. All it takes is putting some kind of system in place. I really really want to tell people using my upcoming project to get into csound. :-/

Am I totally alone in thinking some kind of system to ensure releases work as advertised is warranted? Even if it's nothing more than a 3 day holding period while people test out the build before removing the word 'beta'? It's not asking much.

Iain

Victor Lazzarini

Re: Error building 5.16.1 on os x

As I understand, it happened on Linux from GIT, which can happen as it is a development environment and not guaranteed to always work, so whatever you are saying here does not apply. The source release should not have been broken, but it was, and so we fix it.

If people want to go and use SC or whatever, they are entitled to do so.

Victor

On 12 Feb 2012, at 01:56, Iain Duncan wrote:

On Sat, Feb 11, 2012 at 4:50 PM, Victor Lazzarini <[hidden email]> wrote:

In general, we do not have such problems because we are constantly building from GIT and will identify these issues before a source release. However, this time I was occupied elsewhere and only built from GIT after the release was out, and had no problems whatsoever (probably due to the the fixes).

I don't think this is a problem that would affect the csound advocacy department as the number of OSX users building their own Csound is minimal and usually savvy enough to get around small issues like these.

Given that this has happened to twice to me in the last couple of months, once on os x and once on linux ( where it is documented as being 'the recommended way to install csound ). I'd respectfully disagree.

It just shouldn't happen; in most software development circles, the release of a broken build is an unacceptable failure. I realize that the Csound community has a different take on this, and that I'm in a minority here, but when new user/devlopers who come from other software development scenes come to check out csound and this happens, it creates a really negative impression.

I do python web dev for a living, and I download and install dozens of dependencies every day and rebuild stuff every day. Pubic release builds of published tools are *never* broken. No one releasing a package that gets used in the wild let's that happen, they'd lose your users in a flash. I really think there's no good reason for Csound not to hold itself to the same standard, because you never know how many potential developers get turned off and then decide to go off and be SuperCollider guys or use stk, or just write Csound off as some ivory tower dinosaur project. Yes, I hear that complaint. I don't believe that's the case, but I hear it.

Jack is *never* released in a broken state. Paul would flip out if it happened because there are partnerships in place with people like Harrison consoles and the public release needs to always work. If this were going to be hard for the csound to community to achieve, I could understand dismissing my complaints as whining. But it's not, it's just standard practice for heavily used open source software, and it's not hard. All it takes is putting some kind of system in place. I really really want to tell people using my upcoming project to get into csound. :-/

Am I totally alone in thinking some kind of system to ensure releases work as advertised is warranted? Even if it's nothing more than a 3 day holding period while people test out the build before removing the word 'beta'? It's not asking much.

Iain

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/_______________________________________________
Csound-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini

Senior Lecturer

Dept. of Music

NUI Maynooth Ireland

tel.: +353 1 708 3545

Victor dot Lazzarini AT nuim dot ie

Andres Cabrera

Re: Error building 5.16.1 on os x

In reply to this post by Iain Duncan-2

hi,

I think you are right. Another important thing is that LINUX distributions might rely on source packages, and if they don't build out of the box, the update will be postponed until the next working release.

Cheers,
AndresOn 12/02/2012 1:56 Iain Duncan wrote:
On Sat, Feb 11, 2012 at 4:50 PM, Victor Lazzarini <[hidden email]> wrote:

In general, we do not have such problems because we are constantly building from GIT and will identify these issues before a source release. However, this time I was occupied elsewhere and only built from GIT after the release was out, and had no problems whatsoever (probably due to the the fixes).

I don't think this is a problem that would affect the csound advocacy department as the number of OSX users building their own Csound is minimal and usually savvy enough to get around small issues like these.

Given that this has happened to twice to me in the last couple of months, once on os x and once on linux ( where it is documented as being 'the recommended way to install csound ). I'd respectfully disagree.

It just shouldn't happen; in most software development circles, the release of a broken build is an unacceptable failure. I realize that the Csound community has a different take on this, and that I'm in a minority here, but when new user/devlopers who come from other software development scenes come to check out csound and this happens, it creates a really negative impression.

I do python web dev for a living, and I download and install dozens of dependencies every day and rebuild stuff every day. Pubic release builds of published tools are *never* broken. No one releasing a package that gets used in the wild let's that happen, they'd lose your users in a flash. I really think there's no good reason for Csound not to hold itself to the same standard, because you never know how many potential developers get turned off and then decide to go off and be SuperCollider guys or use stk, or just write Csound off as some ivory tower dinosaur project. Yes, I hear that complaint. I don't believe that's the case, but I hear it.

Jack is *never* released in a broken state. Paul would flip out if it happened because there are partnerships in place with people like Harrison consoles and the public release needs to always work. If this were going to be hard for the csound to community to achieve, I could understand dismissing my complaints as whining. But it's not, it's just standard practice for heavily used open source software, and it's not hard. All it takes is putting some kind of system in place. I really really want to tell people using my upcoming project to get into csound. :-/

Am I totally alone in thinking some kind of system to ensure releases work as advertised is warranted? Even if it's nothing more than a 3 day holding period while people test out the build before removing the word 'beta'? It's not asking much.

Iain

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Csound-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/csound-devel

Iain Duncan-2

Re: Error building 5.16.1 on os x

In reply to this post by Victor Lazzarini

On Sun, Feb 12, 2012 at 12:58 AM, Victor Lazzarini <[hidden email]> wrote:

As I understand, it happened on Linux from GIT, which can happen as it is a development environment and not guaranteed to always work, so whatever you are saying here does not apply. The source release should not have been broken, but it was, and so we fix it.

No it was not, it was the production release source tarball of 5.14.2 as downloaded on Dec 18, 2011 from sourceforge. I was very clear in my emails at the time that my frustration stemmed from the fact that the *production release* did not build on linux, while the official documentation suggested building from source as the correct thing to do for linux. Please see the list archives for that date if you want verification.

I was advised that time that it was "fixed in git". However, you are now telling me that the trunk from git is not stable, and can't be relied on at any given point ( totally reasonable, and why others use release candidate branches prior to releasing ). So that leaves, at that point, no reliable latest production release for linux. I had to backdate to Csound 5.13, not a big deal, but not confidence inspiring to someone hoping to use the Csound engine as a dependency for an app.

Now this has happened again within two months on os x. It was the production release tarball that didn't build.

iain

Victor Lazzarini

Re: Error building 5.16.1 on os x

yes, what I am telling you is that GIT is not always stable, but if you ask the question politely, we will say whether the current GIT is correct or not, or try to help identify any issues.

Victor

On 12 Feb 2012, at 23:30, Iain Duncan wrote:

On Sun, Feb 12, 2012 at 12:58 AM, Victor Lazzarini <[hidden email]> wrote:

As I understand, it happened on Linux from GIT, which can happen as it is a development environment and not guaranteed to always work, so whatever you are saying here does not apply. The source release should not have been broken, but it was, and so we fix it.

No it was not, it was the production release source tarball of 5.14.2 as downloaded on Dec 18, 2011 from sourceforge. I was very clear in my emails at the time that my frustration stemmed from the fact that the *production release* did not build on linux, while the official documentation suggested building from source as the correct thing to do for linux. Please see the list archives for that date if you want verification.

I was advised that time that it was "fixed in git". However, you are now telling me that the trunk from git is not stable, and can't be relied on at any given point ( totally reasonable, and why others use release candidate branches prior to releasing ). So that leaves, at that point, no reliable latest production release for linux. I had to backdate to Csound 5.13, not a big deal, but not confidence inspiring to someone hoping to use the Csound engine as a dependency for an app.

Now this has happened again within two months on os x. It was the production release tarball that didn't build.

iain
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/_______________________________________________
Csound-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini

Senior Lecturer

Dept. of Music

NUI Maynooth Ireland

tel.: +353 1 708 3545

Victor dot Lazzarini AT nuim dot ie

Iain Duncan-2

Re: Error building 5.16.1 on os x

On Sun, Feb 12, 2012 at 3:52 PM, Victor Lazzarini <[hidden email]> wrote:

yes, what I am telling you is that GIT is not always stable, but if you ask the question politely, we will say whether the current GIT is correct or not, or try to help identify any issues.

I apologize that I have come across as impolite.

My poor conduct aside, this does not change the fact that all three broken builds I have complained about were production snapshots, not pulls from git as you believed. I still maintain that this is a serious problem, please see my new post in which I have tried to be as polite and diplomatic as possible.

iain

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Csound-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/csound-devel

Iain Duncan-2

Re: Error building 5.16.1 on os x

On Sun, Feb 12, 2012 at 4:03 PM, Iain Duncan <[hidden email]> wrote:

On Sun, Feb 12, 2012 at 3:52 PM, Victor Lazzarini <[hidden email]> wrote:

yes, what I am telling you is that GIT is not always stable, but if you ask the question politely, we will say whether the current GIT is correct or not, or try to help identify any issues.

I apologize that I have come across as impolite.

My poor conduct aside, this does not change the fact that all three broken builds I have complained about were production snapshots, not pulls from git as you believed. I still maintain that this is a serious problem, please see my new post in which I have tried to be as polite and diplomatic as possible.

I also believe that there should always be a way to get and build the latest production release without having to be on a mailing list and be following what is going on inside the development community. If someone is building an app that has csound as one of its dependencies, it does not seem reasonable to me to expect them to be up on Csound. It may be just one of many dependencies for the app in question.

Iain

andy fillebrown

Re: Error building 5.16.1 on os x

On Windows, production releases of everything I build frequently have
problems, so I'm not really sure what the big deal is. I will say,
however, that with all the libraries I build for my apps, the Csound
devs are the most responsive when I run into bugs, sometimes getting
fixes posted within the hour. In comparison, the Qt libraries can
often take *months* to get fixes pushed through, and they have all
kinds of git branches, hooks, and CI to keep bugs from appearing.
While I'm sure those systems help them deal with the many issues
regarding their giant code-base, is this really necessary for a
repository as small as Csound's? Granted, the Csound releases could
definitely be vetted out a bit, but again ...with the responsiveness
of the devs being so good, what's the big deal?

Cheers,
~ andy.f

On Sun, Feb 12, 2012 at 7:05 PM, Iain Duncan <[hidden email]> wrote:

> On Sun, Feb 12, 2012 at 4:03 PM, Iain Duncan <[hidden email]>
> wrote:
>>
>> On Sun, Feb 12, 2012 at 3:52 PM, Victor Lazzarini
>> <[hidden email]> wrote:
>>>
>>> yes, what I am telling you is that GIT is not always stable, but if you
>>> ask the question politely, we will say whether the current GIT is correct or
>>> not, or try to help identify any issues.
>>>
>>
>> I apologize that I have come across as impolite.
>>
>> My poor conduct aside, this does not change the fact that all three broken
>> builds I have complained about were production snapshots, not pulls from git
>> as you believed. I still maintain that this is a serious problem, please see
>> my new post in which I have tried to be as polite and diplomatic as
>> possible.
>>
>
> I also believe that there should always be a way to get and build the latest
> production release without having to be on a mailing list and be following
> what is going on inside the development community. If someone is building an
> app that has csound as one of its dependencies, it does not seem reasonable
> to me to expect them to be up on Csound. It may be just one of many
> dependencies for the app in question.
>
> Iain
>
>
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Csound-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

Iain Duncan-2

Re: Error building 5.16.1 on os x

On Sun, Feb 12, 2012 at 7:21 PM, andy fillebrown <[hidden email]> wrote:

On Windows, production releases of everything I build frequently have
problems, so I'm not really sure what the big deal is. I will say,
however, that with all the libraries I build for my apps, the Csound
devs are the most responsive when I run into bugs, sometimes getting
fixes posted within the hour. In comparison, the Qt libraries can
often take *months* to get fixes pushed through, and they have all
kinds of git branches, hooks, and CI to keep bugs from appearing.
While I'm sure those systems help them deal with the many issues
regarding their giant code-base, is this really necessary for a
repository as small as Csound's? Granted, the Csound releases could
definitely be vetted out a bit, but again ...with the responsiveness
of the devs being so good, what's the big deal?

The big deal is that someone building an app that depends on Csound should not need to be on mailing lists with the csound devs just to build csound from a production release, in order to use it as a dependency for whatever they are ultimately trying to build. Just as I don't have to be on the mailing lists for the packages that Csound depends on to build csound. I don't have to talk to fltk, portaudio, libsndfile I just download those packages and build them. If I did have to, would we in csound land be using them as dependencies? I have never had an issue downloading and building FLTK, libsndfile, portaudio, qt, or jack. I can't say that they *never* have this same issue, but my experience is that is has never happened to me, while it has happened 3 times in two months with csound, and I don't even build on windows. The QT releases always build, they may not be perfect, but I definitely don't have to get on QT lists to get a new production releases of QT working. I am not talking about 100% test coverage here, just source releases building as advertised so they can be used.

iain

Iain Duncan-2

Re: Error building 5.16.1 on os x

The big deal is that someone building an app that depends on Csound should not need to be on mailing lists with the csound devs just to build csound from a production release, in order to use it as a dependency for whatever they are ultimately trying to build. Just as I don't have to be on the mailing lists for the packages that Csound depends on to build csound. I don't have to talk to fltk, portaudio, libsndfile I just download those packages and build them. If I did have to, would we in csound land be using them as dependencies? I have never had an issue downloading and building FLTK, libsndfile, portaudio, qt, or jack. I can't say that they *never* have this same issue, but my experience is that is has never happened to me, while it has happened 3 times in two months with csound, and I don't even build on windows. The QT releases always build, they may not be perfect, but I definitely don't have to get on QT lists to get a new production releases of QT working. I am not talking about 100% test coverage here, just source releases building as advertised so they can be used.

Another way to look at this. Let's say I have a project (which of course I do, it's just a long way from release) and I want user/developers to build it from source. I publish a page on how to build it, much like the one we have here that Steven just updated:

https://sourceforge.net/apps/mediawiki/csound/index.php?title=Building_Csound_on_OSX_Lion

On the above the instructions tell us to go and get the latest production snapshot of each dependency, and also mention which one was used, which is as far as I can tell in all cases except for PortAudio, the latest production release. This page, and the process of building Csound from source, would be a lot worse if each package had to say something like "install this one only, we can't guarantee other versions including the latest build". I would hate to have to install each of those were their release management the same as Csound's. ( In fact, if I recall correctly, PortAudio's sketchy situation was indeed a cause of concern on the csound dev list years ago when audio output was moved to port audio, and that was part of the reason that it became one option for output and not *the* option for output. That was a long time ago, but I do remember gnashing of teeth on the list over portaudio, and I haven't used it as a result ).

That is the relationship projects using the CsoundAPI will have to Csound.

iain

iain

andy fillebrown

Re: Error building 5.16.1 on os x

I am also a developer of an app depending on Csound and I have no
problem with how Csound is released. I just bring the Csound library
into my own repository and make sure it works in my build system.
Voila! Build and install issues for my users disappear, and as an
added bonus I get a stripped down version of Csound that only depends
on libsndfile.

Cheers,
~ andy.f

On Sun, Feb 12, 2012 at 11:16 PM, Iain Duncan <[hidden email]> wrote:

>> The big deal is that someone building an app that depends on Csound should
>> not need to be on mailing lists with the csound devs just to build csound
>> from a production release, in order to use it as a dependency for whatever
>> they are ultimately trying to build. Just as I don't have to be on the
>> mailing lists for the packages that Csound depends on to build csound. I
>> don't have to talk to fltk, portaudio, libsndfile I just download those
>> packages and build them. If I did have to, would we in csound land be using
>> them as dependencies? I have never had an issue downloading and building
>> FLTK, libsndfile, portaudio, qt, or jack. I can't say that they *never* have
>> this same issue, but my experience is that is has never happened to me,
>> while it has happened 3 times in two months with csound, and I don't even
>> build on windows. The QT releases always build, they may not be perfect, but
>> I definitely don't have to get on QT lists to get a new production releases
>> of QT working. I am not talking about 100% test coverage here, just source
>> releases building as advertised so they can be used.
>>
>
> Another way to look at this. Let's say I have a project (which of course I
> do, it's just a long way from release) and I want user/developers to build
> it from source. I publish a page on how to build it, much like the one we
> have here that Steven just updated:
>
> https://sourceforge.net/apps/mediawiki/csound/index.php?title=Building_Csound_on_OSX_Lion
>
> On the above the instructions tell us to go and get the latest production
> snapshot of each dependency, and also mention which one was used, which is
> as far as I can tell in all cases except for PortAudio, the latest
> production release. This page, and the process of building Csound from
> source, would be a lot worse if each package had to say something like
> "install this one only, we can't guarantee other versions including the
> latest build". I would hate to have to install each of those were their
> release management the same as Csound's. ( In fact, if I recall correctly,
> PortAudio's sketchy situation was indeed a cause of concern on the csound
> dev list years ago when audio output was moved to port audio, and that was
> part of the reason that it became one option for output and not *the* option
> for output. That was a long time ago, but I do remember gnashing of teeth on
> the list over portaudio, and I haven't used it as a result ).
>
> That is the relationship projects using the CsoundAPI will have to Csound.
>
> iain
>
>
>>
>> iain
>>
>
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Csound-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

Tito Latini

Re: Error building 5.16.1 on os x

In reply to this post by Iain Duncan-2

> No it was not, it was the production release source tarball of 5.14.2 as downloaded on Dec 18, 2011 from
> sourceforge. I was very clear in my emails at the time that my frustration stemmed from the fact that the
> *production release* did not build on linux, while the official documentation suggested building from source as
> the correct thing to do for linux. Please see the list archives for that date if you want verification.

Csound5.14.2 and `scons buildNewParser=0' fails

I had helped you before the fix, read this

http://sourceforge.net/mailarchive/message.php?msg_id=28562348

You would have been able to compile csound simply adding
`buildMultiCore=0' to the `scons' command.

Today I have wanted to compile csound from 5.16.1 downto 5.07.0
to show you that the "*production release*" did build on linux:

gnu/linux 64, gcc 4.4.4, slackware pkg 40%, compiled code 60%

* Csound5.16.1
scons: done building targets.

* Csound5.15.0
scons: done building targets.

* Csound5.14.2
scons: done building targets.

* Csound5.13.0
scons: done building targets.

* Csound5.12.1
scons: done building targets.

* Csound5.11.1
scons: done building targets.

* Csound5.10.90
scons: *** [InOut/FL_graph.os] Error 1
...
scons: building terminated because of errors.

downgrade to fltk-1.1.0

scons: done building targets.

* Csound5.10.1
scons: done building targets.

* Csound5.09.0
Opcodes/linear_algebra.cpp:4117: instantiated from here
/usr/include/gmm/gmm_blas.h:59: error: 'do_clear' is not a member of 'gmm::linalg_traits<double>'
scons: *** [Opcodes/linear_algebra.os] Error 1
scons: building terminated because of errors.

I don't have the old gmm headers to try, therefore I remove gmm

scons: done building targets.

* Csound5.08
scons: done building targets.

* Csound5.07.0
scons: done building targets.

=== Endless thanks to All for this ===

I finish with a simple recipe:

- howto help
+ bug report with code (csd file etc)
+ bug fix with code

- how(not)to help
+ bug report with words
+ bug fix with words
+ only words

tito

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Csound-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/csound-devel

jpff

Re: Error building 5.16.1 on os x

First let nme say that i ALWAYS compile csound on my system before
release; only rarely does the GIT system not compile. Similarly it is
plain incorrect to assume we do not test before a release.

One major difference between us and some of the other systems is rate of
change. Even a "minor" release has many many lines changed or new. Also
ther eis a relationship between size anad complexity

Crude count of lines of C/C++ gives

wiiuse 5K
liblo 6K
portaudio 42K
FLTK 54K
libsndfile 70K
exim 86K
csound 251K

We release more often than many of these, and change more.
And we can always improve if anyone were to care to instigate a serious
blackbox testing regime

==John ff

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Csound-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/csound-devel

123