CSTD=c99 breaks package creation

From: Kris Kennaway (kris_at_obsecurity.org)
Date: 06/12/03

  • Next message: Kris Kennaway: "Re: adsl/pppoe no longer connecting on 5.1" 
    Date: Wed, 11 Jun 2003 19:37:01 -0700
To: Kris Kennaway <kris@obsecurity.org>

    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 can use the `bzip2recover' program to attempt to recover
    > data from undamaged sections of corrupted files.
    >
    > ports-i386%bzip2 -t cclient-2002c1_1,1.tbz
    > bzip2: cclient-2002c1_1,1.tbz: file ends unexpectedly
    >
    > You can use the `bzip2recover' program to attempt to recover
    > data from undamaged sections of corrupted files.
    > ----
    >
    > They're broken no matter how many times I rebuild them. The bento
    > package cluster machines haven't been updated, so I don't blame a
    > kernel problem, but the build chroot is being populated with a
    > 5.1-CURRENT world instead of 5.1-RELEASE.
    >
    > Can anyone else reproduce this, or has anyone else seen a similar
    > problem?

    Backing out the recent changes to bsd.sys.mk fixed these problems. I
    don't know why, but pkg_create was creating packages that were
    truncated - perhaps tar was closing the pipe early or something.

    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.

    Kris

    • application/pgp-signature attachment: stored
  • Next message: Kris Kennaway: "Re: adsl/pppoe no longer connecting on 5.1"

    Relevant Pages

    • package creation broken on 5.1-CURRENT
      ... A couple of ports are creating broken bzip2 archives since I updated ... You can use the `bzip2recover' program to attempt to recover ... data from undamaged sections of corrupted files. ... kernel problem, but the build chroot is being populated with a ...
      (freebsd-current)
    • Re: kernel-source-2.5.69.tar.bz
      ... > Who do I contact about a bad *.deb file? ... > You can use the `bzip2recover' program to attempt to recover ... > data from undamaged sections of corrupted files. ... > When I run bzip2recover, I get alot of smaller files. ...
      (Debian-User)
    • Re: kernel-source-2.5.69.tar.bz
      ... > Who do I contact about a bad *.deb file? ... > You can use the `bzip2recover' program to attempt to recover ... > data from undamaged sections of corrupted files. ... > When I run bzip2recover, I get alot of smaller files. ...
      (Debian-User)