From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: Anybody else having problems with audio/vidio apps and glibc-2.5?
Date: Mon, 23 Oct 2006 22:18:10 +0000 (UTC) [thread overview]
Message-ID: <ehjf32$bdt$3@sea.gmane.org> (raw)
In-Reply-To: 200610232131.04118.janjitse@gmail.com
Jan Jitse Venselaar <janjitse@gmail.com> posted
200610232131.04118.janjitse@gmail.com, excerpted below, on Mon, 23 Oct
2006 21:30:58 +0200:
> You patched your glibc ebuild to not strip -ftree-vectorize ?
> If so, I'd say that means trouble. I had some trouble with segfaulting apps
> when I tried a rebuild with this flag. I did not rebuild glibc with this flag
> however. I'd say -ftree-vectorize with glibc means big trouble.
>
> FWIW, I have glibc-2.5, everything built with gcc-4.1.1 but nothing fancy in
> the cflags, and everything runs fine.
No, I didn't patch the ebuild. That's one of the things I hadn't double
checked yet when I posted, but indeed, it seems that -ftree-vectorize
(and pretty much everything else for that matter) is stripped by the glibc
ebuild. Thus, it's almost certainly glibc-2.5 itself, not any CFLAGS, that
caused my pain, tho it very well could be glibc-2.5 in /combination/ with
other software compiled with certain CFLAGS. I'll have to recompile
glibc-2.5 again and try it again to be sure, but that's my working
hypothesis at this point.
--
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:[~2006-10-23 22:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 17:22 [gentoo-amd64] Anybody else having problems with audio/vidio apps and glibc-2.5? Duncan
2006-10-23 19:10 ` Hemmann, Volker Armin
2006-10-23 22:12 ` [gentoo-amd64] " Duncan
2006-10-23 22:19 ` Hemmann, Volker Armin
2006-10-23 23:48 ` Jamie
2006-10-24 0:19 ` Hemmann, Volker Armin
2006-10-24 1:26 ` Jamie
2006-10-24 1:47 ` Joe Menola
2006-10-24 1:58 ` Richard Fish
2006-10-24 9:00 ` Peter Humphrey
2006-10-24 17:25 ` Richard Fish
2006-10-25 8:17 ` Peter Humphrey
2006-10-24 2:02 ` Nuitari
2006-10-24 2:04 ` Hemmann, Volker Armin
2006-10-24 8:29 ` Simon Stelling
2006-10-24 13:04 ` [gentoo-amd64] Backup techniques Was: " Duncan
2006-10-24 13:28 ` Rob Lesslie
2006-10-24 14:01 ` Peter Humphrey
2006-10-24 14:18 ` Bo Ørsted Andresen
2006-10-25 8:19 ` Peter Humphrey
2006-10-24 15:03 ` [gentoo-amd64] Re: Anybody else having problems with " Bob Sanders
2006-10-24 9:11 ` Andrei Slavoiu
2006-10-23 19:30 ` [gentoo-amd64] " Jan Jitse Venselaar
2006-10-23 22:18 ` Duncan [this message]
2006-10-24 9:43 ` Piotr Pruszczak
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='ehjf32$bdt$3@sea.gmane.org' \
--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