headers
Patrick Shirkey | 12 Jun 2012 18:49

gcc-4.1 support

Hi,

Apologies if this has been hashed out already.

I would like to know if there is a specific reason that jack no longer
compiles under gcc-4.1. This affects specifically users of debian etch
based derivatives and creates a substantial amount of pain in the case of
upgrading to > gcc-4.1.

I have looked at the proposed solution of adding

#define __USE_UNIX98

in certain headers that reference pthread.h but that doesn't get past the
issue for me or others who have tried.

http://old.nabble.com/Problems-building-jack-from-svn-td18774043.html

If it is just that no one had time to do the work around then it would be
very helpful for me and no doubt many others who are still reliant on
solutions built on top of etch to have an official patch which we can
manually apply if there is not time to fully integrate a fix to main
trunk.

I had no trouble upgrading to latest alsa on the same machine so the only
thing holding me back is a new version of jack. It would significantly
extend the life of some machines that are currently installed around the
world in varying professional and educational settings.

--
(Continue reading)

Permalink | Reply |
headers
Adrian Knoth | 12 Jun 2012 19:24
Picon
Gravatar

Re: gcc-4.1 support

On Tue, Jun 12, 2012 at 06:49:33PM +0200, Patrick Shirkey wrote:

> Hi,

Hi!

I assume we're talking about jack1. Correct me if I'm wrong.

> Apologies if this has been hashed out already.

I don't think so.

> I would like to know if there is a specific reason that jack no longer
> compiles under gcc-4.1.

Like with all open-source software: apparently, nobody ran into this
problem before. I for one don't even have a system with gcc-4.1 anymore.

> If it is just that no one had time to do the work around then it would
> be very helpful for me and no doubt many others who are still reliant
> on solutions built on top of etch to have an official patch which we
> can manually apply if there is not time to fully integrate a fix to
> main trunk.

Patches welcome.

Cheers

--

-- 
mail: adi <at> thur.de  	http://adi.thur.de	PGP/GPG: key via keyserver
(Continue reading)

Permalink | Reply |
headers
Paul Davis | 12 Jun 2012 19:25

Re: gcc-4.1 support



On Tue, Jun 12, 2012 at 12:49 PM, Patrick Shirkey <pshirkey <at> boosthardware.com> wrote:
Hi,

Apologies if this has been hashed out already.

The decision to use POSIX Read-Write Locks was taken more than 4 years ago. We do not support any build platform that does not provide this part of the POSIX API.

_______________________________________________
Jack-Devel mailing list
Jack-Devel <at> lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Permalink | Reply |
headers
Patrick Shirkey | 13 Jun 2012 01:54

Re: gcc-4.1 support


On Tue, June 12, 2012 7:25 pm, Paul Davis wrote:
> On Tue, Jun 12, 2012 at 12:49 PM, Patrick Shirkey <
> pshirkey <at> boosthardware.com> wrote:
>
>> Hi,
>>
>> Apologies if this has been hashed out already.
>>
>
> The decision to use POSIX Read-Write Locks was taken more than 4 years
> ago.
> We do not support any build platform that does not provide this part of
> the
> POSIX API.
>

Without asking you to personally commit to anything is there a theoretical
possibility that it could be supported?

What do you estimate is the time/effort required?

Is it along the lines of adding a third party library, testing
specifically on an etch based distribution, then maintaining it across
jack1/2/3 or does it get more hairy than that?

I understand that everyone has a lot on their plate already so I am not
expecting or asking for you to add this task to your workload.

--
Patrick Shirkey
Boost Hardware Ltd
Permalink | Reply |
headers
Paul Davis | 13 Jun 2012 01:59

Re: gcc-4.1 support



On Tue, Jun 12, 2012 at 7:54 PM, Patrick Shirkey <pshirkey <at> boosthardware.com> wrote:

Without asking you to personally commit to anything is there a theoretical
possibility that it could be supported?

posix rwlocks were a part of the UNIX98 specification. that's 1998 ... it is now 2012. using a compiler and/or glibc that doesn't support a feature from 24 years ago ... not worth anyone's time.

and ironically, its almost certainly just a header file issue. i strongly suspect that the glibc version on these systems has these rwlocks, but the headers are not exposing it for various reasons.

_______________________________________________
Jack-Devel mailing list
Jack-Devel <at> lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Permalink | Reply |
headers
Patrick Shirkey | 13 Jun 2012 02:28

Re: gcc-4.1 support


On Wed, June 13, 2012 1:59 am, Paul Davis wrote:
> On Tue, Jun 12, 2012 at 7:54 PM, Patrick Shirkey
> <pshirkey <at> boosthardware.com
>> wrote:
>
>>
>> Without asking you to personally commit to anything is there a
>> theoretical
>> possibility that it could be supported?
>>
>
> posix rwlocks were a part of the UNIX98 specification. that's 1998 ... it
> is now 2012. using a compiler and/or glibc that doesn't support a feature
> from 24 years ago ... not worth anyone's time.
>
> and ironically, its almost certainly just a header file issue. i strongly
> suspect that the glibc version on these systems has these rwlocks, but the
> headers are not exposing it for various reasons.
>

Thanks that helped make things click for me.

To build alsa-driver I had to change a couple of things in the configure
script. One of those things was to add

_GNU_SOURCE

to the CPPFLAGS.

I looked at the jack makefile.am. Do you have a suggestion for the best
way to add it?

If this works I'll have a new tutorial to write...

    "Updating etch to latest Alsa and Jack"

--
Patrick Shirkey
Boost Hardware Ltd
Permalink | Reply |
headers
Patrick Shirkey | 17 Jun 2012 11:11

Re: gcc-4.1 support


On Wed, June 13, 2012 2:28 am, Patrick Shirkey wrote:
>
> On Wed, June 13, 2012 1:59 am, Paul Davis wrote:
>> On Tue, Jun 12, 2012 at 7:54 PM, Patrick Shirkey
>> <pshirkey <at> boosthardware.com
>>> wrote:
>>
>>>
>>> Without asking you to personally commit to anything is there a
>>> theoretical
>>> possibility that it could be supported?
>>>
>>
>> posix rwlocks were a part of the UNIX98 specification. that's 1998 ...
>> it
>> is now 2012. using a compiler and/or glibc that doesn't support a
>> feature
>> from 24 years ago ... not worth anyone's time.
>>
>> and ironically, its almost certainly just a header file issue. i
>> strongly
>> suspect that the glibc version on these systems has these rwlocks, but
>> the
>> headers are not exposing it for various reasons.
>>
>
>
> Thanks that helped make things click for me.
>
> To build alsa-driver I had to change a couple of things in the configure
> script. One of those things was to add
>
> _GNU_SOURCE
>
> to the CPPFLAGS.
>
> I looked at the jack makefile.am. Do you have a suggestion for the best
> way to add it?
>

For future reference the way to solve this problem is quite simple.

cd jack
./configure --prefix=/usr CFLAGS=-D_GNU_SOURCE
make
make install

> If this works I'll have a new tutorial to write...
>
>     "Updating etch to latest Alsa and Jack"
>

Just need to solve a small issue with alsa-drivers on the 2.6.18 kernel
and I think it is done.

--
Patrick Shirkey
Boost Hardware Ltd
Permalink | Reply |

Gmane