From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: gcc 4.1.2 and esound
Date: Sat, 17 Mar 2007 11:47:59 +0000 (UTC) [thread overview]
Message-ID: <pan.2007.03.17.11.47.59@cox.net> (raw)
In-Reply-To: 45EF4071.3000904@ercbroadband.org
"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
next prev parent reply other threads:[~2007-03-17 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 22:45 [gentoo-amd64] gcc 4.1.2 and esound Mark Haney
2007-03-08 9:08 ` Stefan Vunckx
2007-03-17 11:47 ` Duncan [this message]
2007-03-17 15:11 ` [gentoo-amd64] " Stefan Vunckx
2007-03-17 18:28 ` Vladimir G. Ivanovic
2007-03-18 2:59 ` Vladimir G. Ivanovic
2007-03-19 12:49 ` Mark Haney
2007-03-19 13:27 ` Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2007.03.17.11.47.59@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox