Problems of the corss-compiler.

Problems of the corss-compiler.

[Seong-kyu Ko]

Hi everyone.
First, I'm sorry for my weak English.

Well, Now I build a powerpc cross-compiler.
so I compiled some binary using that cross-compiler, but
I have some problems.

I think cross-compiler is not problem.
because I compile kernel with that cross-compiler, and
kernel runs good.

but, init, shell etc thease binaries have some problems.
shell cant recieve argument, and some binaries print 'segmentation fault'

I don't know why my compiler can't compile well.

These are the packages that I used.
1. binutils-2.10
2. gcc-2.95.2
3. glibc-2.1.3 (add-ons : glibc-crypt-2.1, glibc-linuxthreads-2.1.3)

First, I compile the binutils for powerpc cpu.
Second, I build cross compiler with gcc.
Third, I compile glibc for powerpc with cross compiler that I made.
Last, I re-build cross compiler include glibc for library.

Please tell me what do you think about that And why the problem happen.
I'll wait your answers.
thank you.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Problems of the corss-compiler.

[Ralph Blach]

[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]

Seong-kyu Ko,

You might want to let us know what platform you are running on?.

I myself am very partial to the montavista tool chain.  It seems rock
Solid
and they have the bash shell and other stuff already compiled.

Chip

Seong-kyu Ko wrote:
>
> Hi everyone.
> First, I'm sorry for my weak English.
>


> Well, Now I build a powerpc cross-compiler.
> so I compiled some binary using that cross-compiler, but
> I have some problems.
>
> I think cross-compiler is not problem.
> because I compile kernel with that cross-compiler, and
> kernel runs good.
>
> but, init, shell etc thease binaries have some problems.
> shell cant recieve argument, and some binaries print 'segmentation fault'
>
> I don't know why my compiler can't compile well.
>
> These are the packages that I used.
> 1. binutils-2.10
> 2. gcc-2.95.2
> 3. glibc-2.1.3 (add-ons : glibc-crypt-2.1, glibc-linuxthreads-2.1.3)
>
> First, I compile the binutils for powerpc cpu.
> Second, I build cross compiler with gcc.
> Third, I compile glibc for powerpc with cross compiler that I made.
> Last, I re-build cross compiler include glibc for library.
>
> Please tell me what do you think about that And why the problem happen.
> I'll wait your answers.
> thank you.
>

[-- Attachment #2: Card for Ralph Blach --]
[-- Type: text/x-vcard, Size: 247 bytes --]

begin:vcard
n:Blach;Ralph
tel;work:919-543-1207
x-mozilla-html:TRUE
url:www.ibm.com
org:IBM MicroElectronics
adr:;;3039 Cornwallis		;RTP;NC;27709;USA
version:2.1
email;internet:rcblach@raleigh.ibm.com
x-mozilla-cpt:;24544
fn:Ralph Blach
end:vcard

Re: Problems of the corss-compiler.

[Cal Erickson]

Seong-kyu,

In the MSR of the PPC processor there is a bit
that indicates whether there is hardware
floating point unit available. This bit should
be set in the state to turn hardware floating
point off when not present. In my experience
even on PowerPC cpus which have hardware
floating point some people do not need or
want to use it. So they make sure that the
MSR is set properly.

That being said, it is important to either make
sure that bit is always set properly or provide
the proper library routines to make sure that
you are getting the desired results. For instance,
the 8xx family of PPC does not have floating point
hardware. So you provide libraries that do
software floating point. The one area where
this comes into play is when using va_args in the
runtime of the C-library. It is typical to save the
registers and the floating point state upon
entry. If the routine does not check the MSR bit
and branch around the floating point state
save code then the system will crash as a
result of the floating point instructions. So the fix
is to eliminate that code from the library and not
depend on the state of the MSR bit. This makes
it necessary to have a special library for the 8xx
family of PPC processors.

Cal

Seong-kyu Ko wrote:

> Hi everyone.
> First, I'm sorry for my weak English.
>
> Well, Now I build a powerpc cross-compiler.
> so I compiled some binary using that cross-compiler, but
> I have some problems.
>
> I think cross-compiler is not problem.
> because I compile kernel with that cross-compiler, and
> kernel runs good.
>
> but, init, shell etc thease binaries have some problems.
> shell cant recieve argument, and some binaries print 'segmentation fault'
>
> I don't know why my compiler can't compile well.
>
> These are the packages that I used.
> 1. binutils-2.10
> 2. gcc-2.95.2
> 3. glibc-2.1.3 (add-ons : glibc-crypt-2.1, glibc-linuxthreads-2.1.3)
>
> First, I compile the binutils for powerpc cpu.
> Second, I build cross compiler with gcc.
> Third, I compile glibc for powerpc with cross compiler that I made.
> Last, I re-build cross compiler include glibc for library.
>
> Please tell me what do you think about that And why the problem happen.
> I'll wait your answers.
> thank you.
>

--
===========================================================================
Cal Erickson                 MontaVista Software Inc.
Customer Support Engineer    490 Potrero Avenue
Phone (408) 328-0304         Sunnyvale CA 94085
Fax   (408) 328-9204         e-mail cal_erickson@mvista.com
Pager 877-566-2012           support 1-800-759-8888 pin 202-7489
web http://www.mvista.com    support e-mail: support@mvista.com
eCode: http://cal@work.com.ecode.com
===========================================================================


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Problems of the corss-compiler.

[Tom Roberts]

Cal Erickson wrote:
> In the MSR of the PPC processor there is a bit
> that indicates whether there is hardware
> floating point unit available.

Beware -- Linux uses the bit to optimize FP-register usage in the
kernel. Basically it starts each process with the bit off, but turns
it on for a process which takes the "FP not avail" trap. The
optimization occurs in context switches where the FP registers are
not saved or restored for processes with this bit off.

This is, of course, for CPUs which have FP units.... IIRC the CPUs
without FP units have the bit hardwired to 0.


Tom Roberts	tjroberts@lucent.com

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

software floating point

[ÁֹαÔ]

I have some questions...about soft-floating point...

I use MPC860, and I made cross develop enviroment.
Host is i386 machine. Target is MPC860.

package that I use
1. binutils-2.10
2. gcc-2.95.2
3. glibc-2.1.3 (add-ons : glibc-crypt-2.1, glibc-linuxthreads-2.1.3)

I did following steps..
First, I compile the binutils for powerpc cpu.
Second, I build cross compiler with gcc.
Third, I compile glibc for powerpc with cross compiler that I made.
Last, I re-build cross compiler include glibc for library.

When compile third step, shoud I use some options to support software floating point?
or shoud I edit some code to support software floating point?

To support software floating point, which steps should I use some special options in above steps and what option is it need?

Thank u for reading my terrible english...^ ^
Take care...


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: software floating point

[Graham Stoney]

=?iso-8859-1?B?wda5zrHU?= writes:
> I have some questions...about soft-floating point...

I suggest you read the section in the HOWTO on the subject, at:
    http://members.xoom.com/greyhams/linux/PowerPC-Embedded-HOWTO-13.html

> When compile third step, shoud I use some options to support software floating point?

You need to configure the compiler to make -msoft-float the default in step 2,
and apply the glibc patch to make it work correctly on the 860 before you do
step 3.

> To support software floating point, which steps should I use some special options in above steps and what option is it need?

The options are mentioned in the HOWTO.

Regards,
Graham
--
Graham Stoney
Principal Hardware/Software Engineer
Canon Information Systems Research Australia
Ph: +61 2 9805 2909  Fax: +61 2 9805 2929

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Problems of the corss-compiler.

[Whitney, John]

Depending on what processor you are using, you may or may not need to
compile the development environment to use software floating-point.  The
860 serial does not have the FPU (at least, none that I know of do), while
the 8260 and 603 series do.

Trying to execute code compiled with hardware floating-point on a processor
without this will result in a crash (floating-point exception, I believe).

Most of the tools compile fairly well for software floating-point, but the
glibc code needs some source modification.

John Whitney
johnw@aiinet.com

-----Original Message-----
From: Seong-kyu Ko [mailto:sugenius@doit.ajou.ac.kr]
Sent: Monday, August 28, 2000 1:18 PM
To: linuxppc-embedded@lists.linuxppc.org
Subject: Problems of the corss-compiler.



Hi everyone.
First, I'm sorry for my weak English.

Well, Now I build a powerpc cross-compiler.
so I compiled some binary using that cross-compiler, but
I have some problems.

I think cross-compiler is not problem.
because I compile kernel with that cross-compiler, and
kernel runs good.

but, init, shell etc thease binaries have some problems.
shell cant recieve argument, and some binaries print 'segmentation fault'

I don't know why my compiler can't compile well.

These are the packages that I used.
1. binutils-2.10
2. gcc-2.95.2
3. glibc-2.1.3 (add-ons : glibc-crypt-2.1, glibc-linuxthreads-2.1.3)

First, I compile the binutils for powerpc cpu.
Second, I build cross compiler with gcc.
Third, I compile glibc for powerpc with cross compiler that I made.
Last, I re-build cross compiler include glibc for library.

Please tell me what do you think about that And why the problem happen.
I'll wait your answers.
thank you.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/