Building RTEMS 4.11.0 RC4 for i386 targets

[Cláudio Silva]

Hello,

Regarding draconian firewalls, I have spent more time than I would like to
admit working around git:// protocol issues. Last time I checked the git
protocol didn't follow very well git proxy rules nor the system's rules.
This issue is especially painful when you have git repos with submodules
where the submodules are connected through git:// instead of http(s),
because you have to discover and manually change every URL to http.
I have worked around this issue by creating a SOCKS proxy and forcing git
proxy every connection through it. This is only possible because I am
allowed to connect to external SSH server.
In summary, you have to create a connection with a remote server
(non-firewalled) through ssh, creating a SOCKS proxy:

ssh -D 9052 user at external_server

Then you need this small script that essentially uses socat to force git to
connect to that SOCKS server:
https://gist.github.com/cdcs/bc00ba3121c09013f2c057b549e6930d

Then you need to mark the script as executable and tell git to use it.

chmod +x gitproxy
git config --global core.gitproxy gitproxy

This workaround is able to use other types of proxies besides SOCKS. So if
you have a less restricted proxy available, just change the SOCAT options
to use it.
It's better to unset the option after you are through with git protocol
clones as every git connection in unnecessarily being proxied through it
(git config --unset core.gitproxy).

Anyway the long term solution is to migrate every PATH to HTTPS.

Thanks,
Best Regards,
Cláudio

On Thu, Nov 3, 2016 at 9:41 PM Chris Johns <chrisj at rtems.org> wrote:

> On 04/11/2016 07:00, Ricardo Derbes wrote:
> > Hello.
> > About rtems 4.11.0-rc4 release building:
> > Following Chris instructions, I have built rtems 4.11.0-rc4 release,
> > for i386/pc686 target, without any glitch.
> > I issued the --without-rtems option when running
> > ../source-builder/sb-set-builder in rtems-source-builder/rtems folder,
> > because I wanted to build later the pc686 BSP, without networking
> > support, as to add libbsd.
> >
> > After that, using i386 BSP and tools (i386-rtems-gcc et al) I made a
> > checkout of rtems-libbsd from git://git.rtems.org/rtems-libbsd.git and
> > built it, also without any issue, so now I have libbsd.a library and
> > includes along with pc686 files.
>
> Are you using the libbsd 4.11 branch with 4.11.0-rc4?
>
> I have forgotten to include the libbsd source in the release which is a
> mistake on my part. I will add it for RC5. Thanks for reporting this.
>
> > The host used was Fedora19 x86-64 host (on a VM), and the only package
> > I had to install was waf (yum install waf).
> >
> > Only one caveat: for corporative users like me, who live behind a
> > draconian proxy with only port 80 available, it's not possible to
> > download the packages needed by RSB, nor even git://...
> > Will be possible to add http and proxy support for RSB, and http
> > protocol for git repos?
>
> There are two issues here, first if I add the 4.11 branch of libbsd as a
> tar file to the sources directory you should be able to fetch the needed
> source from the RTEMS ftp server using http which solves your problem
> for 4.11.
>
> The second issue of git verses http in the RSB means changing all the
> git:// paths in the configuration files. Maybe we can do this but not
> for 4.11.0. I am not sure what I need to do to add proxy support so some
> help there would be most welcome. I suspect a --proxy option would be
> needed.
>
> Having restricted firewalls is common with RTEMS users so we are willing
> to do what we can to help. One of the important goals of our releases is
> to have _all_ referenced source in the sources directory of a release to
> help here. This means all source even source from outside RTEMS.
>
> > Thank you
>
> Thank you for taking the time to test and report what you have found.
> Every little bit helps improve 4.11.
>
> Chris
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20161104/1fa988cd/attachment-0002.html>