ReturnInfinity/BareMetal-OS

setup.sh cp command fails on macOS

Closed this issue · 5 comments

placrosse commented

It appears to be back again. I did a fresh git clone today, ran setup.sh, and:

Entering /Users/paul/dev/BareMetal-OS/src/BMFS/utils
 CC      /Users/paul/dev/BareMetal-OS/src/BMFS/utils/bmfs.o
 LD      /Users/paul/dev/BareMetal-OS/src/BMFS/utils/bmfs
Updating /Users/paul/dev/BareMetal-OS/output/bin/bmfs
cp: illegal option -- -
usage: cp [-R [-H | -L | -P]] [-fi | -n] [-apvXc] source_file target_file
       cp [-R [-H | -L | -P]] [-fi | -n] [-apvXc] source_file ... target_directory

'cp --update' appears in several places, and on Mac the 'cp' command does not support the '--update' option. Some people have suggested using 'rsync' to get similar behavior (as it does allow the '--update' option).

Deleted user commented

Thanks for bringing this up again. I'll fix it real quick.

Deleted user commented

Should be fixed by 29281be.

Please let me know if this fixes the build on macOS.

placrosse commented

That fixed the first issue from running 'setup.sh'. Got another one now from it. Want a new issue? Or just post here:

Entering /Users/paul/dev/BareMetal-OS/src/AlloyLoader
ld: unknown option: -T
Deleted user commented

See #21. You need a recent release of GCC installed.

placrosse commented

Ah, thanks Taylor. I knew that sounded familiar. I thought I had gcc installed, but it must've been removed while I was upgrading MacOS recently (along with a bunch of other things).