Skip to content
Snippets Groups Projects
Commit cabb5529 authored by Yorhel's avatar Yorhel
Browse files

Use uint64_t instead of ino_t

POSIX defines ino_t to be of an unsigned integer type, and searching
around the net didn't tell me of any definitions conflicting that. So
every ino_t can be represented in an uint64_t. (Assuming that is the
largest integer type in use for an inode number, but I'm sure that
assumption will hold for a while)

(dev_t, on the other hand, is a bit messier. Still figuring out what to
do with that.)
parent a61c784b
No related branches found
No related tags found
No related merge requests found
......@@ -16,6 +16,7 @@ AC_CHECK_HEADERS(
# Check for typedefs, structures, and compiler characteristics.
AC_TYPE_INT64_T
AC_TYPE_UINT64_T
AC_SYS_LARGEFILE
AC_STRUCT_ST_BLOCKS
......
......@@ -49,7 +49,7 @@ static dev_t curdev; /* current device we're scanning on */
/* Populates the struct dir item with information from the stat struct. Sets
* everything necessary for output_dir.item() except FF_ERR and FF_EXL. */
static void stat_to_dir(struct dir *d, struct stat *fs) {
d->ino = fs->st_ino;
d->ino = (uint64_t)fs->st_ino;
d->dev = fs->st_dev;
if(S_ISREG(fs->st_mode))
......
......@@ -61,7 +61,7 @@
struct dir {
struct dir *parent, *next, *prev, *sub, *hlnk;
int64_t size, asize;
ino_t ino;
uint64_t ino;
int items;
dev_t dev;
unsigned char flags;
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment