Open kayloehmann opened 1 year ago
Hello, not a mac person but someone else can help you on build from code questions.
Just wanted to make sure you know there is a premade easy to use Binary already. you can download and don't need to build it from code.
Get it here https://github.com/pine64/blisp/releases
Thanks for pointing this out, I tried it before and got this result:
➜ firmware sudo ./blisp write -c bl70x --reset Pinecilv2_DE.bin
sudo: ./blisp: command not found
The blisp file is in the same folder as Pinecilv2_DE.bin
Thanks for pointing this out, I tried it before and got this result:
➜ firmware sudo ./blisp write -c bl70x --reset Pinecilv2_DE.bin sudo: ./blisp: command not found
The blisp file is in the same folder as Pinecilv2_DE.bin
I will try to take a guess based on my knowledge since Mac people are not around yet.
sudo ./blisp write -c bl70x --reset Pinecilv2_EN.bin
Yes, that is exactly what I did. firmware is just the folder that contains the blisp file and the bin. Still:
sudo: ./blisp: command not found
Maybe it is an issue with the fact that blisp has not be compiled for arm architecture (M1).
Oic in that case. we need to wait for @gamelaster
It's not clear which exact architectures the macOS binary covers.
I just got it working by setting permissions like this: chmod +x ./blisp
Thanks guys for helping out!
@kayloehmann also if you feel like it you could join Pinecil live chat channel. see what people think. it can be joined from either Discord or telegram or matrix. https://wiki.pine64.org/wiki/Pinecil#Live_Community_Chat
someone else was saying in live Chat just now that there is an issue with Build from Code for MacOS users that has not been fixed yet.
@kayloehmann someone else also in live chat says they got blisp to work with M1 . you probably saw chat before I could post this image.
have to set permissions . I'm not Mac person and I had to ask around that is often why getting in the live chat is good. lots of people there with different experience.
cd blispFolder
# move into the folder with blisp and BIN file.
ls -l
# to see permissions
chmod +x ./blisp
# make blisp executable
sudo ./blisp write -c bl70x --reset Pinecilv2_EN.bin
run the command inside the Blisp folder.
Yes! It solved it. Thx.
While the x86_64 release of blisp
will work on an Apple Silicon Mac, I still wanted a native arm64 version. The fix for compiling from source for me was to add the header #include <mach-o/dyld.h>
inside the __APPLE__
ifdef at https://github.com/pine64/blisp/blob/de4a9cd5e67084cca07727071c23bac1f074a3a2/tools/blisp/src/util.c#L7-L13
The fix for compiling from source for me
@dotsam is this something that could be submitted as a Pull Request to the blisp repo so that it will automatically work for other ARM64 Mac people?
is the new Mac binary made from arm64 able to be zipped and shared with people in this repo?
I thought I'd already committed that. It's definitely a required and needed fix.
It's another reason I'm so skeptical that there's functional CI for this project. If it won't compile, there's no way that CI should be working...
On Tue, Apr 11, 2023 at 7:03 PM river-mochi @.***> wrote:
Reopened #34 https://github.com/pine64/blisp/issues/34.
— Reply to this email directly, view it on GitHub https://github.com/pine64/blisp/issues/34#event-8979154272, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCSD37VDN2I7XJ5DP66IT3XAXWM5ANCNFSM6AAAAAAWYB7FNU . You are receiving this because you were assigned.Message ID: @.***>
There is working CI. But only for X86 Macs 😉
There is working CI. But only for X86 Macs 😉
CI works for x86 and M1 Macs right now. the M1 macs we confirmed yesterday, they just need to do:
chmod +x
to make the Blisp executable
someone told me that if you repackage it and do the permission change before you zip it. then mac people will not need to to the chmod +x. don't know if you have time to do that? and then rezip it?
@dotsam Thx, also working for Apple M2.
If the build doesn't create an executable with execute permissions, the build system should be fixed, IMO. The error shown (can't find) is not consistent with missing execute permissions, which would look like this:
$ touch booger $ ./booger zsh: permission denied: ./booger
Still, this is consistent on Mac, Linux, *BSD, and others. Since it's now confirmed working everywhere, I'm going to close this. Thanx for al that participated.
The patch in the above comment has not been integrated yet.
@ohmantics it still doesn't compile?
@ohmantics it still doesn't compile?
@gamelaster No, it still fails. The patch in the above comment needs to be hand-applied (the additional #include statement).
Hi there,
I just tried to compile blisp flasher on an M1 Mac and got the following error. Could you please have a look? Thx.