![]() (Someone more classic-mac oriented then me can tell you the best way to do this. Then you can download the System 7.5 Network Access Disk and image it to a real floppy. You can download that in a bunch of floppy-disk size pieces here. The simplest thing is probably putting System 7.5.3 on it. Once you're certain the Mac has a working hard disk if your PC has a floppy drive you can use use that to spoonfeed-over a system 7 upgrade. ![]() If you don't, well, you're obviously not going to get too far. make sure you actually *have* a working hard disk in the system. I'm concerned that your system may actually be booting from that, not the hard disk. The reason I ask is that the Mac Classic has a built-in System. That said, I had a similar problem getting an OS onto a bare Quadra and solved it, so.įirst off, it should probably be clarified, what OS does your Classic have on it again? There's no such thing as Mac OS "6.8.1". test/cctest/test_url.cc '-DV8_DEPRECATION_WARNINGS' '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_DARWIN_USE_64_BIT_INODE=1' '-DOPENSSL_NO_PINSHARED' '-DOPENSSL_THREADS' '-DNODE_ARCH="arm64"' '-DNODE_WANT_INTERNALS=1' '-DHAVE_OPENSSL=1' '-DHAVE_INSPECTOR=1' '-D_POSIX_' '-DNODE_USE_V8_PLATFORM=1' '-DNODE_HAVE_I18N_SUPPORT=1' '-DNODE_PLATFORM="darwin"' '-DUCONFIG_NO_SERVICE=1' '-DU_ENABLE_DYLOAD=0' '-DU_STATIC_IMPLEMENTATION=1' '-DU_HAVE_STD_STRING=1' '-DUCONFIG_NO_BREAK_ITERATION=0' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DNGHTTP2_STATICLIB' -I./src -I./tools/msvs/genfiles -I./deps/v8/include -I./deps/cares/include -I./deps/uv/include -I./deps/uvwasi/include -I./test/cctest -I./deps/histogram/src -I./deps/icu-small/source/i18n -I./deps/icu-small/source/common -I./deps/zlib -I./deps/llhttp/include -I./deps/cares/src/lib -I./deps/nghttp2/lib/includes -I./deps/brotli/c/include -I./deps/openssl/openssl/include -O3 -gdwarf-2 -mmacosx-version-min=10.13 -arch arm64 -Wall -Wendif-labels -W -Wno-unused-parameter -Werror=undefined-inline -Wall -Wendif-labels -W -Wno-unused-parameter -std=gnu++1y -stdlib=libc++ -fno-rtti -fno-exceptions -fno-strict-aliasing -MMD -MF /Users/ryan/.nvm/.cache/src/node-v14.17.5/files/out/Release/.deps//Users/ryan/.nvm/.cache/src/node-v14.17.5/files/out/Release/obj.target/cctest/test/cctest/test_url.o.d.It's been a *long* time, so you'd probably be better served by someone with a fresher memory. deps/v8/src/compiler/code-assembler.h:528:12: note: in implicit copy constructor for 'v8::internal::TNode' first required hereĬ++ -o /Users/ryan/.nvm/.cache/src/node-v14.17.5/files/out/Release/obj.target/cctest/test/cctest/test_url.o. deps/v8/src/codegen/tnode.h:352:9: warning: definition of implicit copy constructor for 'TNode' is deprecated because it has a user-provided copy assignment operator ![]() deps/v8/src/codegen/interface-descriptors.h:12: deps/v8/src/compiler/code-assembler.h:17: In file included from /Users/ryan/.nvm/.cache/src/node-v14.17.5/files/out/Release/obj/gen/torque-output-root/torque-generated/exported-macros-assembler-tq.h:4: In file included from /Users/ryan/.nvm/.cache/src/node-v14.17.5/files/out/Release/obj/gen/torque-output-root/torque-generated/:22: In my opinion if I want to install 15.3 and you cannot find binaries, it's better to compile it on device instead of returning me a wrong binary (Intel one). I would vote to remove this as this is hidden, unintended side-effect and changes previous behaviour. Only then I have found out the culrpit: NVM is overriding architecture for any Node version below 16. We pinpointed the issue to them having x86 node binaries, instead of arm64 ones (as me and our M1 CI has had for months now).Īfter day of searching for the issue, and not understanding why even the 15.3 which is officially supported arm version of node is not properly installing. Imagine my surprise when their environment does not work. We are still on v14, because v15 is not supported by some of our packages, and v16 is not working with Realm. This was not ideal (built binaries would be better) but still ok.įast forward to now, rest of my team got the M1 macbooks, they followed my steps of nvm and node installation. Back then the NVM was returning 404 on binary download and then compiling node by itself. I have used NVM just when the M1 processors came out.
0 Comments
Leave a Reply. |