On Thu, Jun 12, 2003, Tim Robbins wrote:
> On Wed, Jun 11, 2003 at 07:37:01PM -0700, Kris Kennaway wrote:
>
> > It's possible that there's either a bug in gcc or there is C code in
> > the system that has a different meaning when interpreted to C99
> > standards.
>
> I think I may have found the
On Thu, Jun 12, 2003 at 02:43:42PM -0700, David O'Brien wrote:
> On Wed, Jun 11, 2003 at 07:37:01PM -0700, Kris Kennaway wrote:
> > On Tue, Jun 10, 2003 at 04:38:58AM -0700, Kris Kennaway wrote:
> > > A couple of ports are creating broken bzip2 archives since I updated
> > > the build environments
On Wed, Jun 11, 2003 at 07:37:01PM -0700, Kris Kennaway wrote:
> On Tue, Jun 10, 2003 at 04:38:58AM -0700, Kris Kennaway wrote:
> > A couple of ports are creating broken bzip2 archives since I updated
> > the build environments to 5.1-CURRENT:
...
> Backing out the recent changes to bsd.sys.mk fixe
deleting the define __attribute
stuff in system.h of
/usr/src/contrib/tar/src/system.h
and rebuilding+installing tar repaired package creation here.
--
Mit freundlichen Grüßen
Fritz Heinrichmeyer FernUniversitaet, LG ES, 58084 Hagen (Germany)
tel:+49 2331/987-1166 fax:987-355 http://www-es.fernun
On Wed, Jun 11, 2003 at 07:37:01PM -0700, Kris Kennaway wrote:
> It's possible that there's either a bug in gcc or there is C code in
> the system that has a different meaning when interpreted to C99
> standards.
I think I may have found the problem, and I think it's in GNU tar.
GNU tar does thi
On Tue, Jun 10, 2003 at 04:38:58AM -0700, Kris Kennaway wrote:
> A couple of ports are creating broken bzip2 archives since I updated
> the build environments to 5.1-CURRENT:
>
>
> ports-i386%bzip2 -t ja-makejvf-fkr-1.0_1.tbz
> bzip2: ja-makejvf-fkr-1.0_1.tbz: file ends unexpectedly
>
> You
