Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Case-sensitive filesystems fail to build in/around code for HFSPlus #16

Open
emory opened this issue Oct 26, 2013 · 0 comments
Open

Case-sensitive filesystems fail to build in/around code for HFSPlus #16

emory opened this issue Oct 26, 2013 · 0 comments

Comments

@emory
Copy link

emory commented Oct 26, 2013

Case-sensitive filesystems (ZFS, any non-jhfs+ via NFS and even HFS+ if initialized as case-sensitive) will choke and fail due to not being able to find HFSPlus/X64/HFSPlus.efi — the "IA32" or "X64" subdirectory that contains that file should probably be called ia32 or x64 respectively.

Errors will begin starting with something like:

GenFds.py...
/Users/emory/Projects/CloverGrower/edk2/Clover/HFSPlus/HFSPlus.inf(22): error 000E: File/directory not found in workspace
    /Users/emory/Projects/CloverGrower/edk2/Clover/HFSPlus/X64/HFSPlus.efi
make: *** [fds] Error 14

And there may be others later in the build process.

I dug around a bit and saw a place in the CloverGrower.command it should be fixed but that won't fix it entirely. The tree it pulls from the svn repository will also need to be fixed and I don't know if it's appropriate to submit a routine that fixes it (if it sees that it's broken) in CloverGrower.command or if you'd rather they fix it upstream in Clover?

Workarounds:

Checkout the git repository for CloverGrower onto a case-insensitive filesystem and it should work smoothly.

Alternatively, users may "fix" the discrepancy by symlinking x64 to X64, ia32 to IA32 and, ahem, Ia32 and CloverGrower will build packages as expected.

Notes:

In my above example, /Users/emory/Projects is a ZFS filesystem that is mounted via NFS from a central fileserver that I keep my projects on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant