public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Yuri Vasilevski <yvasilev@duke.math.cinvestav.mx>
To: gentoo-embedded@lists.gentoo.org
Cc: vapier@gentoo.org
Subject: Re: [gentoo-embedded] openssl for arm
Date: Tue, 3 May 2005 21:07:47 -0500	[thread overview]
Message-ID: <20050503210747.0401b795@edune.lan> (raw)
In-Reply-To: <200505032130.38769.vapier@gentoo.org>

Hi!

> > But I personally preferred to use softgun (en arm
> > emulator, in portage) with a custom stage I made
> > with soft-float gcc and uclibc (i used the patches
> > posted in http://bugs.gentoo.org/show_bug.cgi?id=75585).
> > And this way I can compile and use openssl + openssh
> > without any problems.
> 
> could you do me a favor and write up a little HOWTO for this ?  i'd like to 
> make an index of howtos for all the emulators out there 
> (qemu/hercules/softgun/etc...)

I'm going on vacation tomorrow for a week, and after that
i can try to write something. But the problem i see is that
the way I did it, it involves so many steps in hacking many
different things that I'm not sure that it is a good idea
to write about something so unpolished.

But if you want, and there is interest in it we can try
to make it more functional.

> i wasnt able to figure out how to make softgun work nicely :/

The way i did it was:

1.- Patch linux 2.6.8.1 (it was the one used at that time
    by the developer of softgun)
2.- Modify this patched version to register more that 64MB
    of ram and remove watchdog initialization.
    (i can try to (and plan to) make a patch for softgun's
    patch to linux 2.6.10)
3.- Modify uclibc's build root to build soft-float gcc and
    uclibc with the patches from that bug report.
4.- boot to softguns image, mount over nfs my root and
    chroot to it. and there build python and portage by
    hand. (after that i found a better way to do this step
    outlined in:
    http://dev.gentoo.org/~solar/uclibc/uclibc.txt)
5.- In this chrooted environment bootstrap gentoo.
6.- emerge system
7.- emerge openssh vixie-cron syslog-ng devfsd ...
8.- build another custom kernel to boot from nfs,
    with devfs, preemptive and some another modifications.
9.- boot to my arm gentoo directly over nfs

The problem I'm having now is that i sometimes get
segmentation faults that are reported by softgun
as "Alignment Problem in Load/Store Multiple".
And the things is that they happen in deterministic
manner on programs that work fine when called by hand.
And so far my best guess is that it may be corrected
when I will move to the kernel that is used in the
development of softgun (i.e 2.6.10)

Let me know about your thoughts about the how-to
and the steps I outlined.

Yuri.

-- 
gentoo-embedded@gentoo.org mailing list


  reply	other threads:[~2005-05-04  2:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-03 20:42 [gentoo-embedded] openssl for arm Tim Dodge
2005-05-03 20:50 ` Mike Frysinger
2005-05-04  1:21   ` Yuri Vasilevski
2005-05-04  1:30     ` Mike Frysinger
2005-05-04  2:07       ` Yuri Vasilevski [this message]
2005-05-04  2:25         ` Mike Frysinger
2005-05-04  3:05           ` Yuri Vasilevski
2005-05-13 17:18       ` Yuri Vasilevski
2005-05-15 17:39         ` Tim Dodge
2005-05-15 18:21           ` Yuri Vasilevski
2005-05-15 18:50             ` Tim Dodge
2005-05-04  9:15     ` Tim Dodge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050503210747.0401b795@edune.lan \
    --to=yvasilev@duke.math.cinvestav.mx \
    --cc=gentoo-embedded@lists.gentoo.org \
    --cc=vapier@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox