Comment 8 for bug 271956

Thanks all. I'll likely be submitting a similar "update" bug for
makedumpfile 1.3.0 when it is released. Turns out the bug I was
encountering still existed in 1.2.9 but I worked with the upstream dev
to resolve it and 1.3.0 is now in "rc2" status

Additionally, in Ben's original commit he appears to have introduced a
bug when he performed "Use _LARGEFILE_SOURCE and _LARGEFILE64_SOURCE
instead of _FILE_OFFSET_BITS=64 for correct compilation." Without
FILE_OFFSET_BITS=64, makedumpfile fails on my system with 4GB of
memory. Simply adding this flag back in causes it to work. Next
upstream version will have all three flags included. Should I file a
bug or just wait for 1.3.0 and file an "update" bug?

-Kevin

On Tue, Sep 30, 2008 at 11:08 PM, Martin Pitt <email address hidden> wrote:
> Fixed to match current intrepid version, checked, and sponsored the
> upload. Will make it into intrepid after beta freeze. Thank you!
>
> ** Changed in: makedumpfile (Ubuntu)
> Status: New => Fix Committed
>
> --
> Upgrade to new upstream version 1.2.9
> https://bugs.launchpad.net/bugs/271956
> You received this bug notification because you are a direct subscriber
> of the bug.
>