Re: [mer-general] Platform SDK improvement brainstorming meeting Tueday 18 Sep
hi David; I'm not sure exactly what the problem you're trying to solve is but I'm pretty sure this is not the right approach in general. The SDK is a standalone environment which should have no links to the host binaries. Please revert that patch from your SDK setup and either log a bug with the problem you're encountering or come and discuss it on #mer so we can help find the correct approach. Sorry, my bad, I did not post link to related bug, here it goes: https://bugs.merproject.org/show_bug.cgi?id=567 PS. Though you are on Cc list in there ;) -- Aliaksei David On 13/09/12 07:40, Aliaksei Katovich wrote: hi; would it be possible to apply patch in attachment. The problem it fixes is related to 64-bit systems, where /lib32 and /lib64 dirs are present. Otherwise compilation of e.g. standalone kernel modules is not possible. -- Aliaksei Hi We'll be having a brainstorming meeting to get ideas on how to improve the platfrom SDK and it's usability. If you cannot attend the meeting and have some input, please send your thoughts by replying to this mail. Meeting will be held Tuesday 18 September from 9:00 to 10:00 UTC in #mer-meeting @freenode ps. in addtion to sharing thoughts we welcome helping hands to implement and test the improvements :) BR, Timo -- Don't worry, you'll be fine; I saw it work in a cartoon once...
Re: [mer-general] Platform SDK improvement brainstorming meeting Tueday 18 Sep
Hi David, Let me answer your questions. This URL https://img.merproject.org/images/sdk/ actually lies into my face. mer-sb2sdk-i486-chroot-latest.tar.bz2 is by far not the latest release at all. It was very confusing that I downloaded the latest image, then had to upgrade it... because it was not the latest. Please fix this. Actually that is the latest release - however, although I have been doing quite a bit of work on improving the SDK I've not actually had time to make another proper release. Not it's not the latest. If it were the latest, then no upgrades would be required. Some other thought: After I restart my machine, simply calling '/srv/mer/sdks/sdk/mer-sdk-chroot mount' doesn't work. I have to unmount it first. (Despite it saying that it's not mounted.) Thanks for the bug report. Ideally you should file this in https://bugs.merproject.org/ If you do that could you clarify doesn't work ... does it give any error message? No error messages at all, it just drops me into an empty, useless terminal. I wasn't sure whether this is a bug or a feature, thus I didn't file a bug report. Cheers, Timur
