#8 par.exe generates corrupt PAK files on Windows

closed-fixed
nobody
None
5
2006-11-10
2006-11-09
No

The build outputs corrupt PAK files on Windows. The
Quake engines do their best to load the file and don't
emit clear diagnostics. The result is Quake simply
doesn't run with the PAK files that user's build on
their own.

The root cause of the problem is that par.c assumes
that off_t is a four byte value. On my Windows box and
with my version of gcc, off_t is an eight byte value.

I'm using gcc:

gcc (GCC) 3.4.4 (cygming special) (gdc 0.12, using dmd
0.125)

par.c should be fixed such that.

How Reproducible:
Every Time (when you have a strange gcc)

Steps to Reproduce:
1) par -c test.pak file1 file2
2) par -l test.pak

What Happens:
The second par command complains that test.pak is corrupt.

Expected Result:
The second par command says that test.pak contains
file1 and file2.

Discussion

  • David Costanzo

    David Costanzo - 2006-11-10
    • status: open --> closed-fixed
     
  • David Costanzo

    David Costanzo - 2006-11-10

    Logged In: YES
    user_id=109252

    I have checked in a fix for this. I don't think there is a
    need to release the fix, because I don't think this bug was
    present in any released files. But if you did sync-up to
    CVS and had this problem, try re-syncing.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks