Opened 11 years ago

Last modified 10 years ago

#36748 new defect

ext2fuse: mounted filesystem not readable (PPC or 32bit issue?)

Reported by: mklein-de (Michael Klein) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: haspatch Cc: mkae (Marko Käning), cooljeanius (Eric Gallager)
Port: ext2fuse

Description

  • ext2fuse 0.8.1
  • fuse4x 0.9.2

File systems mount ok on 10.5.8/PPC, but any operation on the mounted file system results in an Input/output error.

$ pkg-config fuse --cflags
-D_FILE_OFFSET_BITS=64 -D_DARWIN_USE_64_BIT_INODE -I/opt/local/include/fuse  

After rebuilding ext2fuse with -D_DARWIN_USE_64_BIT_INODE everything seems to work fine

Attachments (5)

Portfile.diff (743 bytes) - added by mklein-de (Michael Klein) 11 years ago.
Portfile.2.diff (893 bytes) - added by mklein-de (Michael Klein) 11 years ago.
Portfile.3.diff (997 bytes) - added by mklein-de (Michael Klein) 10 years ago.
Updated Portfile
Portfile.4.diff (1.0 KB) - added by mklein-de (Michael Klein) 10 years ago.
Updated Portfile
main.log (79.1 KB) - added by mf2k (Frank Schima) 10 years ago.

Download all attachments as: .zip

Change History (15)

Changed 11 years ago by mklein-de (Michael Klein)

Attachment: Portfile.diff added

comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Is using 64-bit inodes safe for all versions of OS X (Tiger and up) on all four architectures? I don't know.

comment:2 in reply to:  1 Changed 11 years ago by mklein-de (Michael Klein)

Replying to ryandesign@…:

Is using 64-bit inodes safe for all versions of OS X (Tiger and up) on all four architectures? I don't know.

Me neither. I'm attaching a new patch that makes the Portfile use pkg-config instead.

Changed 11 years ago by mklein-de (Michael Klein)

Attachment: Portfile.2.diff added

comment:3 Changed 11 years ago by mkae (Marko Käning)

Cc: mk@… added

Cc Me!

comment:4 Changed 10 years ago by cooljeanius (Eric Gallager)

Is this still relevant now that fuse4x has been replaced by osxfuse?

comment:5 Changed 10 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

comment:6 in reply to:  4 ; Changed 10 years ago by mklein-de (Michael Klein)

Replying to egall@…:

Is this still relevant now that fuse4x has been replaced by osxfuse?

yes, the issue persists with osxfuse

Changed 10 years ago by mklein-de (Michael Klein)

Attachment: Portfile.3.diff added

Updated Portfile

comment:7 Changed 10 years ago by mf2k (Frank Schima)

@michael.klein: Your patch will need to be updated because the revision of this port is currently 2. Why are you putting configure.cflags and cppflags arguments in a pre-configure block?

comment:8 in reply to:  7 Changed 10 years ago by mklein-de (Michael Klein)

Replying to mf2k@…:

@michael.klein: Your patch will need to be updated because the revision of this port is currently 2. Why are you putting configure.cflags and cppflags arguments in a pre-configure block?

that's because of the exec, otherwise pkg-config would be executed every time the Portfile is read (IIRC)

Changed 10 years ago by mklein-de (Michael Klein)

Attachment: Portfile.4.diff added

Updated Portfile

comment:9 Changed 10 years ago by mf2k (Frank Schima)

This patch does not build for me on Mavericks. attaching the main.log.

Changed 10 years ago by mf2k (Frank Schima)

Attachment: main.log added

comment:10 in reply to:  6 Changed 10 years ago by mklein-de (Michael Klein)

Replying to michael.klein@…:

Replying to egall@…:

Is this still relevant now that fuse4x has been replaced by osxfuse?

yes, the issue persists with osxfuse

ah, forget it. osxfuse is Intel-only anyway. Don't know what I tested back then.

now that fuse4x has been replaced by osxfuse means that there is no way to get ext2fuse running on a PPC Mac at all.

Time to move to Linux, it seems,

Note: See TracTickets for help on using tickets.