Date: Sat, 17 Jan 2009 01:20:50 -0800 From: Tim Kientzle <kientzle@freebsd.org> To: "Sean C. Farley" <scf@freebsd.org> Cc: Pegasus Mc Cleaft <ken@mthelicon.com>, freebsd-current@freebsd.org Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standardcompiler?) Message-ID: <4971A2F2.7060509@freebsd.org> In-Reply-To: <alpine.BSF.2.00.0901150917440.1930@thor.farley.org> References: <de2964020901141507m5a30c466ta1e05694d220ce0b@mail.gmail.com><20090115084515.GA91157@freebsd.org> <496F0D1D.7080505@andric.com> <6c51dbb10901150344s409cd834p3cd8fae189e42a68@mail.gmail.com> <9225949D37F24E01AA5FC01169A256F2@PegaPegII> <alpine.BSF.2.00.0901150917440.1930@thor.farley.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Sean C. Farley wrote: > > For an archiver, what about tar (bsdtar)? tar tf /usr/lib/libc.a works > for me. :) Actually, there is some development[1] to replace those > utilities with BSD-licensed versions. ar has already been replaced in > HEAD. Kai Wang added "ar" format to libarchive, so tar and cpio in -CURRENT can both read and write ar archives. But that doesn't mean that tar can serve as a replacement for ar. The "ar" utility does have a few tricks. ;-) Kai and I did at one time discuss the feasability of using tar or cpio format as a library archive format. It does have a certain appeal (the "ar" format is fairly gruesome, especially the Gnu/SysV long filename extension) but is probably not worth the effort. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4971A2F2.7060509>