Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    I was seeing at least LDFLAGS leaking into the cross compiler
    But that at least holds true for the sanity check
     Sanity testing C compiler: /home/niluje/x-tools/arm-kobo-linux-gnueabihf/bin/arm-kobo-linux-gnueabihf-gcc
     Is cross compiler: True.
     Sanity check compiler command line: /home/niluje/x-tools/arm-kobo-linux-gnueabihf/bin/arm-kobo-linux-gnueabihf-gcc -isystem/home/niluje/Kindle/CrossTool/Build_KOBO/include -O3 -ffast-math -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=hard -mthumb -D_GLIBCXX_USE_CXX11_ABI=0 -pipe -fomit-frame-pointer -frename-registers -fweb -flto=5 -fuse-linker-plugi n -DG_DISABLE_CAST_CHECKS -pipe -D_FILE_OFFSET_BITS=64 -c /home/niluje/Kindle/CrossTool/Build_KOBO/glib-2.60.6/builddir/meson-private/sanitycheckc.c -o /home/niluje/Kindle/CrossTool/Build_KOBO/glib-2.60.6/builddir/meson-private/sanitycheckc_cross.exe
    NiLuJe
    @NiLuJe
    Anyway, fantastic for native builds, extremely peculiar for cross builds
    I do like the "plain" buildtype for releases that enforce a "don't fuck with my *FLAGS" for PMS ;)
    NiLuJe
    @NiLuJe
    ... except for stuff that meson itself enforces (large file support :/)
    Anyway, managed to build it even for the crappy K3 TC
    Had to resort to sed'ing the meson file to disable one custom linking check, because of course you can't override custom fragments -_-"
    Frans de Jonge
    @Frenzie
    @NiLuJe You could try to report it? :-)
    NiLuJe
    @NiLuJe
    It's apparently by design, for some mysterious reason
    NiLuJe
    @NiLuJe
    And I'm not the only one dealing with the madness, as usual, I should have started by looking how Portage dealt with it: https://gitweb.gentoo.org/repo/gentoo.git/tree/eclass/meson.eclass#n123
    Essentially building a cross-file on-demand from the env, like I did
    -_-"
    NiLuJe
    @NiLuJe
    Random unrelated comment: https://github.com/AppImage/zsync2
    Might actually support HTTPS?
    NiLuJe
    @NiLuJe
    And OpenStack \o/
    C++ and a bunch of deps, though
    NiLuJe
    @NiLuJe
    Also bundles a zlib copy for... reasons?. :/
    Frans de Jonge
    @Frenzie
    Interesting find
    NiLuJe
    @NiLuJe
    Apparently it does support HTTPS, and I did check, it does handle my openstach mirrors that zsync barfs on
    openstack. OpenStach would be a fun rebrand, though :D
    Frans de Jonge
    @Frenzie
    Or an evil clone :P
    NiLuJe
    @NiLuJe
    :D
    NiLuJe
    @NiLuJe
    Hmm, actually tried it for a stable -> nightly update (80% data re-used)
    It does work w/ OpenStack container, but it's fairly slow (probably because of the broken range request support)
    It also deal fairly slowly w/ ota.koreader.rocks
    And slightly slower w/ my nginx instance @ koreader.ak-team.com
    No idea if there's CDN shenanigans involved that mess w/ this, or if that's simply a case of one being lower latency than the other
    So, eh, mixed signals ;p
    Frans de Jonge
    @Frenzie
    Weird
    Frans de Jonge
    @Frenzie
    Some interesting reading https://hashman.ca/git-bash-alias/
    NiLuJe
    @NiLuJe
    Neat ;).
    I generally go with the patch approach for a quick test, but this is useful if you need more involved testing.
    Or if you need to push commits to the PR
    (GH recently made the "add a .diff/.patch to a PR URL" thing more obvious by actually adding links in the footer of the page, before that you kinda had to know it worked ;p)
    Frans de Jonge
    @Frenzie
    Oh, you can also git push origin pull/123/head on GH?
    Btw, I hadn't noticed GH's new (?) contribution schematic thingy prior to reading that post a few hours ago.
    Screenshot_2019-08-03_21-18-55.png
    Looks like I don't create many issues :-P
    NiLuJe
    @NiLuJe
    It used to be opt-in, they might have finally pushed it to prod
    Yeah, if you have write access to the repo the PR is posted against, you can commit in any PR
    Frans de Jonge
    @Frenzie
    No, I just enabled it. I guess I don't navel gaze enough to have noticed whenever they added the option. ;-)
    @NiLuJe I know you can commit in any PR, but I thought you had to clone (part of) the fork.
    NiLuJe
    @NiLuJe
    That's also been made slightly more explicit with a footer notice, IIRC
    Frans de Jonge
    @Frenzie
    I didn't realize you could push straight to origin.
    NiLuJe
    @NiLuJe
    Yeah, the refs are on origin
    Frans de Jonge
    @Frenzie
    What I've been doing to test larger PRs is to create a branch (well, that speaks for itself) and then pull the relevant fork branch into it. Not a lot of effort, but doing origin /pull/12345/head is probably slightly more elegant.
    Frans de Jonge
    @Frenzie
    @NiLuJe I just got into the GitHub Actions beta program.