In article [EMAIL PROTECTED] you write:
I just tried to build d-i on sparc.
You'll need to patch mklibs. My patch is in bug 227291.
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It
In article [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
Btw: I can now build d-i on sparc, but how can I make a cdimage for
testing? After building d-i I got a cdrom-image.img and a cdrom-initrd.gz
Apparently you use debian-cd, which requires a local package mirror.
From my looking into it,
Le Thu, Jan 15, 2004 at 08:42:39PM -0800, Blars Blarson écrivait:
Apparently you use debian-cd, which requires a local package mirror.
From my looking into it, debian-cd will need some minor tweeks to
build bootable sparc CDs. When I get it running, I'll submit
appropriate bugs.
Please
On Wed, 2004-01-14 at 08:59, Joerg Friedrich wrote:
I generally do a sparc32 /bin/bash do make sure everything is detected
right.
when using sparc32 /bin/bash before a make TYPE=cdrom image make
fails like this:
8 (snip)
mkdir -p ./tmp/cdrom/tree/lib/modules/2.4.21-sparc32/kernel; if [
Joerg Friedrich schrieb am Dienstag, 13. Januar 2004 um 16:48:36 +0100:
Joerg Friedrich schrieb am Dienstag, 13. Januar 2004 um 14:45:28 +0100:
ok, quick n dirty:
--- mklibs.orig 2004-01-13 16:27:52.0 +0100
+++ mklibs 2004-01-13 16:28:19.0 +0100
@@ -518,7 +518,7 @@
On Wed, 2004-01-14 at 07:45, Joerg Friedrich wrote:
this solved the problem. it seems that mklibs doesn't work right with
32-bit and 64-bit libraries. does anyone have an idea?
Btw: I can now build d-i on sparc, but how can I make a cdimage for
testing? After building d-i I got a
On Wed, Jan 14, 2004 at 01:45:16PM +0100, Joerg Friedrich wrote:
Btw: I can now build d-i on sparc, but how can I make a cdimage for
testing? After building d-i I got a cdrom-image.img and a cdrom-initrd.gz
Three possibilities:
- If you are confident that the kernel and initrd have been
Jeff Bailey schrieb am Mittwoch, 14. Januar 2004 um 08:31:46 -0500:
On Wed, 2004-01-14 at 07:45, Joerg Friedrich wrote:
this solved the problem. it seems that mklibs doesn't work right with
32-bit and 64-bit libraries. does anyone have an idea?
Btw: I can now build d-i on sparc, but how
Hi,
I just tried to build d-i on sparc.
System was a new installed woody upgraded to unstable.
recent cvs checkout, all build-debs satisfied.
btw. its a sun e450
using make TYPE=cdrom
and this is the problem:
# Library reduction.
mkdir -p ./tmp/cdrom/tree/lib
mklibs -v -d
Blars Blarson wrote:
The sparc netcfg udebs need to get into the debian archives. (The
sparc autobuilder is either not running or still trying to catch up.
I'd rate python a higher priority.) Should I sign and upload the
package I built?
Yes, certianly.
--
see shy jo
signature.asc
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
a. Work to get the debian-installer package cleanly building for
all relevant image types.
cdrom and netboot are now cleanly building. At some future point
floppy may be added for sparc32, but that's not something I'm
concerned about.
Blars Blarson wrote:
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
a. Work to get the debian-installer package cleanly building for
all relevant image types.
cdrom and netboot are now cleanly building. At some future point
floppy may be added for sparc32, but that's not
After not doing anything on it for six weeks, I'm again trying to get
debian-installer working on sparc.
First iritation was needing to rebuild python2.3, as it's a dependancy
of a build-dendancy. (Apparently the sparc autobuilder is still
down.) That took 14 hours to compile. I also had to
Blars Blarson wrote:
After not doing anything on it for six weeks, I'm again trying to get
debian-installer working on sparc.
First iritation was needing to rebuild python2.3, as it's a dependancy
of a build-dendancy. (Apparently the sparc autobuilder is still
down.) That took 14 hours to
14 matches
Mail list logo
