[Bug 1322178] Re: new armhf click build chroot is DEB_BUILD_ARCH=amd64
** Changed in: savilerow Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322178 Title: new armhf click build chroot is DEB_BUILD_ARCH=amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/developer-ubuntu-com/+bug/1322178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322178] Re: new armhf click build chroot is DEB_BUILD_ARCH=amd64
My two cents (echoing in part what Florian said), Critical pieces of information devs need include: * dpkg-architecture vars do not clearly reflect the click chroot --architecture (they reflect the host system). * to install compiled build dep debian pkgs, you must add the architecture to the pkgs, as in: apt-get install package:armhf. Adding these to some general discussion of click chroots and developing for touch may help. Perhaps in a C++ section/guide. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322178 Title: new armhf click build chroot is DEB_BUILD_ARCH=amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/developer-ubuntu-com/+bug/1322178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322178] Re: new armhf click build chroot is DEB_BUILD_ARCH=amd64
Sorry, I think I'm not quite sure how this bug should be fixed on developer.ubuntu.com. Is there a summary of what needs to be changed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322178 Title: new armhf click build chroot is DEB_BUILD_ARCH=amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/developer-ubuntu-com/+bug/1322178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322178] Re: new armhf click build chroot is DEB_BUILD_ARCH=amd64
Can maybe somebody point out in which way developer.ubuntu.com should be fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322178 Title: new armhf click build chroot is DEB_BUILD_ARCH=amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/developer-ubuntu-com/+bug/1322178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322178] Re: new armhf click build chroot is DEB_BUILD_ARCH=amd64
@Daniel, fire a bug on https://launchpad.net/developer-ubuntu-com and mail to those who works on it ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322178 Title: new armhf click build chroot is DEB_BUILD_ARCH=amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/developer-ubuntu-com/+bug/1322178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322178] Re: new armhf click build chroot is DEB_BUILD_ARCH=amd64
good documents on how to use the chroot is the right fix to this issue. Maybe https://launchpad.net/developer-ubuntu-com is the right place for this issue ? ** Changed in: savilerow Importance: Undecided = Medium ** Changed in: savilerow Status: New = Triaged ** Tags added: tracking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322178 Title: new armhf click build chroot is DEB_BUILD_ARCH=amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1322178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322178] Re: new armhf click build chroot is DEB_BUILD_ARCH=amd64
** Also affects: developer-ubuntu-com Importance: Undecided Status: New ** Changed in: savilerow Importance: Medium = Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322178 Title: new armhf click build chroot is DEB_BUILD_ARCH=amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/developer-ubuntu-com/+bug/1322178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322178] Re: new armhf click build chroot is DEB_BUILD_ARCH=amd64
I think docs would help and they should go somewhere here: https://developer.ubuntu.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322178 Title: new armhf click build chroot is DEB_BUILD_ARCH=amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1322178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322178] Re: new armhf click build chroot is DEB_BUILD_ARCH=amd64
This is still an issue, and very confusing. I assume that most developers who need external dependenices for the click package run into this and wonder why the linker complains about not finding the library. I guess most developers find it more convenient to add build rules that copy prebuilt libraries from the chroot into the click package instead of adding the library source code to their project. This ensures easy click package updates whenever Ubuntu updates the library (without API breaking changes of course). For this use case, running apt-get install libwhatever-dev in the chroot is the first required step, and the user expects to have a somewhat sane environment when clicking the Maintain button. I worked around this by installing libupnp6:armhf and libupnp6-dev:armhf instead of libupnp-dev. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322178 Title: new armhf click build chroot is DEB_BUILD_ARCH=amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1322178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322178] Re: new armhf click build chroot is DEB_BUILD_ARCH=amd64
I think it is not a bug, but indeed a confusing behavior. But this multi arch click chroot is the very essence of the click build story. I agree that the default arch when installing a package in the click chroot should be the target arch, as developers install more typically libs, headers, qml plugins than developer tools. Anyhow, I think the click package is the best address for this issue and not the QtC plugin. ** Project changed: qtcreator-plugin-ubuntu = click (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322178 Title: new armhf click build chroot is DEB_BUILD_ARCH=amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1322178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
