<halosghost>
and I'm now running into a set of errors whenever I try to compile anything
<halosghost>
/usr/bin/ld.gold: error: ./fb.o: requires dynamic R_X86_64_32 reloc against 'String_Trace' which may overflow at runtime; recompile with -fPIC
<halosghost>
/usr/bin/ld.gold: error: ./fb.o: requires dynamic R_X86_64_32 reloc against 'pony_personality_v0' which may overflow at runtime; recompile with -fPIC
<halosghost>
but
<halosghost>
I didn't run `ponyc -fPIC`, so I think it's talking about recompiling ponyc itself with -fPIC?
<halosghost>
thoughts?
<SeanTAllen>
yes, that is what it sounds like to me
<halosghost>
solid
<halosghost>
so I should tell the archlinux packagers to FixIt™? :P
jemc has joined #ponylang
<halosghost>
okay, in looking further into this, Arch just uses the upstream Makefile
<SeanTAllen>
how did you install Pony?
<halosghost>
through the official repos
<halosghost>
I'm gonna talk to the package maintainer and see if he can shed any light on it
<SeanTAllen>
im not sure if anyone has tried that recently
<SeanTAllen>
can you give the "install from source" directions for arch a try?
<halosghost>
sure
<halosghost>
the arch package is 0.2.1 the latest release
runehog has joined #ponylang
<SeanTAllen>
that's very old
<SeanTAllen>
we are working on getting a new release together and hopefully from there will have more regular releases
<SeanTAllen>
every tracks master at this point
<halosghost>
mm
<halosghost>
in that case
<SeanTAllen>
we have .rpm and .deb packages that get built automatically, not so much with pacman
<halosghost>
since arch makes a point of using the latest release, I'll hold off on opening a bug for arch
<halosghost>
someone should consider packaging a -git for the AUR for arch then :)
<SeanTAllen>
we are looking for someone to take over the release process. we had someone kindly step in and do a lot of work but its not something they can commit to at this point.
<halosghost>
I mean, I'd gladly throw together a -git package for the AUR
<SeanTAllen>
what's involved with that?
<halosghost>
assuming I get it to build correctly
<halosghost>
SeanTAllen: well, mostly, I copy the PKGBUILD that's used to build the main repo package and convert it to build from-source tracking the git master branch
<halosghost>
yeah, that's really it
<halosghost>
:)
<SeanTAllen>
sounds great
<halosghost>
oh
<halosghost>
incidentally
<halosghost>
building from-source gives me the same issue
<halosghost>
so
<halosghost>
yeah
<SeanTAllen>
we don't have a lot of arch users.
<SeanTAllen>
at one point it worked and someone was nice enough to put together the build instructions
<SeanTAllen>
if you could open an issue on the repo, perhaps someone in the community who uses arch might be able to diagnose.
<halosghost>
sure
<halosghost>
can do :)
<halosghost>
hmm
<halosghost>
just out of interest
<halosghost>
pony's compilation doesn't require loading any kernel modules, right?
<SeanTAllen>
if you can include the ld.gold version, that would be awesome
<SeanTAllen>
not that i am aware of
<halosghost>
okay, good
<halosghost>
it'd be really weird if it did anyway :)
gsteed has quit [Quit: Leaving]
<halosghost>
and sure, can do
<SeanTAllen>
thanks
<halosghost>
oh
<halosghost>
wait
<halosghost>
I figured it out
<halosghost>
-_-
<halosghost>
muhsilleh
<halosghost>
it wanted me to use `ponyc --pic`
<halosghost>
in retrospect, it makes sense that the error message would be so unhelpful (it's an error from gold, not ponyc)
<halosghost>
not a great experience though :)
<SeanTAllen>
could you open a PR against the README with a note about that for archlinux, if that error is encountered to do that?
<halosghost>
oh, sure
<SeanTAllen>
thank you.
<halosghost>
yeah
montanonic has joined #ponylang
<halosghost>
and I'll take a look at making a ponyc-git for the AUR
c355e3b has quit [Quit: Connection closed for inactivity]
montanonic has joined #ponylang
<halosghost>
doublec: weird; is there a chance that the .deb has ponyc statically compiled?
<doublec>
halosghost: I build from source
<halosghost>
doublec: any chance that you statically compiled it? :P
<doublec>
halosghost: not unless the default "make config=release" does that
<halosghost>
yeah
<halosghost>
I figured not
<halosghost>
is there a chance that you have a CFLAGS exported globally that includes -fPIC?
<doublec>
halosghost: no, I don't have that, sorry
<halosghost>
welp
<halosghost>
¯\ʕ·ᴥ·ʔ/¯
montanonic has quit [Ping timeout: 244 seconds]
<doublec>
Isn't linux fun :)
<halosghost>
indeed
<halosghost>
now I can continue pining for typeclasses in pony
<halosghost>
:)
<doublec>
haha, add all the things!
<halosghost>
indeed
<halosghost>
how I wish overloading would just go away and we could just have typeclasses
<halosghost>
Haskell has ruined me
Dyserna__ has joined #ponylang
Dyserna_ has quit [Ping timeout: 250 seconds]
Perelandric has quit [Ping timeout: 264 seconds]
Goba_ has quit [Ping timeout: 264 seconds]
srenatus[m] has quit [Remote host closed the connection]
M-hrjet has quit [Remote host closed the connection]
srenatus[m] has joined #ponylang
M-hrjet has joined #ponylang
<emilbayes>
SeanTAllen: Did you find anyone to help out with the website?
jemc has quit [Quit: WeeChat 1.4]
jemc has joined #ponylang
mcguire1 has quit [Ping timeout: 265 seconds]
jemc has quit [Ping timeout: 244 seconds]
Matthias247 has joined #ponylang
gsteed has joined #ponylang
c355e3b has joined #ponylang
_andre has joined #ponylang
<SeanTAllen>
emilbayes: not yet
<otremblay>
Context: I want to write a toy parser in Pony to hone my skills. Say I wanted to break apart all the UTF8 codepoints in a string and pass the individual characters to an actor, I'm tempted to use the "runes" iterator and pass each codepoint to my actor in charge of the parsing; how do I make U32 back into a single UTF-8 character?
<otremblay>
"from_utf32" seems to do what I want, I think
<emilbayes>
SeanTAllen: What work has been done on besides the logo?
<SeanTAllen>
emilbayes: i started work a while back of a tuft css theme for hugo that i was going to use as the basis for something but i never got very far because i'm not so good with the implementing design
<emilbayes>
SeanTAllen: Cool, I did read that issue
<emilbayes>
I might be interested
<emilbayes>
as in, I'll propose something and see how it fares
<emilbayes>
but I will not commit to anything, was just curious if anyone else was working on it. I really want to see pony succeed
<SeanTAllen>
ok
<SeanTAllen>
sounds good
<Candle>
On that "work in progress" note, I have a working Maven plugin for pony now, If I get the time to sit down this evening and publish it, I will.
<halosghost>
oh snap! There's a native {I,U}128
<halosghost>
why no F128? ):
<Candle>
It is very much work in progress, and there are some decisions that I've made that may want input from other people trying to use it!
<halosghost>
actually, I'd love to see an F8 and F16 too even though they are essentially useless for anything other than being fun
gsteed has quit [Quit: Leaving]
jemc has joined #ponylang
aturley has joined #ponylang
unbalancedparen has quit [Quit: WeeChat 1.4]
unbalancedparen has joined #ponylang
aturley has quit [Ping timeout: 265 seconds]
aturley has joined #ponylang
gsteed has joined #ponylang
amclain has joined #ponylang
aturley has quit [Ping timeout: 244 seconds]
jemc has quit [Ping timeout: 276 seconds]
aturley has joined #ponylang
aturley has quit [Ping timeout: 244 seconds]
aturley has joined #ponylang
mcguire1 has joined #ponylang
jemc has joined #ponylang
_andre has quit [Quit: leaving]
<jemc>
halosghost: I don't think LLVM provides implementations for F8 and F16
<jemc>
for F128 - it could probably be done if someone had a need
<jemc>
would probably require fallback handwritten implementations of its methods for platforms that did not support the native128 operations
<jemc>
just as U128 and I128 do (see their implementations, with `ifdef native128 ... else ... end`
<halosghost>
yeah, nothing provides F8 and F16 because everyone is mean
<halosghost>
and yeah, F128 would need to be platform-dependent
<halosghost>
though, I think llvm might automatically handle that
<halosghost>
¯\ʕ·ᴥ·ʔ/¯
gsteed has quit [Quit: Leaving]
<jemc>
I'm not totally sure, but it looks like it's not handled by LLVM for I128 and U128 - see the code referred to in my earlier comment
mcguire1 has quit [Ping timeout: 252 seconds]
<halosghost>
well, llvm itself has arbitrarily-sized fixed with integer arithmetic
<halosghost>
so, I'm not sure what you mean about that
<halosghost>
(incidentally, I really wish higher-level languages offered arbitrarily-sized fixed-width integer arithmetic, but that's a different thin)
<halosghost>
s/n)/ng)/
<jemc>
according to LLVM docs, not all platforms support 128 - LLVM may support it, but that doesn't mean it's guaranteed to work on your target triple
<jemc>
when it comes to user-defined limits on integer type sizes, you may be interested in checking out value-dependent types, an academic project in expanding Pony's type system that should be wrapping up soon and merged into the main language