[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [microblaze-uclinux] kernel compilation error: 'vmlist_lock undeclared'
Hi Anand,
I don't have any experience using gdbserver running under the uClinux
kernel; I've only used the gdbserver that runs as part of XMD.
There are some issues running the kernel from FLASH. There were some recent
posts regarding this.
Regards,
David Banas
Field Applications Engineer
Nu Horizons Electronics Corp.
2070 Ringwood Avenue
San Jose, CA 95131
(408)434-0800 - office
(415)846-5837 - cell
http://www.nuhorizons.com
> -----Original Message-----
> From: owner-microblaze-uclinux@itee.uq.edu.au [mailto:owner-microblaze-
> uclinux@itee.uq.edu.au] On Behalf Of Anand Shivhare
> Sent: Friday, July 15, 2005 10:55 AM
> To: microblaze-uclinux@itee.uq.edu.au
> Subject: Re: [microblaze-uclinux] kernel compilation error: 'vmlist_lock
> undeclared'
>
> Hello David,
>
> I was got the gdbserver sources and mb-gdb-user. mb-gdb-user is
> working fine but i am not able to compile gdbserver.
> Other issue is :
>
> Currently
> 1. I compile
> 2. Run uClinux from RAM
> 3. I have also used utility provided to copy program
> from RAM to FLASH
> 4. I copied uClinux from flash to RAM and was able to
> run it successfuly.
> Now I want to run uClinux directly from flash (not from RAM).
> Do I need to do any chages in compilation or linking.
> Do I need to mount jffs. If I don't how can I remove it from
> initial(booting) mount sequence.
>
>
> Thanx for your support.
> Anand Shivahre
> Reliance Infocomm
> ITIC
> India
>
>
>
>
> On 7/5/05, David Banas <dbanas@nuhorizons.com> wrote:
> > Hi Anand,
> >
> > 2 Things:
> >
> > 1) A general question to you and the group,
> > What happens if you try and remotely debug a user-space
> application
> > the way you debug the booting kernel? (That is, using the gdb-server
> built
> > into XMD, as opposed to one running on the target.)
> >
> > 2) As you can see from John's reply, below, as well as the many messages
> on
> > this topic, which have come through the list in the recent months, this
> is
> > not a quickly solved problem. Regrettably, I'm unable to provide any
> sort of
> > "quick fix" for this one.
> >
> > Regards,
> >
> > David Banas
> > Field Applications Engineer
> > Nu Horizons Electronics Corp.
> > 2070 Ringwood Avenue
> > San Jose, CA 95131
> > (408)434-0800 - office
> > (415)846-5837 - cell
> > http://www.nuhorizons.com
> > > -----Original Message-----
> > > From: owner-microblaze-uclinux@itee.uq.edu.au [mailto:owner-
> microblaze-
> > > uclinux@itee.uq.edu.au] On Behalf Of Anand Shivhare
> > > Sent: Tuesday, July 05, 2005 7:23 AM
> > > To: microblaze-uclinux@itee.uq.edu.au
> > > Subject: Re: [microblaze-uclinux] kernel compilation error:
> 'vmlist_lock
> > > undeclared'
> > >
> > > Hi David,
> > >
> > > I have got a spartan-3 1500 board from nu-horizon, (sent by you)
> > > and currently working with uClinux. I am having problem with
> > > compilation of gdbserver. I want to use it for debug my own user
> > > application. please help me.
> > > Is there any other way to debug user application?
> > >
> > > Please help me.
> > >
> > >
> > > Anand Shivhare
> > > Reliance Infocomm
> > > ITIC Gurgaon
> > > India
> > >
> > >
> > >
> > >
> > > On 5/27/05, David Banas <dbanas@nuhorizons.com> wrote:
> > > > Thanks, John!
> > > >
> > > > As part of preparing an "official" release for submission to your
> Web
> > > site,
> > > > I've attempted to chose the appropriate tag for users to specify
> when
> > > > checking out both kernel and dist. sources from the archive, the
> intent
> > > > being to know for certain that the patches I supply as part of that
> > > release
> > > > will apply cleanly to the particular version of the source that I
> > > recommend
> > > > and that the resultant code will compile.
> > > >
> > > > I settled on "uClinux-2_4_29-uc0" for the kernel source, only
> because
> > > the
> > > > date associated with the more recent tag,
> > > > "before-snapgear-code-sync-20050504", (May 4, 2005) appeared to be
> > > > coincident with some complaints regarding recently introduced kernel
> > > > instabilities, which I thought I recalled coming through the list.
> > > >
> > > > However, now I've run into the second case where the version of
> source
> > > code
> > > > associated with the former tag is quite old, as compared with that
> of
> > > the
> > > > latter. And, as I've just noticed after applying the patch you
> > > recommend,
> > > > below, I still don't have a successful kernel compilation. So,
> perhaps
> > > > there're more places where these 2 versions are quite different?
> > > >
> > > > Have I made a poor decision here? Is the
> > > > "before-snapgear-code-sync-20050504" version of the kernel code a
> > > "stable"
> > > > release, and is it the one I should recommend to users of my
> release?
> > > >
> > > > Thanks,
> > > >
> > > > David Banas
> > > > Field Applications Engineer
> > > > Nu Horizons Electronics Corp.
> > > > 2070 Ringwood Avenue
> > > > San Jose, CA 95131
> > > > (408)434-0800 - office
> > > > (415)846-5837 - cell
> > > > http://www.nuhorizons.com
> > > > > -----Original Message-----
> > > > > From: owner-microblaze-uclinux@itee.uq.edu.au [mailto:owner-
> > > microblaze-
> > > > > uclinux@itee.uq.edu.au] On Behalf Of John Williams
> > > > > Sent: Thursday, May 26, 2005 9:23 PM
> > > > > To: microblaze-uclinux@itee.uq.edu.au
> > > > > Subject: Re: [microblaze-uclinux] kernel compilation error:
> > > 'vmlist_lock
> > > > > undeclared'
> > > > >
> > > > > Hi David,
> > > > >
> > > > > David Banas wrote:
> > > > > > Hi All,
> > > > > >
> > > > > > Has anyone bumped into this error when compiling the kernel?
> It's
> > > > > occurring
> > > > > > while make is operating in the './fs/proc' directory.
> > > > > >
> > > > > > kcore.c: In function `read_kcore':
> > > > > > kcore.c:362: `vmlist_lock' undeclared (first use in this
> function)
> > > > >
> > > > > You need to freshen your copy of linux-
> 2.4.x/include/linux/vmalloc.h
> > > > > from CVS, or apply the following trivial patch:
> > > > >
> > > > > Regards,
> > > > >
> > > > > John
> > > > >
> > > > > Index: vmalloc.h
> > > > >
> ===================================================================
> > > > > RCS file: /var/cvs/uClinux-2.4.x/include/linux/vmalloc.h,v
> > > > > retrieving revision 1.4
> > > > > retrieving revision 1.5
> > > > > diff -u -b -B -w -p -r1.4 -r1.5
> > > > > --- vmalloc.h 27 Aug 2003 03:13:47 -0000 1.4
> > > > > +++ vmalloc.h 14 Feb 2005 06:32:51 -0000 1.5
> > > > > @@ -69,6 +69,12 @@ extern struct vm_struct * vmlist;
> > > > >
> > > > > #else /* NO_MM */
> > > > >
> > > > > +/*
> > > > > + * vmlist_lock is a read-write spinlock that protects vmlist
> > > > > + * Used in mm/vmalloc.c (get_vm_area() and vfree()) and
> > > fs/proc/kcore.c.
> > > > > + */
> > > > > +extern rwlock_t vmlist_lock;
> > > > > +
> > > > > extern void vfree(void * addr);
> > > > > extern void *__vmalloc(unsigned long size, int gfp_mask,
> pgprot_t
> > > prot);
> > > > > extern long vread(char *buf, char *addr, unsigned long count);
> > > > >
> > > > >
> > > > > ___________________________
> > > > > microblaze-uclinux mailing list
> > > > > microblaze-uclinux@itee.uq.edu.au
> > > > > Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-
> > > uclinux
> > > > > Mailing List Archive :
> http://www.itee.uq.edu.au/~listarch/microblaze-
> > > > > uclinux/
> > > > >
> > > > >
> > > > >
> > >
> ________________________________________________________________________
> > > > > This email has been scanned for all viruses by the MessageLabs
> Email
> > > > > Security System. For more information on a proactive email
> security
> > > > > service working around the clock, around the globe, visit
> > > > > http://www.messagelabs.com
> > > > >
> > >
> ________________________________________________________________________
> > > >
> > > >
> > > > ___________________________
> > > > microblaze-uclinux mailing list
> > > > microblaze-uclinux@itee.uq.edu.au
> > > > Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-
> uclinux
> > > > Mailing List Archive :
> http://www.itee.uq.edu.au/~listarch/microblaze-
> > > uclinux/
> > > >
> > > >
> > >
> > > ___________________________
> > > microblaze-uclinux mailing list
> > > microblaze-uclinux@itee.uq.edu.au
> > > Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-
> uclinux
> > > Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-
> > > uclinux/
> > >
> > >
> > >
> ________________________________________________________________________
> > > This email has been scanned for all viruses by the MessageLabs Email
> > > Security System. For more information on a proactive email security
> > > service working around the clock, around the globe, visit
> > > http://www.messagelabs.com
> > >
> ________________________________________________________________________
> >
> >
> > ___________________________
> > microblaze-uclinux mailing list
> > microblaze-uclinux@itee.uq.edu.au
> > Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> > Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-
> uclinux/
> >
> >
>
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@itee.uq.edu.au
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-
> uclinux/
>
>
> ________________________________________________________________________
> This email has been scanned for all viruses by the MessageLabs Email
> Security System. For more information on a proactive email security
> service working around the clock, around the globe, visit
> http://www.messagelabs.com
> ________________________________________________________________________
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/