From: Carlos O'Donell <carlos_odonell@mentor.com>
To: Andreas Jaeger <aj@suse.com>
Cc: <libc-ports@sourceware.org>, Mike Frysinger <vapier@gentoo.org>,
<libc-alpha@sourceware.org>
Subject: Re: Request for help: Fix building tarballs for ports add-on.
Date: Thu, 14 Jun 2012 14:31:00 -0000 [thread overview]
Message-ID: <4FD9F5B9.8050900@mentor.com> (raw)
In-Reply-To: <1889834.8sqT8COGaf@byrd>
On 6/14/2012 3:16 AM, Andreas Jaeger wrote:
> On Wednesday, June 13, 2012 21:15:13 Mike Frysinger wrote:
>> On Wednesday 13 June 2012 20:08:57 Carlos O'Donell wrote:
>>> 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?
>>
>> isn't it just:
>> git archive --prefix=glibc-ports-2.16/ glibc-2.16 | xz \
>>
>> > glibc-ports-2.16.tar.xz
>
> Yeah - there's a Makefile rule in libc:
> %.tar: FORCE
> git archive --prefix=$*/ $* > $@.new
> mv -f $@.new $@
>
> I guess, this just needs to be done for ports as well in the proper way
> - unless Carlos wants to call the above manually...
Exactly. I'd like to see this added to the libc-ports makefile,
and tested by someone. That would help the upcoming release and
all the point releases based on 2.16. It's just one less thing to
do manually :-)
Cheers,
Carlos.
--
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell@mentor.com
carlos@codesourcery.com
+1 (613) 963 1026
prev parent reply other threads:[~2012-06-14 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 0:09 Carlos O'Donell
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 [this message]
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=4FD9F5B9.8050900@mentor.com \
--to=carlos_odonell@mentor.com \
--cc=aj@suse.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=vapier@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).