-
Notifications
You must be signed in to change notification settings - Fork 88
Mac Integer expression error #6
Comments
Can you post an error log please. I've never owned a mac but I'm willing to try to help you debug. |
Haven't received a reply in 7 days, going to close. |
For what it's worth, this is / was "declare -A", i.e. bash 4 language features not available in the (dusty old) version of bash 3 that OSX ships with. Coding down to bash 3 is a significant change. If you really want to use h265ize under OSX, it's easier to start by installing bash4 from homebrew or fink, I suspect.
|
So, having updated to bash4 with homebrew (quick! easy! guides all over the web!), this is more like it, I'll noodle with it a bit to see if I can make sense of it:
Mostly because getopt is doing something unexpected there (i.e. nothing at all) and the getopt args end up somehow getting passed to find later on? yech. |
@pfriedel What's you Also I will add a bash version check to inform the user if they are using an unsupported bash version. |
That's part of the hilarity:
The related man1 and man3 manpages are from 1999 and 1995, respectively, so "old" is probably safe. I dunno if
Editing the FILES=$() to see what it's doing, I see this, which related to #9 :
Additionally, OSX
...Which is, if nothing else, a known place. To sum up, OSX users:
Having done all that, it seems to work as well as I'm used to in Linux, barring the issues from #9 so with a bit of user hacking it seems to work moderately well? I'll give it some more testing to see what isn't actually working. |
Ah, there's a dependency on ffprobe as well - not having that seems like it knocks h265ize back a bit. You get the mac ffprobe binary the same place you get the ffmpeg binary: https://www.ffmpeg.org/download.html There's an expr and a date error in the logs, but that's getting nitpicky:
|
I actually laughed a few times while reading your last messages. The 1999 getopt was definitely funny. My man page is from December 2014. Unfortunately bash's builtin Just to be clear, in order to get h265ize running on a mac I would need to:
Also, if you don't mind, what version of OS X are you running? |
El Capitan, relatively recently installed. I'll see what's necessary in a clean install El Cap VM to see how much was just dumb luck from having been down this sort of road before versus it really being just that easy. It's probably more trouble than it's worth to try to merge the changes with OS detection wrapped around it, but a branch might be tolerable since it's only a few key lines to keep in sync. I'll sync it up after #9 closes and submit a diff - my find hack is definitely suboptimal, even if it works. The current code changes are here: To be honest, I was surprised how well it ported once the toolchain was brought up to speed, and installing the homebrew mods is pretty straightforward these days. A few other changes vs master here:
All of which are either noop with gnu tools (the awk won't hurt, but it doesn't need to be there, for example) or not unreasonable additions to the defaults array for interested parties to change to. Then OSX compatibility is "install necessary tools, change defaults header, let 'er rip". |
Cool, adding some OS detection, which is actually rather straight forward, and asking the user to change the hashbang plus install dependencies should be all it takes. BTW, the date at L518 is just converting
Thanks for all your work so far pfriedel. |
Running on mac throws integer expression errors on line 5 which appears to be the default settings.
Any suggestions for getting this to properly run on mac would be great.
Thanks.
The text was updated successfully, but these errors were encountered: