You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 calledia32
orx64
respectively.Errors will begin starting with something like:
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
toX64
,ia32
toIA32
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.The text was updated successfully, but these errors were encountered: