* [parisc-linux] build errors, recipe still not up to date?
@ 2000-03-27 21:31 Mike Brancato
2000-03-27 22:07 ` Mike Brancato
0 siblings, 1 reply; 4+ messages in thread
From: Mike Brancato @ 2000-03-27 21:31 UTC (permalink / raw)
To: parisc-linux
I've been folowing the recipe step by step, yet i still get build
problems. i'm working witht he march 26th 2.3.42 version, and everything
in the kernel is building fine, except the link at the end.
anyone know? did i not get something?
mike
make[2]: Entering directory `/tmp/mabran3/palo/ipl'
echo "char *bld_info = \"`whoami`@`hostname` `date`\";" > build.c
hppa1.1-linux-gcc -I/tmp/mabran3/palo/../linux-2.3/include -I../lib -O2
-fwritable-strings -mdisable-fpregs -Wall -c -o build.o build.c
rm -f build.c
hppa1.1-linux-ld -N -Ttext 0x500000 -e '$START$' -o ipl crt0.o byteio.o
elf64.o ipl.o offset.o som.o diskpart.o ext2.o
lib.o pdc_bootio.o vsprintf.o elf32.o fileio.o
load.o pdc_cons.o build.o
/tmp/mabran3/palo/../linux-2.3/arch/parisc/lib/milli.o
rm -f build.o
make[2]: Leaving directory `/tmp/mabran3/palo/ipl'
./palo/palo -s -b ipl/ipl -k /tmp/mabran3/palo/../linux-2.3/vmlinux -r
/tmp/mabran3/palo/../linux-2.3/ramdisk.bin \
-c "0/vmlinux HOME=/ TERM=LINUX root=/dev/ram initrd=0/ramdisk" lifimage
palo version 0.8 mabran3@alpha Mon Mar 27 16:30:10 EST 2000
/tmp/mabran3/palo/../linux-2.3/ramdisk.bin: No such file or directory
make[1]: *** [lifimage-only] Error 2
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [parisc-linux] build errors, recipe still not up to date?
2000-03-27 21:31 [parisc-linux] build errors, recipe still not up to date? Mike Brancato
@ 2000-03-27 22:07 ` Mike Brancato
2000-03-27 23:40 ` willy
0 siblings, 1 reply; 4+ messages in thread
From: Mike Brancato @ 2000-03-27 22:07 UTC (permalink / raw)
To: parisc-linux
ok, I guess I forgot to ask my real question, how would I create the
ramdisk image?
also, say I want nfs, I have two hpux 11.0 machines I could mount from.
machine A has a raid array (/users/) attached to it, and machine B mounts
that same array in /users/ via nfs. can i have the root for the parisc
linux in /opt/linuxroot/ or something, and have the parisc machine mount
that thru nfs? i'm new to nfs.
mike
On Mon, 27 Mar 2000, Mike Brancato wrote:
>
> I've been folowing the recipe step by step, yet i still get build
> problems. i'm working witht he march 26th 2.3.42 version, and everything
> in the kernel is building fine, except the link at the end.
>
> anyone know? did i not get something?
>
> mike
>
> make[2]: Entering directory `/tmp/mabran3/palo/ipl'
> echo "char *bld_info = \"`whoami`@`hostname` `date`\";" > build.c
> hppa1.1-linux-gcc -I/tmp/mabran3/palo/../linux-2.3/include -I../lib -O2
> -fwritable-strings -mdisable-fpregs -Wall -c -o build.o build.c
> rm -f build.c
> hppa1.1-linux-ld -N -Ttext 0x500000 -e '$START$' -o ipl crt0.o byteio.o
> elf64.o ipl.o offset.o som.o diskpart.o ext2.o
> lib.o pdc_bootio.o vsprintf.o elf32.o fileio.o
> load.o pdc_cons.o build.o
> /tmp/mabran3/palo/../linux-2.3/arch/parisc/lib/milli.o
> rm -f build.o
> make[2]: Leaving directory `/tmp/mabran3/palo/ipl'
> ./palo/palo -s -b ipl/ipl -k /tmp/mabran3/palo/../linux-2.3/vmlinux -r
> /tmp/mabran3/palo/../linux-2.3/ramdisk.bin \
> -c "0/vmlinux HOME=/ TERM=LINUX root=/dev/ram initrd=0/ramdisk" lifimage
> palo version 0.8 mabran3@alpha Mon Mar 27 16:30:10 EST 2000
> /tmp/mabran3/palo/../linux-2.3/ramdisk.bin: No such file or directory
> make[1]: *** [lifimage-only] Error 2
>
>
> ---------------------------------------------------------------------------
> To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
> `unsubscribe' as the subject.
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [parisc-linux] build errors, recipe still not up to date?
2000-03-27 22:07 ` Mike Brancato
@ 2000-03-27 23:40 ` willy
2000-03-28 15:13 ` dkennedy
0 siblings, 1 reply; 4+ messages in thread
From: willy @ 2000-03-27 23:40 UTC (permalink / raw)
To: Mike Brancato; +Cc: parisc-linux
On Mon, Mar 27, 2000 at 05:07:03PM -0500, Mike Brancato wrote:
> ok, I guess I forgot to ask my real question, how would I create the
> ramdisk image?
Easy: Download one from puffin.external.hp.com/pub/parisc/ramdisks/
Hard: create a non-sparse file, using dd. create an ext2 filesystem on it.
Mount it via loopback. copy whatever you want onto it.
> also, say I want nfs, I have two hpux 11.0 machines I could mount from.
> machine A has a raid array (/users/) attached to it, and machine B mounts
> that same array in /users/ via nfs. can i have the root for the parisc
> linux in /opt/linuxroot/ or something, and have the parisc machine mount
> that thru nfs? i'm new to nfs.
Linux NFS Root looks for /tftpboot/<ip-address> by default. I think
there's a way to change it, but I forget how.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [parisc-linux] build errors, recipe still not up to date?
2000-03-27 23:40 ` willy
@ 2000-03-28 15:13 ` dkennedy
0 siblings, 0 replies; 4+ messages in thread
From: dkennedy @ 2000-03-28 15:13 UTC (permalink / raw)
To: willy; +Cc: Mike Brancato, parisc-linux
On Mon, 27 Mar 2000 willy@thepuffingroup.com wrote:
> Linux NFS Root looks for /tftpboot/<ip-address> by default. I think
> there's a way to change it, but I forget how.
If you are DHCPing the Linux box, you can specify the NFS Root
directory as an option in the DHCP file. Also, the (regular) Linux
kernel takes a command line argument which is the NFS Root directory.
--
David Kennedy, Senior Linux Consultant, Linuxcare, Inc.
613.562.9594 tel, 613.562.9304 fax
dkennedy@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2000-03-28 14:02 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-03-27 21:31 [parisc-linux] build errors, recipe still not up to date? Mike Brancato
2000-03-27 22:07 ` Mike Brancato
2000-03-27 23:40 ` willy
2000-03-28 15:13 ` dkennedy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox