Hi Sylvain, I didn't realize it when you responded, but <sys/_types.h> is a toolchain problem, and you just nailed it. Cool:) Early on, before it was pointed to me to use the Getting Started wiki, I used the src/README.building file, which is a normal practice for all unix developers/admins. When I couldn't find the gnuarm.com toolchain, I searched the web for ubuntu toolchains and found the linaro one, gcc-arm-linux-gnueabi, which doesn't provide <sys_types.h>. No dev version either:( So, when using that toolchain, I had to come up with the missing <sys/_types.h>, and the only one I could find was from vivado:( Is there a point to my life's story? Just to pont out into how much problems one can get with the wrong README file. I realize that building procedure must be defined and maintained in 1 place, either the wiki or the README file. The wiki is a non standard unix location, but a more convenient one. I propose to fix the info in README.building, to avoid future issues. The fix can be as simple as "Prerequisite is the armel toolchain. Check the <wiki url> for installation" HTH Nikos On Sun, May 13, 2018 at 12:11 PM, Nikos Balkanas &lt;nbalkanas(a)gmail.com&gt; wrote:

Got it. I'm on it:) On Mon, May 14, 2018 at 2:45 PM, Neels Hofmeyr &lt;nhofmeyr(a)sysmocom.de&gt; wrote:

Hi, On 14/05/18 20:38, Nikos Balkanas wrote: No, it's not. You must use: ssh://YOUR_USER@gerrit.osmocom.org:29418/osmocom-bb.git -- - Pau Espin Pedrol &lt;pespin(a)sysmocom.de&gt; http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

On Tue, May 15, 2018 at 3:38 PM, Neels Hofmeyr &lt;nhofmeyr(a)sysmocom.de&gt; wrote: ​I think I got it working. I got this cryptic response: -> git push ssh://osmo/osmocom-bb.git Everything up-to-date ​Anyway to check if changes committed? Cloning from gerrit will just give me ​the main osmocom-bb.git :( Nikos

On Wed, May 16, 2018 at 3:38 PM, Neels Hofmeyr &lt;nhofmeyr(a)sysmocom.de&gt; wrote: ​Too much Information. Confusing. There should be only 3 headers aside from the introductory why you use gerrit: 1) Creating user in gerrit 2) Setting up gerrit for commits and pushing 3) Push Patch for Review The only relevant entry in there is "Push for Review", and It is wrong:( git push gerrit HEAD:refs/for/master/my_topic It is different from what you told me in this mail, and gerrit is not an FQD. When I try to use FQD for gerrit, I get pubkey errors: -> git push nbalkanas@gerrit.osmocom.org:29418 HEAD:refs/for/master/Minor_Typo_Fixes Permission denied (publickey). fatal: Could not read from remote repository. If you still can't get it to work, please show us your ~/.ssh/config that ​> cat .ssh/config ServerAliveInterval = 300 Host osmo Hostname gerrit.osmocom.org Port 29418 User nbalkanas ​-> git status ​On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: src/README.building no changes added to commit (use "git add" and/or "git commit -a") -> git add src/README.building -> git add -f src/shared/libosmocore/configure -> git push ssh://osmo/osmocom-bb.git Everything up-to-date That's a major shortcoming. CVS has its problems but at least you can check what you have just commited:(​ ​Yes, I created user and added public key. Otherwise I would keep getting: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

Ty domi, I got further along with commit:) Unfortunately, it now tells me that user nbalkanas has no rights to push:( Np, I can find help for git myself, if I need to. On the bright side, git offers enough messages during push, so no checking of committed data is needed @Neels, can you please authorize me? BR, Nikos On Thu, May 17, 2018 at 12:32 AM, Tomcsányi, Domonkos &lt;domi(a)tomcsanyi.net&gt; wrote:

Yeah, I have done all that. I'm still confused with the "Push for review" section. -> git push gerrit HEAD:refs/for/master fatal: 'gerrit' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. As I mentioned to Domi, I just need push priviledges to gerrit. This is my output: -> cat .ssh/config ServerAliveInterval = 300 Host osmo Hostname gerrit.osmocom.org Port 29418 User nbalkanas -> git push ssh://osmo/osmocom-bb.git Counting objects: 32, done. Delta compression using up to 8 threads. Compressing objects: 100% (7/7), done. Writing objects: 100% (7/7), 96.37 KiB | 0 bytes/s, done. Total 7 (delta 4), reused 0 (delta 0) remote: Resolving deltas: 100% (4/4) remote: Branch refs/heads/master: remote: You are not allowed to perform this operation. remote: To push into this reference you need 'Push' rights. remote: User: nbalkanas remote: Please read the documentation and contact an administrator remote: if you feel the configuration is incorrect remote: Processing changes: refs: 1, done To ssh://osmo/osmocom-bb.git ! [remote rejected] master -> master (prohibited by Gerrit: ref update access denied) error: failed to push some refs to 'ssh://osmo/osmocom-bb.git' gerrit is not a repository:( I also don't have priviledges to post to gerrit, which is fine, it is the gerrit master, and not the gerrit review... Not that for the git push output i've posted, all pubkeys and accounts are in order... Nikos On Thu, May 17, 2018 at 3:55 AM, Neels Hofmeyr &lt;nhofmeyr(a)sysmocom.de&gt; wrote: