<SeanTAllen>
did you previously build wallaroo or machida in this repository before?
<t0m>
i did, but i rm -rf'd the directory and started over. should i do that again?
<SeanTAllen>
the directory being ".deps" in machida?
<SeanTAllen>
`make clean` in the `machida` directory should restore you to a default state
<SeanTAllen>
and you can then do
<SeanTAllen>
`make`
<t0m>
no, in machida/
<SeanTAllen>
sorry, i dont understand what "in machida/" means in that context
<t0m>
the directory i ran make in, was machida no .deps. sorry
<SeanTAllen>
sorry, i dont understand
<SeanTAllen>
in machida
<SeanTAllen>
do
<SeanTAllen>
make clean
<SeanTAllen>
then
<SeanTAllen>
make
<SeanTAllen>
you should be good then unless there's something you did that im not aware of
<t0m>
besides running this on my local and a cloud linux machine, i don't think i did anything out of the documentation
<SeanTAllen>
it would appear at some point you ran `make` for machida on `master` before checking out `0.4.1` and when you ran it on `0.4.1` the dependencies had a conflict but that is easy enough to fix
<SeanTAllen>
`make clean`
<SeanTAllen>
the
<SeanTAllen>
`make`
<SeanTAllen>
and you should be good
<t0m>
sorry, one more. environment variable $CC undefined, using gcc as linker
<SeanTAllen>
was it a warning or an error?
<SeanTAllen>
ive never seen that as an error, only as a warning
<SeanTAllen>
in the `machida` directory, can you do `ls build/` and put the output here
<SeanTAllen>
if that was a warning (as i expect) then you should see a `machida` executable in `machida/build` ls output
<t0m>
no such file or directory
<t0m>
the real error is: unable to link: gcc -o /home/wallaroo/wallaroo-tutorial/wallaroo/machida/build/machida -O3 -march=x86-64 -mcx16 -latomic -fuse-ld=gold /home/wallaroo/wallaroo-tutorial/wallaroo/machida/build/machida.o -L"/home/wallaroo/wallaroo-tutorial/wallaroo/machida/build" -Wl,-rpath,"/home/wallaroo/wallaroo-tutorial/wallaroo/machida/build" -L"../lib/" -Wl,-rpath,"../lib/"
<t0m>
yes, now i'm getting a few erorrs like: /usr/bin/ld.gold: error: /home/wallaroo/wallaroo-tutorial/wallaroo/machida/build/machida.o: requires
<t0m>
dynamic R_X86_64_32 reloc which may overflow at runtime; recompile with -fPIC
<SeanTAllen>
@strmpnk when you built on artful did you get that error?
<strmpnk>
Ah. Yes. ponyc doesn't default to pic unless you build it that way. you can add PONYFLAGS="--pic" to make. You may need to make clean.
<SeanTAllen>
PIC will be the death of me, i wonder why artful gets that issue but not trusty or xenial
<strmpnk>
Someday we'll have to teach pony to autodetect systems that require PIC.
<SeanTAllen>
so t0m
<SeanTAllen>
make clean
<SeanTAllen>
make PONYFLAGS="--pic"
<SeanTAllen>
sorry
<SeanTAllen>
make clean
<SeanTAllen>
make PONYFLAGS="--pic"
<SeanTAllen>
oops had the right the first time
puzza007 has quit [*.net *.split]
tourdownunder has quit [*.net *.split]
<SeanTAllen>
jonbrwn: will be updating the instructions accordingly to include artful
tourdownunder has joined #wallaroo
puzza007 has joined #wallaroo
<t0m>
sorry i'm still running into the same error after running make clean and make PONYFLAGS="--pic"
<SeanTAllen>
one moment
<SeanTAllen>
can you try `make PONYCFLAGS="--pic"` ?
<strmpnk>
Sorry. My bad. It's PONYCFLAGS (I forget the C in there).
<t0m>
no worries, i'm kidnapping the morning from yall
<SeanTAllen>
all good t0m
<SeanTAllen>
?
<t0m>
sorry had to step away quick, it's writing ./machida, but cannot find -lpython-wallaroo, i was digging into it but got sandwich distracted
<SeanTAllen>
what's in machida/bin/ ?
<SeanTAllen>
you should have some errors prior to that error
<t0m>
libpython-wallaroo.a and python-wallaroo.o
<SeanTAllen>
so python-wallaroo exists
<jonbrwn>
t0m: I'm going to spin up a vagrant box and test things out with artful so you don't keep hitting a wall
<jonbrwn>
I'll let you know when I have something useful for you
<t0m>
i'm doing everything on an azure machine, i can give you the credentials and you can see where i'm going wrong if you want
<t0m>
the docker container ran, i can always switch gears into it
<jonbrwn>
would probably be easier to start from scratch on my end
<jonbrwn>
but if it ends up that you did the same things we can debug on yours
cmeiklejohn has quit []
cmeiklejohn has joined #wallaroo
<t0m>
i followed the ubuntu setup and only missed installing snappy. it's your call
nisanharamati has joined #wallaroo
<jonbrwn>
t0m: assuming you're running `make` from the machida directory, can you run this: `make PONYCFLAGS="--pic --output=./build --path=./build"`
<t0m>
running
<t0m>
that ran with no issues
<nisanharamati>
re ^ I still get the `fPIC` issue consistently (also on Ubuntu Artful)... I've resorted to symlinking my ponyc bin
<t0m>
would make build-giles-all build-utils-cluster_shutdown-all PONYCFLAGS="--pic --output=./build --path=./build" be the next commands to run?
<strmpnk>
You can add the --pic call to rules.mk but it's nice to avoid that. Locally I use a compiled version of pony which defaults to pic so no flags are needed.
<strmpnk>
(When compiling pony you do something like `make default_pic=true`)
<strmpnk>
I keep LTO off for now but that's not hard to get working unless you have many versions of LLVM installed at once.
<SeanTAllen>
jonbrwn: can you create an update on the examples repo to change it from pointing at the blog for info about Wallaroo version to being in the README and update the blog post to note the version?