Unix and Mac compilers download location

by **Roody_Yogurt** » Sat Mar 15, 2025 4:40 pm

My reasoning is this- I googled "timeout"/"wtimeout" and "arm64" together. I would think that if curses had incompatible functions and that those were some of them, there would be some google hits verifying that (even if my google-fu when it comes to Linux-y things is pretty hit and miss). When no such hits came up, it made me think, well, maybe it's a lack of installation or the installation itself (googling "curses" and "arm64" mainly brings up information on installing the right version).

Anyhow, sorry to harp on this. Recently, I've been in a mood where I have wanted to find answers for all of the mysteries from weeks past before I go seek out new problems myself.

by **Ice Cream Jonsey** » Sat Mar 15, 2025 10:45 am

Sorry, I didn't see your email! I wanted to double check but I haven't had a chance to yet.

by **Roody_Yogurt** » Sat Mar 15, 2025 8:44 am

Whoops, pretend I didn't mess that up.

by **Roody_Yogurt** » Sat Mar 15, 2025 8:43 am

ICJ away from home wrote: Fri Feb 14, 2025 1:22 pm 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[
[/quote]

It seems _wtimeout is a call to curses, so now I'm thinking that possibly your work computer doesn't have curses installed.

by **Roody_Yogurt** » Fri Feb 14, 2025 2:09 pm

Chris Spiegel, Gargoyle developer guy, has recently submitted several arm64-related updates to the Gargoyle project.

Here is his github page:
https://github.com/cspiegel

Maybe ask him to look at it?

by **ICJ away from home** » Fri Feb 14, 2025 1:22 pm

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[

by **Roody_Yogurt** » Fri Feb 07, 2025 9:46 pm

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!

by **Jizaboz** » Mon Feb 03, 2025 2:03 am

Ice Cream Jonsey wrote: Fri Jan 31, 2025 2:46 pm Our work computers are Apple silicon

I'm out.

by **Ice Cream Jonsey** » Fri Jan 31, 2025 2:46 pm

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!

by **Roody_Yogurt** » Fri Jan 31, 2025 1:35 pm

Ice Cream Jonsey wrote: Thu Jan 30, 2025 8:46 pm 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)

by **pinback** » Fri Jan 31, 2025 7:21 am

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

by **Ice Cream Jonsey** » Thu Jan 30, 2025 8:46 pm

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

by **Ice Cream Jonsey** » Tue Feb 06, 2024 8:37 pm

I'm gonna pi--

I pinned it!

by **Roody_Yogurt** » Tue Feb 06, 2024 4:04 pm

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!

by **Ice Cream Jonsey** » Mon Feb 05, 2024 4:47 pm

I'm gonna pin it!

by **Roody_Yogurt** » Mon Feb 05, 2024 4:42 pm

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

by **Tdarcos** » Mon Sep 02, 2019 9:13 pm

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.)

by **Tdarcos** » Mon Sep 02, 2019 9:06 pm

RealNC wrote: Mon Mar 23, 2015 12:13 pm 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

by **Ice Cream Jonsey** » Tue Feb 19, 2019 9:01 am

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

by **Roody_Yogurt** » Mon Mar 23, 2015 1:34 pm

[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.

Unix and Mac compilers download location

Post a reply

Expand view Topic review: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re: Unix and Mac compilers download location

Re:

Re: Unix and Mac compilers download location