From: Simone Piccardi <Simone.Piccardi@fi.infn.it>
To: Gabriel Paubert <paubert@iram.es>
Cc: LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: MVME2306 : kernel 2.2.6 SUCCESS !
Date: Thu, 22 Apr 1999 21:22:28 +0200 [thread overview]
Message-ID: <371F76F4.27B2850D@fi.infn.it> (raw)
In-Reply-To: Pine.HPP.3.96.990421181843.20020c-100000@gra-ux1.iram.es
Gabriel Paubert wrote:
>
> :-( You should include linux/string.h instead of string.h.
>
> Gabriel.
Hi,
I made the correction you suggested, and that time make zImage compiled
well the routine, but then it stopped a bit further when doing vmlinuz
and zImage.
This was due to these two lines:
ld -o zImage $(OBJECTS) --just-symbols=$(TOPDIR)/vmlinux
objcopy $(TOPDIR)/vmlinux vmlinux -O binary -R .comment -S
in /home/ppc/linux/arch/ppc/prepboot/Makefile
That just don't work on my PC, because in this way the makefile is using
the intel tools, I modified in:
$(CROSS_COMPILE)ld -o zImage $(OBJECTS) --just-symbols=$(TOPDIR)/vmlinux
$(CROSS_COMPILE)objcopy $(TOPDIR)/vmlinux vmlinux -O binary -R .comment
-S
and everything went fine. So now I can start to do check with your
images.
Many thanks for all the help
--
Simone Piccardi
Microsoft is NOT the answer. Microsoft is the Question.
The answer is: "NO!"
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-04-22 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-20 15:40 MVME2306 : kernel 2.2.6 SUCCESS ! David De Ridder
1999-04-21 15:04 ` Simone Piccardi
1999-04-21 16:30 ` Gabriel Paubert
1999-04-22 19:22 ` Simone Piccardi [this message]
1999-04-22 17:21 ` Gabriel Paubert
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=371F76F4.27B2850D@fi.infn.it \
--to=simone.piccardi@fi.infn.it \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
/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;
as well as URLs for NNTP newsgroup(s).