X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7BFF0.006E1867@onstor-exch02.onstor.net>; Fri, 6 Jul 2007 09:06:32 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7BFF0.006E1867"
References: <BB375AF679D4A34E9CA8DFA650E2B04E022158B2@onstor-exch02.onstor.net> <20070706030201.GA21720@scowler.net>
Content-class: urn:content-classes:message
Subject: FW: Request for build information
Date: Fri, 6 Jul 2007 09:05:25 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E042EFF76@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Request for build information
Thread-Index: Ace/egqfYdR9jb3kStiwWJW6Yc9nswAdc3JK
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Tim Gardner" <tim.gardner@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7BFF0.006E1867
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I got an answer from the debian glibc development group.


-----Original Message-----
From: Clint Adams [mailto:schizo@debian.org]
Sent: Thu 7/5/2007 8:02 PM
To: Larry Scheer
Cc: debian-glibc@lists.debian.org
Subject: Re: Request for build information
=20
On Thu, Jul 05, 2007 at 04:47:13PM -0700, Larry Scheer wrote:
> What were the steps and tools that were used to compile and build the
> glibc packages for the mipsel arch? I am primarily interested in how =
the
> Debian patches were applied, the source code compiled, and the =
libraries
> built.

The glibc source package is transferred to a bonafide mipsel machine, on
which the equivalent of the following line is run:
dpkg-buildpackage -rfakeroot -B

(You'll need to install the dpkg-dev and build-essential packages to
 accomplish this).

Since you want to cross-compile, you may want to install the dpkg-cross
package and use that.  If it happens that the source package is not
clean for a cross build that way, give a shout so we can fix it.




------_=_NextPart_001_01C7BFF0.006E1867
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>FW: Request for build information</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I got an answer from the debian glibc development =
group.<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Clint Adams [<A =
HREF=3D"mailto:schizo@debian.org">mailto:schizo@debian.org</A>]<BR>
Sent: Thu 7/5/2007 8:02 PM<BR>
To: Larry Scheer<BR>
Cc: debian-glibc@lists.debian.org<BR>
Subject: Re: Request for build information<BR>
<BR>
On Thu, Jul 05, 2007 at 04:47:13PM -0700, Larry Scheer wrote:<BR>
&gt; What were the steps and tools that were used to compile and build =
the<BR>
&gt; glibc packages for the mipsel arch? I am primarily interested in =
how the<BR>
&gt; Debian patches were applied, the source code compiled, and the =
libraries<BR>
&gt; built.<BR>
<BR>
The glibc source package is transferred to a bonafide mipsel machine, =
on<BR>
which the equivalent of the following line is run:<BR>
dpkg-buildpackage -rfakeroot -B<BR>
<BR>
(You'll need to install the dpkg-dev and build-essential packages to<BR>
&nbsp;accomplish this).<BR>
<BR>
Since you want to cross-compile, you may want to install the =
dpkg-cross<BR>
package and use that.&nbsp; If it happens that the source package is =
not<BR>
clean for a cross build that way, give a shout so we can fix it.<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7BFF0.006E1867--
