Current Server Time: 09:51 (Central Europe)

#apertus IRC Channel Logs

2019/10/03

Timezone: UTC


02:01
jhlink
joined the channel
06:03
Bertl_oO
off to bed now ... have a good one everyone!
06:03
Bertl_oO
changed nick to: Bertl_zZ
06:23
LordVan
joined the channel
07:15
BAndiT1983|away
changed nick to: BAndiT1983
07:33
sebix
joined the channel
07:33
sebix
left the channel
07:33
sebix
joined the channel
08:41
futarisIRCcloud
joined the channel
10:36
Bertl_zZ
changed nick to: Bertl
10:36
Bertl
morning folks!
11:01
futarisIRCcloud
left the channel
12:07
BAndiT1983
changed nick to: BAndiT1983|away
12:30
Spirit532
left the channel
14:30
jhlink
Morning!!
14:30
jhlink
Okay. Sorry for the MIA. Had to deal with some interview stuff.
14:31
jhlink
So, out of curiosity, how long does it typically take for one to build the beta firmware?
14:31
jhlink
I started the build yesterday, and it took a little longer than 5-10 minutes, so I went to bed to let it run overnight.
14:44
jhlink_
joined the channel
14:44
jhlink_
Err. Sorry. Internet dropped.
14:44
jhlink_
IF someone did reply to that question, I'd be ever so grateful if they could repeat it. :)
14:45
jhlink
left the channel
14:48
Bertl
the channel is logged, so you can check easily
14:48
jhlink_
Are the logs hosted on the site?
14:49
Bertl
http://irc.apertus.org/
14:49
jhlink_
Wow. That's insanely helpful.
14:49
jhlink_
And ridiculously cool.
14:50
Bertl
vup/anuejn probably know best how long it takes, btw :)
14:50
jhlink_
Awesome. Do you know when he's typically active?
14:51
jhlink_
Er. They*
14:51
Bertl
they are located in germany, so roughly european schedule
14:52
jhlink_
In the afternoons or evenings?
14:53
Bertl
mostly, yes
14:53
jhlink_
Um, I guess that was a little vague.
14:54
jhlink_
Morning, noon, or evenings? xD
14:55
sebix
left the channel
14:57
jhlink_
In any case, I had a question about building.
14:58
jhlink_
Is it normal to get a `stty: invalid integer argument: 'rows'` when invoking docker-make.sh?
14:58
Bertl
no idea
14:58
jhlink_
Got it.
14:59
jhlink_
How about this question. Is it normal to get a bunch of permission denied errors for creating symlinks to ca-certs when building the image?
15:01
RexOrCine|away
changed nick to: RexOrCine
15:05
Bertl
you are asking the wrong person here :)
15:05
Bertl
I have not checked the build process yet, so everything you say can be 'normal' or 'unexpected'
15:06
jhlink_
hahaha, okay, okay.
15:08
Bertl
ask me something about the hardware or the FPGA code and we are in business :)
15:09
jhlink_
Hahaha. Okay. I hope to ask you soon, but until then I want to make sure this build system is working.
15:09
jhlink_
I've never done it before, and I think it'd be such a useful skill to learn.
15:11
jhlink_
Out of curiosity... Does it matter what OS is used to build the firmware?
15:11
jhlink_
I'm on OSX, and I'm not sure if this was meant to be build solely in linux.
15:11
jhlink_
Or windows.
15:12
jhlink_
Kinda of a long shot, I know, but just reaching for straws. hahaha
15:13
RexOrCine
jhlink_: Most convenient solution would be for you to opt for a client btw - https://wiki.apertus.org/index.php/Join_the_Team#IRC
15:13
jhlink_
Is LimeChat not a client?
15:14
jhlink_
I don't mind switching, after all they all interact with IRC.
15:14
jhlink_
Er work with IRC.
15:15
Bertl
LimeChat is fine
15:15
Bertl
alternatively you can go for Pidgin (graphical) or irssi (commandline)
15:23
jhlink_
Whaaat? Didn't know there was a cmdline irssi... that's insane.
15:26
Bertl
well, IRC is much older than GUIs :)
15:27
jhlink_
True, true.
15:28
Bertl
nah, it's actually a lie
15:28
Bertl
GUIs existed since the 1960s
15:29
Bertl
while IRC was a replacement for MUT in 1988
15:45
namibj
jhlink_: I'd not try to build on OSX or windows.
15:46
jhlink_
Even with docker?
15:47
namibj
jhlink_: I'd recommend you get a virtual machine running ubuntu or archlnux (the latter needs a bit of manual work to get a gui out of it, but you're rewarded by a constantly up-to-date system).
15:48
namibj
jhlink_: docker kinda just uses the kernel to provide pseudo-virtualization. I honestly doubt binaries build for linux would run on osx in docker... Because the syscalls are different, and the libc the binary is compiled against/with lives inside the docker image.
15:52
namibj
if you really just want a builsystem, I'd think archlinux would loose most arguments against it, just because it by default leaves you to add an user, maybe enable dhcpcd, and then you can log on in a console, or install and enable an ssh server. Aftwerwards it mostly doesn't get in your way (you have to manually install and activate, osmetimes configure further software like a graphical environment
15:52
namibj
though). It shouldn't really matter what you go for, however.
15:53
jhlink_
Should using a Ubuntu/Arch linux VM be added onto the makesfiles/README.md then?
15:54
jhlink_
I didn't know that I running makesfiles/docker-maker.sh on OSX isn't advised.
15:54
namibj
don't think so, necessarily, unless it already expresses support for anything except linux as far as building goes.
15:55
namibj
I recall it being based on archlinux, and I don't think that is officially supported to be build on anything except arch linux using the offical toolchain at least.
15:55
jhlink_
Ah, well. Right now, I'm trying to run the docker vupvupvup/axiom_build image on OSX.
15:55
Bertl
IIRC, docker starts a VM on Microsoft Windows and Apple OSX
15:56
jhlink_
Hopefully, I can figure this out. If not, I'll create a linux VM.
15:56
jhlink_
And run the docker-make script there.
15:56
Bertl
so the docker container should get everything it requires there
15:56
jhlink_
Right?
15:56
jhlink_
Eh, but what do I know. Still hackin' away. hahaha
15:57
namibj
^
16:07
namibj
If it's actually building it from source, I'd expect a 3GHz quadcore skylake to take about an hour, but a lot of it can be parallized, so cores would be able to bring it down to 5 minutes I think.
16:08
jhlink_
Can someone advise me on how I can look at the contents of vupvupvup/axiom_build in Docker?
16:11
namibj
jhlink_: checking.
16:16
jhlink_
Hey namibj, I think I got it.
16:16
jhlink_
I just copied portions of the docker command in the make file.
16:18
namibj
ha, ok
16:20
namibj
from what I saw there, it doesn't look like it'd work on osx though. just based on it trying to provide a priviledged container, which I 1) consider rather bad for security reasons (you giv ethe build tools root, essentially)
16:20
namibj
, and 2) should be incompatible with running the content in a VM.
16:23
namibj
Bertl: can the fpga code be built without me requiring the xillinx pay-me-upfront software? I.e., can I build it without spending money, and without needing to scour the web for a crack (which I'm not interested in doing...)? I might want to try to write multi-stream ethernet blasting...
16:24
jhlink_
So sad. I guess I can't build this on OSX
16:33
jhlink_
vup: or anuejn: Is the docker-make.sh supposed to be run strictly in Arch or Ubuntu? I'd like to make a PR updating the makefiles README. Might as well leave some breadcrumbs while I'm at it. :)
16:44
felix_
the free vivado license is sufficient for the zynq used in the axiom beta
17:18
Spirit532
joined the channel
17:22
Bertl
namibj: so you need to register and request a license, but other than that you should be fine
17:59
jhlink_
Is there a problem with the CMakeFiles for axiom-control-daemon?
18:00
jhlink_
Running an ubuntu VM, and still running into build failures.
18:00
jhlink_
Man... building a project is soooo hard...
18:03
jhlink_
That was a poorly made question. Please ignore that.
18:08
Bertl
what?
18:14
jhlink_
Well, I wanted to ask if there was any more information about the build process, but I think I don't know enough to ask the right question.
18:14
jhlink_
So, right now. I'm fumbling around to see how I can build all the images.
18:14
Bertl
currently we still build the various parts separately
18:14
jhlink_
Really???
18:15
jhlink_
Oh man... That would explain soooo much!
18:15
Bertl
parts are built on the camera, parts are built on an intel PC
18:15
Bertl
but, that said, the 'new' images are automatically built
18:16
Bertl
so the process works but it might not work everywhere
18:16
Bertl
as I said, vup/anuejn know a lot about the build process, so they are probably able to help you and maybe even fix the issues on the way
18:20
jhlink_
Yeah, you're right. It's probably best if I wait for them to make any headway with this.
18:20
jhlink_
Thanks Bertl!!
18:20
Bertl
no problem
19:02
Bertl
off for now ... bbl
19:02
Bertl
changed nick to: Bertl_oO
19:47
vup
jhlink_: i am currently traveling and only have a phone with me, i will get back to you in some days, when i have access to my laptop again
19:50
jhlink_
Thank you!! vup
22:56
namibj
Bertl_oO: sou ds reasonably harmless then. I'll probably try soon.