*** zoli__ has joined #baserock | 04:16 | |
*** zoli__ has joined #baserock | 04:19 | |
*** zoli__ has quit IRC | 04:20 | |
*** Zara has quit IRC | 04:22 | |
*** Zara has joined #baserock | 04:22 | |
*** zoli__ has joined #baserock | 04:23 | |
*** zoli__ has quit IRC | 06:35 | |
*** mike has joined #baserock | 07:32 | |
*** mike is now known as Guest56363 | 07:32 | |
*** gfinney has joined #baserock | 08:01 | |
*** a1exhughe5 has joined #baserock | 08:10 | |
*** gfinney has quit IRC | 08:30 | |
*** gfinney has joined #baserock | 08:30 | |
*** rdale has quit IRC | 08:51 | |
*** mdizzle has joined #baserock | 08:53 | |
*** bashrc_ has joined #baserock | 09:01 | |
*** ssam2 has joined #baserock | 09:05 | |
*** ChanServ sets mode: +v ssam2 | 09:05 | |
*** rdale has joined #baserock | 09:05 | |
*** tiagogomes_ has joined #baserock | 09:18 | |
*** gary_perkins has joined #baserock | 09:44 | |
*** jonathanmaw has joined #baserock | 09:46 | |
ssam2 | i thought it might be an easy job to add an 'include' parameter to lorry-controller, to avoid it importing the whole of baserock/* into Gerrit (since some of those repos are obsolete) | 09:47 |
---|---|---|
ssam2 | but then I looked at the code and realised it uses an SQLite database for storage and doesn't have any concept of schema versioning or database migrations | 09:48 |
ssam2 | i think it should probably be illegal to use SQL without having some kind of mechanism for schema migrations | 09:48 |
*** edcragg has joined #baserock | 09:51 | |
ssam2 | i guess I could just let it import all the repos, then hide the obsolete ones manually. | 09:53 |
*** CTtpollard has joined #baserock | 10:05 | |
*** petefoth has quit IRC | 10:15 | |
*** petefoth has joined #baserock | 10:19 | |
* ssam2 discovers that a bunch of settings that we tell people to set in lorry-controller.conf actually have no effect | 10:29 | |
pedroalvarez | oh! like? | 10:30 |
ssam2 | stagger, for example | 10:30 |
ssam2 | 'tarball' | 10:30 |
Kinnison | ;( | 10:31 |
ssam2 | also seems like create, destroy, serial, and uuid are all ignored | 10:32 |
bashrc_ | I have a firehose question: why are debian-style version numbers referenced? Does that have something to do with "unpetrify-ref" ? | 10:49 |
Kinnison | Back when I specified firehose, we needed a way to generate a strict ordering on ref names (particularly tags) | 10:49 |
Kinnison | the decision I came to was that we should use a stable version ordering system (and I selected debian-style) and then transformation regexps to convert tag names into something which sorted well | 10:49 |
* Kinnison selected debian-style ordering because it's well understood, well documented, widely implemented, and I happen to be a DD :) | 10:50 | |
bashrc_ | I notice that within strata refs are usually sha1's, so is the version number coming from unpetrify-ref? | 10:52 |
Kinnison | firehose isn't retrieving version numbers from the definitions | 10:52 |
Kinnison | the version numbering stuff in firehose is purely related to ordering of *upstream* ref names such as tags | 10:52 |
Kinnison | It then determines what there is to do, based on the SHA1s in the history of the selected ref | 10:52 |
bashrc_ | ok I see | 10:53 |
* ssam2 realises he didn't need the lorry-controller 'include' feature anyway | 11:04 | |
wdutch | when morph can't autodetect a buildsystem the MorphologyNotFoundError is very confusing when first encountered, could I introduce a new error or reword MorphologyNotFoundError to take this into account? | 11:17 |
* Kinnison would rather you removed the buildsystem autodetection | 11:17 | |
Kinnison | but to do that requires that we first make it possible to specify buildsystem in the stratum (for when there's no chunk morphology) or make chunk morphologies mandatory | 11:17 |
wdutch | this would require patching a lot of existing strata | 11:18 |
Kinnison | Aye | 11:18 |
SotK | wdutch: what is the error message that's confusing ooi? | 11:19 |
* Kinnison wants build systems moved out into definitions (instead of in morph's codebase) and so on, but that I think is already being considered by the version-1 team | 11:19 | |
radiofree | i wouldn't like to make chunk morphologies mandatory, for a lot of stuff the autodetection works great | 11:19 |
*** tiagogomes_ has quit IRC | 11:19 | |
wdutch | SotK: I have a strata containing a chunk called luci, there is no chunk morphology for luci specified but when I try and build the strata I get: ERROR: Couldn't find morphology: luci.morph | 11:20 |
ssam2 | there's a version-1 team ?? | 11:20 |
Kinnison | ssam2: well there's people discussing it on the ML | 11:20 |
*** tiagogomes_ has joined #baserock | 11:23 | |
SotK | wdutch: I'd reword it to mention that it couldn't find the morphology it wanted, and also it couldn't detect the build system and see what people say then | 11:23 |
ssam2 | SotK: that seems like a good solution to me | 11:23 |
mauricemoss_ | I was running into this Morph error as well and found it quite confusing at the beginning. The autodetection works quite well for me. | 11:23 |
mauricemoss_ | SotK, +1 | 11:24 |
petefoth | Dumb question alert: I want to work with my Baserock VM while I'm offline. Usually I ssh in using the ip address of the bridged network adaptor (eth0). But when my host is offline, that adapter doesn't have an ip address. | 11:26 |
ssam2 | petefoth: you added a 'Download' link to the sidebar on the wiki, but 'Get baserock' already links to that page | 11:26 |
petefoth | I also have a 'host-only' adapter (eth1). Do I have to work directly in thew VM console or is there some way I can still ssh in using eth1? (Output from `ipaddr` is at http://paste.baserock.org/apemoperur) | 11:26 |
ssam2 | petefoth: 'Download' is definitely a better name, but we don't need both :) | 11:26 |
petefoth | ssam2: oops= failed to ßpot that | 11:27 |
Kinnison | petefoth: providing you can persuade eth1 to DHCP (and you have a DHCP server on your host-only network) then it should be possible to ssh in on that interface | 11:27 |
*** wschaller has joined #baserock | 11:28 | |
Kinnison | petefoth: If you're using virtualbox then it puts such a server on host-only adapters by default IIRC | 11:28 |
petefoth | Kinnison: ta! Any idea what the ip address I need to ssh to would be | 11:29 |
Kinnison | petefoth: it'd depend entirely on what was given to it at DHCP time :( | 11:30 |
petefoth | Kinnison: How can I find that out | 11:30 |
Kinnison | ip addr show dev eth1 | 11:31 |
Kinnison | or simliar | 11:31 |
petefoth | Hmm - eth1 stil dpesn't have an ip address :( | 11:34 |
bashrc_ | I may have asked this before but didn't get to the bottom of it. Within the firehose examples tracking section how is the location of the upstream repo defined? I can see the landing repo, but no upstream one | 11:40 |
persia | bashrc_: In definitions. | 11:40 |
persia | As I understand it, the goal is to read definitions, go find a new foo, ad submit it as a potential change. | 11:41 |
persia | s/ad/and/ | 11:41 |
persia | So any information in the format which can be derived from definitions is redundant and confusing. | 11:41 |
straycat | code would be much simpler if we had a build-system attribute for each chunk and that had to be in definitions | 11:43 |
*** zoli__ has joined #baserock | 11:43 | |
straycat | wdutch, that error was actually reworded from a more detailed err msg, because it's confusing when you mistype a path and morph tells you it can't autodetect a build system | 11:45 |
persia | We should definitely have that for v1 | 11:45 |
straycat | i think we should have different exceptions if we can | 11:45 |
straycat | i definitely don't want morph to go back to telling me it can't autodetect a build system just because i made a typo | 11:46 |
Kinnison | Pete had an old baserock which had been upgraded repeatedly. As such he needed a stanza in /etc/network/interfaces for his eth1 | 11:46 |
wdutch | straycat: I agree, a distinct error for each case seems sensible | 11:47 |
straycat | wdutch, i have a feeling that might be trickier than it sounds, since it might currently be difficult to tell one case from another | 11:49 |
straycat | hopefully i'm wrong about that :) | 11:50 |
*** petefoth has quit IRC | 11:51 | |
*** petefoth has joined #baserock | 11:52 | |
petefoth | Kinnison: thanks - I'm in :) | 11:55 |
radiofree | ssam2: rsync is gpl3 | 12:05 |
radiofree | looks like the strip-gpl3 script won't remove it? | 12:06 |
kejiahu | hi, we are trying to cross build a baserock system for armv8b64 on HP Moonshot. I created a wiki page to record what we have done so far, and some sections are still WIP. anybody interested and suggestion/feedbacks are welcome. http://wiki.baserock.org/x86_64_to_armv8b64/ | 12:09 |
persia | I don't really understand how this is different from any other cross-bootstrap. | 12:10 |
kejiahu | persia, it is under example of cross-build section. so maybe duplicate in some of the sections. Is the example worth to be recorded on baserock wiki? or should I move it to private logs? | 12:14 |
ssam2 | radiofree: ah, thanks for pointing that out | 12:15 |
ssam2 | i'll update the strip-gpl3 script | 12:15 |
persia | kejiahu: I tend to think of the wiki as a source of docs, for searching for how to do things, so I'd recommend improving the existing guides if they are confusing/misleading, and publishing reference definitions for anything particularly interesting. | 12:17 |
ssam2 | might be interesting to have a 'success stories' section on the wiki :) | 12:17 |
ssam2 | if they are identified as 'stories' rather than 'documentation' it places less load on the people who take time to ensure the documentation on the wiki is kept up to date in line with changes to morph.git and definitions.git | 12:19 |
kejiahu | sounds a good idea | 12:23 |
persia | That sounds like an interesting idea. It also provides a way to show off some of the ways people are actually using baserock, rather than just the capabilities. | 12:23 |
SotK | +1 for success stories | 12:24 |
radiofree | i want to add new instructions for flashing a jetson | 12:41 |
radiofree | they've pretty much entirely changed, should i create a new page of just replace everything in the current one? | 12:42 |
ssam2 | aren't the old ones broken ? | 12:44 |
ssam2 | or at least, worse than the new ones? | 12:44 |
petefoth | radiofree: I'd say replace. | 12:44 |
radiofree | it's not broken, this is just an entirely new method that we should encourage people to do | 12:44 |
radiofree | i.e /boot is now on an ext4 partition | 12:45 |
ssam2 | i think replace | 12:45 |
ssam2 | wiki has history anyway | 12:45 |
radiofree | the instructs rely on people cloning a script from my gitlab repo, is that ok? | 12:45 |
ssam2 | as long as you don't suggest they do `curl xxx | bash` | 12:45 |
persia | Is the script something that could be a chunk so that it could be put in a devel system? | 12:46 |
radiofree | yeah, the instructions would actually be a hell of a lot easier if it was in a baserock system + we added the nvidia tools to a devel system | 12:46 |
persia | Can that just be done then? | 12:47 |
radiofree | well i'll put these up now, submit patches for baserock, then modify them once thats done? | 12:47 |
radiofree | there's nothing to stop you following these instructions on a baserock system | 12:47 |
persia | That sounds reasonable: it lets people critique the new approach early. | 12:47 |
radiofree | these also have the added advantage of allowing to to flash a jetson from a jetson | 12:48 |
persia | This is a good thing. Everything should be self-hosting. | 12:54 |
radiofree | mason is red | 12:56 |
petefoth | radiofree: at least it's stopped being yellow :) | 12:57 |
rjek | violets are blue? | 12:57 |
ssam2 | wow, I love that rsync built in my chroot but failed to build on Mason | 12:58 |
radiofree | + morph: strata/tools/rsync.morph, it should be strata/foundation/rsync.morph ? | 12:58 |
ssam2 | oh, hmm | 12:59 |
ssam2 | maybe it built for me because I had that locally | 12:59 |
radiofree | probably, the patch you sent moved it from tools to foundation | 12:59 |
ssam2 | thanks for spotting it, I've pushed a fix | 13:00 |
radiofree | hmm.. should releases be announced on the front page of http://wiki.baserock.org/ ? | 13:10 |
petefoth | I think that w.b.o shoudl have 'news' pages, and a summary of the most recent should appear on the front page | 13:15 |
petefoth | but I think we've beenround this loop before :) | 13:15 |
Kinnison | If we have news as a set of pages then we could do an inline to make that happen | 13:15 |
Kinnison | I could set that up if you want | 13:15 |
Kinnison | Or anyone else with good ikiwiki skills could | 13:15 |
petefoth | *I* think it would be a really good idea, but I think there should be some form of consensus beofre we do it | 13:15 |
SotK | petefoth: Mason was green before the bout of yellows which ended on Monday.. Would it perhaps make sense to indicate the most recent result that wasn't a failure to check for new changes rather than it looking broken? | 13:15 |
SotK | I also think news would be great | 13:15 |
petefoth | Or there's always the 'better to seek forgiveness' route :) | 13:15 |
ssam2 | SotK: once we upgrade to the Zuul-mason the whole status page will disappear | 13:16 |
ssam2 | I'd like it if we could to add support for continous building of 'master' and generating that status page to the new Mason | 13:17 |
ssam2 | also, seems my fix for rsync didn't actually work! | 13:17 |
SotK | ssam2: that should be trivial, Zuul has support for a timer trigger as well as a Gerrit trigger | 13:18 |
SotK | hopefully this upgrade can be soon and people can stop worrying every time there is old NONETs from checking for changes at the top of the results list | 13:19 |
Kinnison | petefoth: if you can come up with one or two news items you'd like present, then I'd be happy to help you set up the inlines etc. | 13:19 |
petefoth | Kinnison: the only recent news I know of is the release of 15.10 | 13:22 |
Kinnison | Okay, I'll set things up | 13:22 |
ssam2 | ok, rsync built from the same commit on my machine | 13:22 |
ssam2 | using build-morphology, so no local changes at work | 13:22 |
Kinnison | Unless at least one person here -1s the idea within the next 5 minutes | 13:22 |
ssam2 | oh! cache.baserock.org is probably full | 13:22 |
ssam2 | no.. | 13:23 |
radiofree | hmmm | 13:23 |
radiofree | can someone test extracting http://download.baserock.org/baserock/baserock-current-build-system-armv7lhf-jetson.img.gz ? | 13:24 |
radiofree | i've tried twice now, file-roller tells me "An error occurred while extracting files" | 13:24 |
radiofree | sha256sum of the download matches | 13:24 |
petefoth | radiofree: I'll give it a try but it'll be in Mac OS | 13:24 |
ssam2 | cache.baserock.org does seem to be giving Mason a 500 error, it's not a problem with rsync | 13:25 |
radiofree | petefoth: thanks | 13:25 |
radiofree | -rw-r-----. 1 james james 1.9G Mar 11 13:23 build-system-armv7lhf-jetson.img | 13:25 |
radiofree | according to file-roller it should be 2.1G | 13:25 |
straycat | radiofree, extracts fine here and is 2G | 13:28 |
radiofree | hmm | 13:29 |
petefoth | radiofree: worked for me - -rw-r-----@ 1 pete staff 2147483648 11 Mar 13:28 baserock-current-build-system-armv7lhf-jetson.img | 13:29 |
Kinnison | petefoth: Okay, so where on the front page do you want the news inline? | 13:29 |
* petefoth thinks | 13:30 | |
radiofree | ok thanks, must be me then | 13:30 |
radiofree | using gzip worked... | 13:32 |
petefoth | I think immediately after the 2nd paragraph (beginning 'Our objectives...'). Everything under that is (relaivley old) news IMHO | 13:32 |
Kinnison | petefoth: I concur | 13:32 |
petefoth | Kinnison: I'm sure others will have different opinions however | 13:33 |
Kinnison | petefoth: I'll insert the inline there, and we can see how it looks | 13:33 |
Kinnison | :) | 13:33 |
*** wschaller_ has joined #baserock | 13:34 | |
* ssam2 tweaks firewall rules and hopes Masons turn green now | 13:34 | |
*** wschaller___ has joined #baserock | 13:35 | |
radiofree | i'm an idiot, i was trying to extract to /tmp - tmpfs 1.9G 12M 1.9G 1% /tmp | 13:36 |
*** wschaller_ has quit IRC | 13:39 | |
Kinnison | petefoth: how does that look to you? | 13:42 |
petefoth | Kinnison: looks good to me. I'd also be tempted to add a link in the Sidebard to a 'News' page with *all* the news | 13:42 |
Kinnison | petefoth: please hold... | 13:42 |
*** wschaller has quit IRC | 13:42 | |
Kinnison | petefoth: where in the sidebar? | 13:42 |
petefoth | Kinnison: hmmmm | 13:42 |
petefoth | Kinnison: In the 'community' section? | 13:42 |
Kinnison | okay | 13:42 |
Kinnison | top, bottom, middle? | 13:42 |
Kinnison | (the inline on the front page is limited to a max of 5 most recent news items) | 13:42 |
Kinnison | btw | 13:42 |
petefoth | Kinnison: you decide! :) | 13:42 |
Kinnison | Argh, the agony of choice | 13:42 |
Kinnison | done | 13:42 |
petefoth | Kinnison: ta! | 13:42 |
Kinnison | petefoth: and the "news" page also has a postform for creating new news items on the web | 13:42 |
* petefoth sits back and waits for any reaction | 13:42 | |
*** zoli__ has quit IRC | 13:45 | |
*** paulw has quit IRC | 13:48 | |
radiofree | looks good | 13:50 |
kejiahu | hi I got an error when doing native build for armv8b64 within the bootstrap rootfs on moonshot node, can anybody help me to figure out what could be happening? http://paste.baserock.org/rohiniluko | 13:52 |
bashrc_ | the last I saw in emails was that BE on moonshot mostly works but that there are a couple of remaining issues | 13:54 |
*** bjdooks has joined #baserock | 13:56 | |
petefoth | what lives in the /cache/ccache directories - they seem to be empty in my VM? | 13:56 |
bashrc_ | PCI bridge. I think it's being patched | 13:56 |
* bjdooks perks up at pci bridge | 13:57 | |
Kinnison | petefoth: it's a native-bootstrap phase | 13:57 |
bjdooks | question, are we differentiating between armv7hf, and armv7hf with vfp4-d16? | 13:58 |
* petefoth translates that as 'nothing you need to worry about' :) | 13:58 | |
radiofree | i don't think so | 13:58 |
Kinnison | bjdooks: armv7lhf is VFPv3-d16 for us IIRC | 13:59 |
radiofree | bjdooks: armv7hf = --with-fpu=vfpv3-d16 | 13:59 |
bjdooks | Kinnison: ok, so it shouldn't be an issue for use on Cortex-A5 based devices | 13:59 |
Kinnison | That's why we picked it | 13:59 |
Kinnison | (general likelihood of being usable) | 13:59 |
*** paulw has joined #baserock | 14:01 | |
bjdooks | thanks | 14:03 |
radiofree | ok, fresh baserock install (downloaded from website), morph init, morph checkout... | 14:06 |
radiofree | morph build systems/devel-system...... - error ERROR: Stratum build-essential has no build dependencies for chunk stage1-binutils in string | 14:06 |
petefoth | 'morph edit --no-git-update bash' tries to talk to g.b.o http://paste.baserock.org/otesuwejug (which is odd) and fails (which is not because I'm 'offline') | 14:06 |
radiofree | NoBuildDependenciesError: Stratum build-essential has no build dependencies for chunk stage1-binutils in string | 14:07 |
radiofree | i suppose i need to use latest morph? | 14:08 |
SotK | I think so | 14:08 |
petefoth | Di I have to do the morph edit while I'm online, and only go offline after that? | 14:08 |
petefoth | s/Di/Do/ | 14:08 |
Kinnison | petefoth: unless you already have bash cached, I'd presume so | 14:08 |
petefoth | Kinnison: i beleive I do have bash cached, in cache/gits/git___git_baserock_org_delta_bash | 14:10 |
petefoth | but that doesn't have any source in it :( | 14:10 |
radiofree | instructions for using latest morph are broken, i'll fix it | 14:10 |
SotK | petefoth: looks like morph edit doesn't honour --no-git-update | 14:11 |
SotK | it always runs `git remote update --prune` | 14:11 |
petefoth | SotK: looks like it. IS that a bug or a feature? If it's a bug, I'll raise a story in StoryBoard | 14:12 |
SotK | I'd imagine its a bug | 14:12 |
petefoth | SotK: ta! | 14:12 |
SotK | certainly it will never work if you're offline | 14:12 |
radiofree | AppException: In staging area /src/tmp/failed/tmphjN2ag: Command failed: sh -c 'export STAGE2_SYSROOT="$(dirname $(pwd))" | 14:13 |
radiofree | :\ | 14:13 |
jjardon | radiofree: you beat me editing the wiki by 10 seconds! | 14:13 |
petefoth | SotK: which is a bit of a hole in the 'Use Baserock when offline' story :) | 14:13 |
radiofree | that's stage2-busybox | 14:14 |
SotK | petefoth: it sure is | 14:14 |
SotK | should be fairly simple to fix | 14:14 |
* SotK will write a patch tonight if he has time | 14:14 | |
* petefoth is almost tempted to try and fix it himself | 14:15 | |
straycat | Was there not a suggestion to split edit in something like fetch, and set-ref commands? | 14:15 |
straycat | *into | 14:15 |
SotK | I think so | 14:15 |
radiofree | log - http://paste.fedoraproject.org/196654/83324142/ | 14:16 |
radiofree | thats a downloaded build-system trying to build a devel-system from master (jetson) | 14:16 |
straycat | It does seem a bit nicer, and clearly you wouldn't attempt to do a morph fetch foochunk if you offline, but you might want to morph set-ref foochunk master... or something | 14:17 |
straycat | *you were | 14:17 |
straycat | s/attempt/expect to be able/ | 14:17 |
* radiofree nukes his cache | 14:19 | |
*** CTtpollard has quit IRC | 14:27 | |
*** CTtpollard has joined #baserock | 14:36 | |
petefoth | Would http://paste.baserock.org/afeciyeyan be an acceptable patch to fix the 'morph edit doesn't honour --no-git-update' issue? | 14:48 |
ssam2 | the logic seems to be inverted | 14:51 |
ssam2 | other than that, I think it'd be OK, although I don't know all the code paths that use that function | 14:51 |
petefoth | ssam2: you spotted the deliberate mistake :) | 14:52 |
* petefoth tries to workout why the patch seemed to work | 14:52 | |
SotK | petefoth: I'd be tempted to put the logic in the edit plugin, since the git fat stuff will break too (if there is a .gitfat file in the repo) | 14:53 |
petefoth | SotK: ta! I'll look there | 14:54 |
SotK | alternatively, duplicate the logic in GitDirectory.fat_pull | 14:55 |
petefoth | but update_remotes is called from a number of places as well as the edit plugin I think | 14:55 |
bashrc_ | so how do you reference an upstream tarball? tarballs don't contain commits | 15:02 |
rdale | you need to get the tarball lorried so that it becomes a git repo, that you can reference as 'upstream:dialog-tarball' in a stratum | 15:03 |
bashrc_ | sounds complicated | 15:04 |
franred | bashrc_, there are a lot of examples in the lorry repository | 15:07 |
franred | bashrc_, http://git.baserock.org/cgi-bin/cgit.cgi/baserock/local-config/lorries.git/tree/open-source-lorries/autoconf-tarball.lorry | 15:07 |
franred | for example | 15:07 |
straycat | petefoth, did we document conf extensions anywhere? like ATTACH_DISKS, FSTAB_* etc ? | 15:14 |
jmacs | ATTACH_DISKS is documented in the extension code, I think | 15:15 |
straycat | just thought it might have been something for the wiki, but probably i'm being stupid | 15:16 |
straycat | *shrug* | 15:16 |
jmacs | Don't have a baserock image to check on | 15:17 |
straycat | ATTACH_DISKS isn't even a conf ext anyway | 15:18 |
jmacs | Hmm, it's not actually well documented in writeexts either | 15:21 |
straycat | heh yeah, i was wondering how to attach multiple disks, i mean it's obvious from the code but still | 15:23 |
petefoth | straycat: all extension documnetation is in the source code. I mostly worked on write extensions. If you're working with the extension, you can improve the documentationas you go :) | 15:24 |
straycat | oh okay | 15:24 |
kejiahu | tiagogomes_: have you got this error when you native build armv8l64 under ubuntu before? http://paste.baserock.org/kuwemopize | 15:29 |
tiagogomes_ | kejiahu, you need to mount the Linux API filesystems before entering the chroot | 15:30 |
kejiahu | tiagogomes_: this? http://paste.baserock.org/ololuxufoj | 15:31 |
tiagogomes_ | I used to do more stuff | 15:32 |
tiagogomes_ | PATH=/bin:/usr/bin:/sbin:/usr/sbin | 15:33 |
tiagogomes_ | LD_LIBRARY_PATH=/lib:/lib64 | 15:33 |
tiagogomes_ | ldconfig | 15:33 |
radiofree | ok, build-system downloaded from website, using morph master to build definitions master, on a jetson, is failing | 15:34 |
radiofree | clean cache as well | 15:35 |
radiofree | configure: error: cannot compute suffix of object files: cannot compile | 15:35 |
radiofree | stage2-glibc | 15:35 |
* radiofree tries building 15.10 | 15:36 | |
paulsherwood | interesting. i had that with ybd... | 15:36 |
rdale | i think it just means that the compiler is broken | 15:37 |
radiofree | that sounds like a problem... | 15:37 |
radiofree | this was with a clean cache, built from step 1 | 15:37 |
* petefoth doesn't unsersatnd the line 'PYTHONPATH="$morphpath/morph" "$morphpath/morph" "$@" in the morph script in http://wiki.baserock.org/using-latest-morph/ Why is "$morphpath/morph" there twice? | 15:37 | |
radiofree | petefoth: because the second one is saying "run $morphpath/morph" the script | 15:38 |
SotK | should that not be 'PYTHONPATH="$morphpath" "$morphpath/morph" "$@"'? | 15:38 |
jjardon | I think so | 15:39 |
radiofree | yep | 15:39 |
rdale | that page dosn't mention pylru in the latest morph, i'm sure i've seen a very similar page which did | 15:39 |
radiofree | changed | 15:40 |
petefoth | previous version (wht pylru) was PYTHONPATH="$morphpath:$pylrupath" "$morphpath/morph" "$@" | 15:40 |
petefoth | rdale: not needed with the latest morph which has pylru added | 15:40 |
* radiofree hopes changing it on his system makes glibc build | 15:40 | |
jjardon | rdale: new release doesnt need pylru, as its already builded in the release | 15:40 |
rdale | i just installed pylru - i don't see the advantage of keeping a local copy | 15:40 |
rdale | ah ok | 15:40 |
straycat | petefoth, don't see the point in commenting it, because if you can see the code then it's obvious, and it's not like that part can be accessed by morph help <ext> | 15:40 |
radiofree | still no luck :\ | 15:41 |
radiofree | anyone know what the problem might be? | 15:41 |
petefoth | straycat: fair enough. If the code comments are good enough that's grand | 15:41 |
rdale | radiofree: there was a sym link for the dynamic loader that was changed recently - maybe that change doesn't work on arm | 15:42 |
radiofree | i don't think it's that? | 15:42 |
radiofree | i'm building everything from stage 1, my host is glibc/gcc 4.9 | 15:42 |
* petefoth now understands why his change to that script broke it :( | 15:43 | |
radiofree | hmmm http://git.baserock.org/cgi-bin/cgit.cgi/baserock/baserock/definitions.git/tree/strata/build-essential.morph#n73 | 15:43 |
radiofree | stage2-linux-api-headers probably shouldn't be in there? | 15:43 |
rdale | ok, so the sym link won't be there at stage1 glibc | 15:43 |
radiofree | oh right, maybe it should | 15:43 |
radiofree | so i'm pretty stumped, looks like stage1-gcc is broken | 15:44 |
radiofree | rdale: you might be right | 15:46 |
paulsherwood | radiofree: did you do the 'using latest morph' thing? | 15:48 |
radiofree | paulsherwood: yep | 15:48 |
paulsherwood | also are you sure what you have checked out is the branch you think it is? | 15:48 |
paulsherwood | sorry to ask dumb qursitons, but these things have bitten me | 15:48 |
radiofree | i'm on master | 15:49 |
radiofree | and master of morph | 15:49 |
radiofree | he's the config.log http://paste.fedoraproject.org/196720/26089087 | 15:51 |
* pedroalvarez can't open that link | 15:51 | |
radiofree | pedroalvarez: should work now | 15:52 |
radiofree | armv7lhf-bootstrap-linux-gnueabi-gcc seems to be segfaulting | 15:52 |
pedroalvarez | I'm still getting 503 trying to open that url | 15:53 |
radiofree | http://paste.baserock.org/fequcegiga | 15:53 |
pedroalvarez | radiofree: I found an oddity in stage1-gcc some weeks ago, it may be related | 15:54 |
radiofree | what was that and what was the fix? | 15:56 |
pedroalvarez | radiofree: http://paste.baserock.org/tozequyeme.diff | 15:57 |
pedroalvarez | but it was only my workaround | 15:57 |
pedroalvarez | and I don't think that a patch like this should be merged | 16:01 |
*** wschaller_ has joined #baserock | 16:03 | |
*** wschaller has joined #baserock | 16:04 | |
radiofree | doesn't work for me anyway | 16:04 |
radiofree | ERROR: In staging area /src/tmp/failed/tmpW2Cndw: Command failed: sh -c '# GCC is not passing the correct host/target flags to GMP'"'"'s configure | 16:05 |
pedroalvarez | meh, my usecase was bootstraping from x86 to arm | 16:05 |
pedroalvarez | cross-bootsraping* | 16:05 |
pedroalvarez | but maybe changing host=armv7a for host=armv7lhf? | 16:06 |
pedroalvarez | I don't know, but I assume the error is when building stage1-gcc | 16:06 |
radiofree | i thought armv7lhf was a baserock creation | 16:07 |
*** jonathanmaw has quit IRC | 16:07 | |
*** wschaller___ has quit IRC | 16:07 | |
radiofree | has anyone tried latest jetson build image to build a devel image? | 16:07 |
*** wschaller_ has quit IRC | 16:07 | |
radiofree | it might just be something wrong with my setup? | 16:08 |
radiofree | i have built master very recently, however that was on an older devel image that didn't have the /lib/ld-linux.so symlink on it... | 16:10 |
pedroalvarez | does removing the link change anything? | 16:13 |
*** jjardon has quit IRC | 16:14 | |
radiofree | that's what i'm trying now | 16:14 |
pedroalvarez | whenever I had ld.so problems, the binary wasn't executable at all, and not seg faulting :/ | 16:16 |
*** jjardon has joined #baserock | 16:18 | |
*** Guest56363 has quit IRC | 16:28 | |
radiofree | this results in an entirely new error | 16:30 |
straycat | jjardon, wow I didn't realise we could just drop all that busybox delta | 16:31 |
radiofree | what's the "log to stdout" option again? | 16:33 |
radiofree | '--build-log-on-stdout' | 16:33 |
straycat | yeah | 16:34 |
jjardon | straycat: our delta were only a small patch to fix some includes (and the morph files but they are are now in definitions) | 16:34 |
straycat | oh i thought there was more | 16:34 |
straycat | cool | 16:35 |
jjardon | yep | 16:39 |
radiofree | so if i download a baserock image from the website, it should be able to build the same version out of the box right? | 16:39 |
radiofree | so i checkout 15.10, the version of morph on their will be able to build 15.10? | 16:39 |
* jjardon happy when our delta is 0 and we only have changes in our morph files. This remembers him we should have a solution for .gitmodules | 16:40 | |
pedroalvarez | radiofree: yes... | 16:40 |
jjardon | radiofree: I think so, yes | 16:40 |
radiofree | ok, i'll get another jetson and try everything from scratch | 16:40 |
* pedroalvarez waits the "that doesn't work" | 16:40 | |
* radiofree is an optimist and knows it absolutely will work with a clean install | 16:41 | |
pedroalvarez | I need release testers.. | 16:42 |
radiofree | does anyone have a jetson build system around from a previous verison? | 16:42 |
radiofree | i.e the release before http://git.baserock.org/cgi-bin/cgit.cgi/baserock/baserock/definitions.git/commit/?id=a51a8ee9fe2c691a4b2d73fe06c1fde1d18f1153 | 16:42 |
rdale | that was the change i was thinking of earlier | 16:44 |
paulsherwood | radiofree: mine is somewhere, i believe, and may pre-date that | 16:44 |
paulsherwood | mwilliams_ct: ^^ ? | 16:44 |
mwilliams_ct | radiofree: Please please please come and take the one off my desk | 16:45 |
mwilliams_ct | it's been sitting looking sad for ages | 16:45 |
mwilliams_ct | paulsherwood: I also have yours, boxed up and ready for your return | 16:45 |
mwilliams_ct | s/your return/return to you | 16:46 |
perryl | hi all; i submitted a patch fixing my morph protocol version error message which has +2, could someone with push access merge it for me? :) | 16:51 |
pedroalvarez | yup! | 16:55 |
*** a1exhughe5 has quit IRC | 16:55 | |
straycat | jjardon, is cool cause it happens to solve a problem i had with buggy grep -x | 16:58 |
straycat | so thanks | 16:58 |
radiofree | sooo | 16:59 |
radiofree | http://git.baserock.org/cgi-bin/cgit.cgi/baserock/baserock/definitions.git/commit/?id=a51a8ee9fe2c691a4b2d73fe06c1fde1d18f1153 | 16:59 |
jjardon | straycat: np :) . Id like to have the option to use coreutils instead busybox command, but we need to finish the "usrmove" first | 16:59 |
radiofree | this breaks the build | 16:59 |
radiofree | if i rm /lib/ld-linux.so.3 and rebuild from binutils again it appears to work | 17:00 |
jjardon | ssam2: ^^ | 17:00 |
radiofree | at least i know how a functional stage1-gcc | 17:00 |
radiofree | s/know/now | 17:00 |
radiofree | s/how/have | 17:00 |
radiofree | :\ | 17:00 |
radiofree | so i guess the current jetson arm build-system on the website can't actually build anything? | 17:01 |
ssam2 | that breaks the build ??? wow, ok | 17:03 |
ssam2 | any idea how? | 17:03 |
ssam2 | yeah, I guess the last release will be broken on ARMv7 hf then | 17:03 |
radiofree | it creates a stage1-gcc that segfaults when you try and run it | 17:04 |
* ssam2 slowclaps | 17:04 | |
*** CTtpollard has quit IRC | 17:04 | |
ssam2 | if we remove it, then we're back with the problem that stage1 chunks built on old ARM systems will not run on new ARM systems, but will have the same cache key | 17:04 |
radiofree | but i'd appreciate it if someone else tried flashing the current image, then building from a clean cache | 17:05 |
ssam2 | but I guess that's better than it not working at all | 17:05 |
ssam2 | radiofree: can't do today, but i'll try tomorrow or friday | 17:05 |
* ssam2 is currently trying to understand how gerrit plugins could possibly ever work, given that the ones up for download on the gerrit website trigger an error when I try to install them | 17:06 | |
ssam2 | oh, seems that the downloads are broken if you use 'wget' instead of a browser to download them | 17:09 |
* ssam2 claps slowly again | 17:09 | |
radiofree | from baserock? | 17:10 |
radiofree | i'd prefer the downloaded files had the release number in them rather than "current" as well | 17:11 |
ssam2 | no, from https://gerritcodereview-plugins.storage.googleapis.com/index.html | 17:11 |
radiofree | when i downloaded the latest one it wanted to overwrite my existing "current" and i had no idea what version my existing "current" was | 17:11 |
ssam2 | radiofree: you can download the files with the number in if you want | 17:11 |
ssam2 | we link to the 'current' ones to avoid needing to update the wiki, I think | 17:12 |
* pedroalvarez was trying to merge perryl's patch for morph in definitions.git | 17:12 | |
perryl | pedroalvarez: oddly, i kept trying to push it to my fork of definitions.git | 17:12 |
*** CTtpollard has joined #baserock | 17:14 | |
perryl | thanks pedroalvarez! | 17:22 |
pedroalvarez | perryl: no worries! thanks for fixing that :0 | 17:22 |
pedroalvarez | :) | 17:22 |
mwilliams_ct | paulsherwood: radiofree has run off with your jetson. I did all I could to defend it (if by "all I could" you mean I stepped back and enjoyed the extra desk space) | 17:25 |
paulsherwood | lol | 17:26 |
*** CTtpollard has quit IRC | 17:26 | |
* straycat wonders why morph's building gcc | 17:28 | |
radiofree | paulsherwood: you don't mind if i completely wipe yours? | 17:28 |
radiofree | i'm going to setup one running the latest release, and one running the previous release, both trying to build definitions master | 17:29 |
radiofree | the previous release should work, current should fail | 17:29 |
straycat | ignore me, build-log-on-stdout was blinding me | 17:29 |
straycat | or more likely the ci had build and transferred gcc by the time i reran build | 17:29 |
straycat | *built | 17:30 |
*** gfinney has quit IRC | 17:30 | |
* radiofree just notices there's a brand new, completely unboxed jetson already on his desk.... | 17:30 | |
mwilliams_ct | no backs | 17:30 |
paulsherwood | radiofree: you lucky person, you | 17:30 |
radiofree | paulsherwood: i'll reflash yours with a working version of master tomorrow | 17:31 |
radiofree | it needs to build first | 17:31 |
paulsherwood | radiofree: ok | 17:32 |
ssam2 | apologies if I did indeed break master on ARM :( | 17:36 |
*** ssam2 has quit IRC | 17:36 | |
*** mdizzle has quit IRC | 17:51 | |
*** sambishop has quit IRC | 17:59 | |
*** tiagogomes_ has quit IRC | 18:01 | |
*** bashrc_ has quit IRC | 18:01 | |
radiofree | a clean 15.02 can't build 15.10 because of "ERROR: Unknown architecture armv8l64 in morphology systems/cross-bootstrap-system-armv8l64-generic.morph" | 18:10 |
* radiofree upgrades morph | 18:10 | |
paulsherwood | radiofree: remove that file | 18:11 |
paulsherwood | (is simpler) | 18:11 |
radiofree | ok | 18:11 |
jjardon | mmm, seems a bit odd that I have to specify in my system a extension that its going to be used only at deploy time (simple-network) | 18:18 |
radiofree | so 15.02 should be able to build 15.10, but the resulting image will be useless | 18:19 |
jjardon | so if I decide to use NETWORK_CONFIG in my deploy morph, I have to rebuid my system and then deploy, instead simply deploy directly | 18:19 |
radiofree | well, i think it will be useless, i'm flashing 15.10 to a clean dev board now, so we'll find out if that can build 15.10 | 18:20 |
radiofree | jjardon: that doesn't sound too good | 18:25 |
pedroalvarez | simple-network should be added to all the systems once it's back | 18:43 |
pedroalvarez | Buy yes, we need to change how we enable extensions for a deployment | 18:44 |
*** wschaller has quit IRC | 18:50 | |
jjardon | pedroalvarez: rigth, Ive added a story here: https://storyboard.baserock.org/#!/story/23 | 18:59 |
*** franred has quit IRC | 19:01 | |
*** edcragg has quit IRC | 19:23 | |
*** edcragg has joined #baserock | 19:25 | |
*** edcragg has quit IRC | 19:40 | |
straycat | ages ago it was suggested all the extensions should be run by default, but maybe it's better to have them specified in the cluster morph instead | 20:15 |
* straycat just did an upgrade for the first time and it just worked :> | 20:17 | |
jjardon | anyone here knows cement? http://builtoncement.com/2.4/dev/quickstart.html I was wondering what would be more difficult: port cliApp to python3 or port morph to cement or similar | 21:05 |
straycat | a lot of morph would have to change if we moved from cliapp | 21:10 |
*** gary_perkins has quit IRC | 21:35 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!