Unix and Mac compilers download location

[Ice Cream Jonsey]

2019 EDIT:

Mac and Unix source is from the same repo. I need to link compiled versions somewhere, although a simple make worked great.

https://bitbucket.org/0branch/hugo-unix/downloads/

I use the Unix and Mac one every day now, compiling a really large work in progress.

However, if you grab these out of the repo and have problems, please let me know. I'm worried I might have screwed up a check-in.

[Roody_Yogurt]

Just making a note that Nikos has been adding fixes to the Unix repo lately.

Everything is coming up Hugo! :mrgreen:

[Ice Cream Jonsey]

Yeah, I gotta check out those changes, rebuild and start using that on the linode to build Cyberganked. (I do it every day at 8:00 AM as-is over there. I think it runs Ubuntu.)

Also, Nikos, every time you have a new Windows release of Hugor, I do make the change and begin using it when I write Cyberganked. Just wanted to let you know that your releases do not go off into the void.

[RealNC]

Note that the changes I pushed only fix some "one in a million chance of happening" bugs.

I think though it might be a good idea to activate the issue tracker for the project, and file known bugs there. I think Marc is the only one who can enable that.

[RealNC]

Also, do you guys really prefer Mercurial? Compared to Git, whenever I need to use Mercurial for something, feels like going from a Superautomatic Espresso Machine to a can of instant coffee, a cup and a spoon :-P

[Roody_Yogurt]

[Hugo] Ellison says (to marc), "Nikos requests that you activate the issue tracker on the unix Hugo repo: http://www.joltcountry.com/phpBB2/viewtopic.php?t=9511"
[Hugo] marc says, "done"
[Hugo] marc says, "and anonymous users can create issues"
[Hugo] marc says, "hopefully that doesn't get spammy (i doubt it)"
[Hugo] marc | https://bitbucket.org/0branch/hugo-unix/issues
[Hugo] Ellison says, "cool!"

And I have no preference when it comes to repos.

[Ice Cream Jonsey]

Updated the top post with https://bitbucket.org/0branch/hugo-unix which is for Mac and Unix.

[Tdarcos]

Also, do you guys really prefer Mercurial? Compared to Git, whenever I need to use Mercurial for something, feels like going from a Superautomatic Espresso Machine to a can of instant coffee, a cup and a spoon :-P

Personally I just kept clients for all three (Mercurial, Subversion, and Git) on my PC so whatever project I looked at I could always do a retrieve of the sources no matter what flavor of version / source code sotftware

[Tdarcos]

they were using.

(i accidentally hit Submit on the previous posting when I meant to hit Preview. Isn't it typical, on an Android tablet you can bang on the button you want to click sometimes ten times before it responds, but hit the wrong button and it always activates on the first slightest touch.)

[Roody_Yogurt]

Because it takes too long to find it every time I need it and I end up searching all of these pages to no avail, this is the current location of the unix/mac compilers:

https://github.com/hugoif/hugo-unix

[Ice Cream Jonsey]

I'm gonna pin it!

[Roody_Yogurt]

In the end, I was unable to compile it myself and just downloaded your binaries off of the IF Archive, so it's great that those are there!

[Ice Cream Jonsey]

I'm gonna pi--

I pinned it!

[Ice Cream Jonsey]

My work computer is of the wrong chipset for the compiler. :(

[pinback]

The work laptop is to only be used for work-related purposes.

[Roody_Yogurt]

My work computer is of the wrong chipset for the compiler. :(

You're saying that your work computer can't even make the current Hugo package (https://github.com/hugoif/hugo-unix)? Or are you trying to use your pre-compiled binaries?

(I never updated my contribution to this thread, but I have since successfully built the Hugo package, which helped me find some of those interpreter bugs I found last year)

[Ice Cream Jonsey]

Oooh good point, I hadn't thought about compiling it on the computer itself.

This is my impression, I could be wrong:

There's two chipsets for Macs now, "Apple silicon" and Intel. I think the Apple one is new. It certainly came after the binary I made and was using. Our work computers are Apple silicon, so when I tried to use it, something - either the compiler itself or the OS or whatnot - said, hey dummy, this doesn't work on Apple silicon.

If recompiling it on an Apple silicon Macbook is all that is needed, I think I can try that! I would be surprised if that is all that is needed, but we'll see!

[Jizaboz]

Our work computers are Apple silicon

I'm out.

[Roody_Yogurt]

I've been waiting for an update on this. I don't fully understand how all of this works so I could be mistaken, but I would think that compiling the binary on the work computer, using whatever c compiler that Apple silicon chipset computer has, would produce a binary that chipset can run. I'm not sure, though! I want an update!

[ICJ away from home]

I tried to compile it, but it did not work.

Code: Select all

"_wtimeout", referenced from:
      _hugo_timewait in hegcc.old: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [he] Error 1
make: *** [all] Error 2[/code[