lkcd
[Top] [All Lists]

Re: Alpha lcrash compile problems

To: Matt Robinson <yakker@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: Alpha lcrash compile problems
From: Brian Hall <brianw.hall@xxxxxxxxxx>
Date: Tue, 15 Feb 2000 12:37:18 -0700 (MST)
Cc: lkcd@xxxxxxxxxxx
In-reply-to: <Pine.SGI.3.94.1000215093001.100716A-100000@xxxxxxxxxxxxxxxxxxxx>
Reply-to: Brian Hall <brianw.hall@xxxxxxxxxx>
Sender: owner-lkcd@xxxxxxxxxxx
Everything here is blocked by the firewall, so I can't get you a login to the
AS200 I've been working on. However, you can get access to an Alpha running
Linux at the below URL. I created an account for myself, but I can't telnet to
the machine because I'm blocked by the firewall! (I'm inside the firewall)

http://www.testdrive.compaq.com/register.shtml

On 15-Feb-2000 Matt Robinson wrote:
> The cmd/lcrash/lib/libklib/include/asm/kl_kernel.h should really be
> based on cmd/lcrash/lib/libklib/include/asm-alpha/kl_kernel.h.  You
> may need to make modifications to those files in order to get it to
> compile correctly.  That file has been setup to deal with header file
> inconsistencies.
> 
> For example, in your case, it's doing a #include <linux/mm.h>, which
> eventually does a #include <asm/current.h>, and from there, it doesn't
> compile correctly, because the global register variable isn't allowed.
> 
> Just purely speculating (if I had an Alpha system, I could probably
> work on it ... do you have a login? :D), you might want to check your
> $(CFLAGS) and make sure one of the standard flags is being used to
> compile for alpha platforms ... also, make sure to look at any files
> that #include <linux/mm.h> in arch/alpha/kernel and see what header
> files may also be needed (the ones that preclude the #include <linux/mm.h>
> definition).  Finally, remove #include <linux/mm.h>, and find out what
> happens.
> 
> My first guess is it is the $(CFLAGS), but without having a system, I
> can't know for sure.
> 
> --Matt
> 
> On Tue, 15 Feb 2000, Brian Hall wrote:
>|>Working on porting lcrash over to Alpha, I've hit a roadblock. To get
>|>started,
>|>I simply copied all lcrash/*/arch/i386 over to lcrash/*/arch/alpha, knowing
>|>that
>|>it would require modification. Problem is, I can't get anywhere trying to
>|>build
>|>it for Alpha. Since there is no fixmap.h for Alpha, I removed the reference
>|>to
>|>that include. Now I get a include problem I have not been able to resolve.
>|>I've
>|>tried building the whole kernel, and the problem also occurs with almost the
>|>exact same errors just building lib/libklib.
>|>
>|>(cd include ; /bin/ln -s asm-alpha asm; cd ..)
>|>cc -gstabs -D__KERNEL__ -I/usr/src/linux/include -I. -Iinclude   -c -o
>|>klib.o
>|>klib.c
>|>In file included from /usr/src/linux/include/asm/semaphore.h:11,
>|>                 from /usr/src/linux/include/linux/fs.h:164,
>|>                 from /usr/src/linux/include/linux/capability.h:13,
>|>                 from /usr/src/linux/include/linux/binfmts.h:5,
>|>                 from /usr/src/linux/include/linux/sched.h:8,
>|>                 from /usr/src/linux/include/linux/mm.h:4,
>|>                 from include/asm/kl_kernel.h:10,
>|>                 from include/klib.h:12,
>|>                 from klib.c:4:
>|>/usr/src/linux/include/asm/current.h:4: global register variable follows a
>|>function definition
>|>/usr/src/linux/include/asm/current.h:4: warning: call-clobbered register
>|>used
>|>for global register variable
>|>
>|>This makes it look like the problem is in current.h, but it can't be;
>|>current.h
>|>is happy with the rest of the Alpha tree. How do I resolve this apparent
>|>conflict with the lcrash source?

--
Brian Hall <brianw.hall@xxxxxxxxxx>
http://www.bigfoot.com/~brihall
Linux Consultant

<Prev in Thread] Current Thread [Next in Thread>