[gentoo-amd64] gcc 4.1.2 and esound

[gentoo-amd64] gcc 4.1.2 and esound

[Mark Haney]

Has anyone else upgraded to gcc 4.1.2 and failed to get esound to 
compile?  My CFLAGS are really simple, but I can't get esound to compile 
at all.  I didn't want to file a bug report until I've heard from 
someone else to see if the fix is out there.

-- 
Mark Haney
Sr. Systems Administrator	
ERC Broadband


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] gcc 4.1.2 and esound

[Stefan Vunckx]

On Wednesday 07 March 2007 23:45:05 Mark Haney wrote:
> Has anyone else upgraded to gcc 4.1.2 and failed to get esound to
> compile?  My CFLAGS are really simple, but I can't get esound to compile
> at all.  I didn't want to file a bug report until I've heard from
> someone else to see if the fix is out there.
>
> --
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband

No problems here!

Some relevant info from emerge --info:
Portage 2.1.2.1-r1 (default-linux/amd64/2006.0, gcc-4.1.2, glibc-2.5-r0, 
2.6.20-gentoo x86_64)
=================================================================
System uname: 2.6.20-gentoo x86_64 AMD Athlon(tm) 64 Processor 3500+
ACCEPT_KEYWORDS="amd64 ~amd64"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -O2 -pipe -msse3"
CHOST="x86_64-pc-linux-gnu"

/stefan
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: gcc 4.1.2 and esound

[Duncan]

"Mark Haney" <mhaney@ercbroadband.org> posted
45EF4071.3000904@ercbroadband.org, excerpted below, on  Wed, 07 Mar 2007
17:45:05 -0500:

> Has anyone else upgraded to gcc 4.1.2 and failed to get esound to
> compile?
>  My CFLAGS are really simple, but I can't get esound to compile at all. 
>  I
> didn't want to file a bug report until I've heard from someone else to
> see if the fix is out there.

Yeah, I know this is over a week old, but just testing it...

You didn't specify which version of esound, but gcc-4.1.2 here, full 
~amd64 system, esound-0.2.37 gets thru the ebuild compile and install 
steps just fine.  I didn't actually qmerge it as I don't need it, but as 
I said, it gets thru the ebuild compile and install steps just fine, and 
that's where you said it was failing you.

If your system is partly stable, partly ~amd64, perhaps that's it.  It 
may need a later version of something else you have merged only as stable.

Or maybe you were trying an older esound, which may not work with the 
newer compiler.  0.2.36-r2 is the latest stable, 0.2.37 is the latest 
~arch and thus what I tested, on this fully ~arch system.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: gcc 4.1.2 and esound

[Stefan Vunckx]

There is a bug report, disabling debug useflag helps.

http://bugs.gentoo.org/show_bug.cgi?id=170971

Regards,
stefan vunckx

On Saturday 17 March 2007 12:47:59 Duncan wrote:
> "Mark Haney" <mhaney@ercbroadband.org> posted
> 45EF4071.3000904@ercbroadband.org, excerpted below, on  Wed, 07 Mar 2007
>
> 17:45:05 -0500:
> > Has anyone else upgraded to gcc 4.1.2 and failed to get esound to
> > compile?
> >  My CFLAGS are really simple, but I can't get esound to compile at all.
> >  I
> > didn't want to file a bug report until I've heard from someone else to
> > see if the fix is out there.
>
> Yeah, I know this is over a week old, but just testing it...
>
> You didn't specify which version of esound, but gcc-4.1.2 here, full
> ~amd64 system, esound-0.2.37 gets thru the ebuild compile and install
> steps just fine.  I didn't actually qmerge it as I don't need it, but as
> I said, it gets thru the ebuild compile and install steps just fine, and
> that's where you said it was failing you.
>
> If your system is partly stable, partly ~amd64, perhaps that's it.  It
> may need a later version of something else you have merged only as stable.
>
> Or maybe you were trying an older esound, which may not work with the
> newer compiler.  0.2.36-r2 is the latest stable, 0.2.37 is the latest
> ~arch and thus what I tested, on this fully ~arch system.
>
> --
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: gcc 4.1.2 and esound

[Vladimir G. Ivanovic]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Duncan wrote:

> You didn't specify which version of esound, but gcc-4.1.2 here, full 
> ~amd64 system, esound-0.2.37 gets thru the ebuild compile and install 
> steps just fine. 

For me, esound-2.37 compiles and installs, but then goes into an
infinite loop using up 100% of the CPU (not immediately, but
unsure---after some sound is played.) The strace output looks like
(repeated ad nauseum):

select(18, [3 4 5 6 7 8 9 10 11 12 13 14 15 16 17], NULL, NULL, {0,
11000}) = 1 (in [17], left {0, 11000})
accept(3, 0x7fffa751c3f0, [28])         = -1 EAGAIN (Resource
temporarily unavailable)
select(17, [16], NULL, NULL, {0, 0})    = 0 (Timeout)
select(16, [15], NULL, NULL, {0, 0})    = 0 (Timeout)
select(15, [14], NULL, NULL, {0, 0})    = 0 (Timeout)
select(14, [13], NULL, NULL, {0, 0})    = 0 (Timeout)
select(13, [12], NULL, NULL, {0, 0})    = 0 (Timeout)
select(12, [11], NULL, NULL, {0, 0})    = 0 (Timeout)
select(11, [10], NULL, NULL, {0, 0})    = 0 (Timeout)
select(10, [9], NULL, NULL, {0, 0})     = 0 (Timeout)
select(8, [7], NULL, NULL, {0, 0})      = 0 (Timeout)
select(7, [6], NULL, NULL, {0, 0})      = 0 (Timeout)
select(9, [8], NULL, NULL, {0, 0})      = 0 (Timeout)
select(6, [5], NULL, NULL, {0, 0})      = 0 (Timeout)
select(5, [4], NULL, NULL, {0, 0})      = 0 (Timeout)
select(18, [17], NULL, NULL, {0, 0})    = 1 (in [17], left {0, 0})
read(17, "", 2048)                      = 0


I am currently downgrading to 2.36-r2 to see if that helps.

- --- Vladimir

- --

Vladimir G. Ivanovic
+1 650 678 8014

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (GNU/Linux)

iD8DBQFF/DNCEo/yvZUwubMRAnpJAJ0R8EudzjcanHyxddzfK8iFvV89fwCdEWvD
tMkIO26RryV1LyE1vxD1dSs=
=Zs/t
-----END PGP SIGNATURE-----
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: gcc 4.1.2 and esound

[Vladimir G. Ivanovic]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vladimir G. Ivanovic wrote:
> For me, esound-2.37 compiles and installs, but then goes into an
> infinite loop using up 100% of the CPU 
<snip>
> I am currently downgrading to 2.36-r2 to see if that helps.

2.36-r2 does not seem to be looping.

- --- Vladimir

- --

Vladimir G. Ivanovic
+1 650 678 8014

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (GNU/Linux)

iD8DBQFF/KsAEo/yvZUwubMRAkXoAJ4jdXeKi4c1LhEH2r7kgvygskTWUACdG0Sq
C7qVbV9l0/IWZiIj42n6JJ0=
=Vs0Z
-----END PGP SIGNATURE-----
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: gcc 4.1.2 and esound

[Mark Haney]

Duncan wrote:
> "Mark Haney" <mhaney@ercbroadband.org> posted
> 45EF4071.3000904@ercbroadband.org, excerpted below, on  Wed, 07 Mar 2007
> 17:45:05 -0500:
> 
>> Has anyone else upgraded to gcc 4.1.2 and failed to get esound to
>> compile?
>>  My CFLAGS are really simple, but I can't get esound to compile at all. 
>>  I
>> didn't want to file a bug report until I've heard from someone else to
>> see if the fix is out there.
> 
> Yeah, I know this is over a week old, but just testing it...
> 
> You didn't specify which version of esound, but gcc-4.1.2 here, full 
> ~amd64 system, esound-0.2.37 gets thru the ebuild compile and install 
> steps just fine.  I didn't actually qmerge it as I don't need it, but as 
> I said, it gets thru the ebuild compile and install steps just fine, and 
> that's where you said it was failing you.
> 
> If your system is partly stable, partly ~amd64, perhaps that's it.  It 
> may need a later version of something else you have merged only as stable.
> 
> Or maybe you were trying an older esound, which may not work with the 
> newer compiler.  0.2.36-r2 is the latest stable, 0.2.37 is the latest 
> ~arch and thus what I tested, on this fully ~arch system.
> 

Hi Duncan, Actually this does help a bit, but I must admit I screwed up 
posting to this list as a day or so after I sent it, I realized the 
machine with the esound compile problem is an x86 not amd64.  Duh.  But 
I think it's fixed now, I'm compiling it now with ~x86 to see if that 
fixes it.


-- 
Ita erat quando hic adveni.

Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: gcc 4.1.2 and esound

[Duncan]

"Mark Haney" <mhaney@ercbroadband.org> posted
45FE86CD.5010401@ercbroadband.org, excerpted below, on  Mon, 19 Mar 2007
08:49:17 -0400:

> Hi Duncan, Actually this does help a bit, but I must admit I screwed up
> posting to this list as a day or so after I sent it, I realized the
> machine with the esound compile problem is an x86 not amd64.  Duh.  But
> I think it's fixed now, I'm compiling it now with ~x86 to see if that
> fixes it.

=8^)  You aren't the first to make that mistake.  I'm sure you won't be 
the last.  No huge deal, as long as this doesn't become user too fast.  
The volume on /that/ list /was/ hard to keep up with.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list