From: "Kyle Unice" <unixe@comcast.net>
To: "'Ilya A. Volynets-Evenbakh'" <ilya@total-knowledge.com>,
"'David Daney'" <ddaney@avtrex.com>
Cc: <ppopov@embeddedalley.com>,
"'Brett Foster'" <fosterb@uoguelph.ca>,
<linux-mips@linux-mips.org>
Subject: RE: Cross-compiling Linux problem
Date: Sat, 8 Oct 2005 07:52:24 -0600 [thread overview]
Message-ID: <003c01c5cc0f$83a19e30$0400a8c0@buzz> (raw)
In-Reply-To: <4346FD34.8000100@total-knowledge.com>
It appears that the function __fixup_bigphys_addr is not inline anymore but
A callable function. I removed the "inline " qualifier from the extern
declaration in
Ioremap.h (if CONFIG_64BIT_PHYS_ADDR is declared) and linux built ok.
Kyle
-----Original Message-----
From: Ilya A. Volynets-Evenbakh [mailto:ilya@total-knowledge.com]
Sent: Friday, October 07, 2005 4:57 PM
To: David Daney
Cc: Kyle Unice; ppopov@embeddedalley.com; 'Brett Foster';
linux-mips@linux-mips.org
Subject: Re: Cross-compiling Linux problem
CVS is not where development happens, but it is still updated, according
to Ralf.
David Daney wrote:
> Kyle Unice wrote:
>
>> I am using gcc-3.4.4 and the cvs checkout of linux-mips.org tree.
>> Kyle
>
>
> Not withstanding Maciej's comment about the real problem being the
> broken header file, I give you a quote from
> http://www.linux-mips.org/wiki/Git : "At this time only the linux.git
> repository is in production use.... all other archives are only
> historical."
>
> You might consider getting your code from the git repository as the
> CVS repository is no longer being maintained.
>
> David Daney
>
>
--
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com
WARNING: multiple messages have this Message-ID (diff)
From: "Kyle Unice" <unixe@comcast.net>
To: "'Ilya A. Volynets-Evenbakh'" <ilya@total-knowledge.com>,
'David Daney' <ddaney@avtrex.com>
Cc: ppopov@embeddedalley.com, 'Brett Foster' <fosterb@uoguelph.ca>,
linux-mips@linux-mips.org
Subject: RE: Cross-compiling Linux problem
Date: Sat, 8 Oct 2005 07:52:24 -0600 [thread overview]
Message-ID: <003c01c5cc0f$83a19e30$0400a8c0@buzz> (raw)
Message-ID: <20051008135224.x2F2D3jaPAwUot3frRmnw4LF2Q-Ul6GugPiuzpKUeiU@z> (raw)
In-Reply-To: <4346FD34.8000100@total-knowledge.com>
It appears that the function __fixup_bigphys_addr is not inline anymore but
A callable function. I removed the "inline " qualifier from the extern
declaration in
Ioremap.h (if CONFIG_64BIT_PHYS_ADDR is declared) and linux built ok.
Kyle
-----Original Message-----
From: Ilya A. Volynets-Evenbakh [mailto:ilya@total-knowledge.com]
Sent: Friday, October 07, 2005 4:57 PM
To: David Daney
Cc: Kyle Unice; ppopov@embeddedalley.com; 'Brett Foster';
linux-mips@linux-mips.org
Subject: Re: Cross-compiling Linux problem
CVS is not where development happens, but it is still updated, according
to Ralf.
David Daney wrote:
> Kyle Unice wrote:
>
>> I am using gcc-3.4.4 and the cvs checkout of linux-mips.org tree.
>> Kyle
>
>
> Not withstanding Maciej's comment about the real problem being the
> broken header file, I give you a quote from
> http://www.linux-mips.org/wiki/Git : "At this time only the linux.git
> repository is in production use.... all other archives are only
> historical."
>
> You might consider getting your code from the git repository as the
> CVS repository is no longer being maintained.
>
> David Daney
>
>
--
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com
next prev parent reply other threads:[~2005-10-08 13:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 20:18 Cross-compiling Linux problem Kyle Unice
2005-10-07 20:18 ` Kyle Unice
2005-10-07 20:41 ` Brett Foster
2005-10-07 20:54 ` Maciej W. Rozycki
2005-10-07 21:26 ` Kyle Unice
2005-10-07 21:26 ` Kyle Unice
2005-10-07 21:47 ` Pete Popov
2005-10-07 21:54 ` Kyle Unice
2005-10-07 21:54 ` Kyle Unice
2005-10-07 22:27 ` David Daney
2005-10-07 22:56 ` Ilya A. Volynets-Evenbakh
2005-10-07 23:15 ` David Daney
2005-10-08 13:52 ` Kyle Unice [this message]
2005-10-08 13:52 ` Kyle Unice
2005-10-13 11:58 ` Ralf Baechle
2005-10-13 12:07 ` Ralf Baechle
2005-10-08 3:33 ` Kyle Unice
2005-10-08 3:33 ` Kyle Unice
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='003c01c5cc0f$83a19e30$0400a8c0@buzz' \
--to=unixe@comcast.net \
--cc=ddaney@avtrex.com \
--cc=fosterb@uoguelph.ca \
--cc=ilya@total-knowledge.com \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@embeddedalley.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.