From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: [gentoo-dev] stable tester request for binutils-config
Date: Fri, 25 Mar 2005 10:56:47 -0500 [thread overview]
Message-ID: <200503251056.47556.vapier@gentoo.org> (raw)
for people running stable (and maybe feedback in general), can you guys give
the new binutils-config system a twirl ? basically whatever version you're
running currently, the next rev up is what i want tested :)
amd64, x86, hppa, sparc: 2.15.92.0.2-r1 -> 2.15.92.0.2-r7
arm, ppc, ppc64: 2.15.90.0.3-r3 -> 2.15.90.0.3-r4
alpha, ia64, mips: 2.14.90.0.8-r1 -> 2.14.90.0.8-r2
s390: 2.15.90.0.1.1-r3 -> 2.15.90.0.1.1-r4
things to test:
- when you emerge the new version, does a simple `gcc test.c -o test` work ?
- if you re-emerge the new version, does the simple test above still work ?
- can you `emerge` other packages w/out problems ?
the new system basically sets up a `binutils-config` just like `gcc-config` so
you can (with USE=multislot) emerge multiple versions of binutils on your
system at the sametime
-mike
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2005-03-25 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 15:56 Mike Frysinger [this message]
2005-04-03 19:17 ` [gentoo-dev] stable tester request for binutils-config Mike Frysinger
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=200503251056.47556.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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