From: Carlos O'Donell <carlos_odonell@mentor.com>
To: <libc-ports@sourceware.org>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Request for help: Fix building tarballs for ports add-on.
Date: Thu, 14 Jun 2012 00:09:00 -0000 [thread overview]
Message-ID: <4FD92B99.3050605@mentor.com> (raw)
Community,
As we approach the 2.16 release I am reminded that building
tarballs for the ports add-on is broken.
For the 2.15 release I had to build the tarballs manually.
I'd like this to be automated like it is for glibc core
where we get a .tar.bz2, .tar.gz, and .tar.xz.
Any takers?
Cheers,
Carlos.
--
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell@mentor.com
carlos@codesourcery.com
+1 (613) 963 1026
next reply other threads:[~2012-06-14 0:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 0:09 Carlos O'Donell [this message]
2012-06-14 0:23 ` Roland McGrath
2012-06-14 6:54 ` Thomas Schwinge
2012-06-14 11:02 ` Joseph S. Myers
2012-06-14 16:47 ` Roland McGrath
2012-06-14 17:31 ` Mike Frysinger
2012-06-14 1:15 ` Mike Frysinger
2012-06-14 7:16 ` Andreas Jaeger
2012-06-14 14:31 ` Carlos O'Donell
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=4FD92B99.3050605@mentor.com \
--to=carlos_odonell@mentor.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).