MPC8260ADS and Linux

Fri Apr 26 15:57:49 UTC 2002

Currently not working as expected is "./bit_rtems powerpc"

The end of the output is:
---------------------------------------
configuring in powerpc-rtems/c
running /bin/sh ../../../rtems-4.5.0/c/configure  --target=powerpc-rtems
--prefix=/home/rtems --disable-hwapi --disable-multiprocessing --enable-cxx
--enable-rdbg --disable-tests --enable-networking --enable-posix
--enable-itron --cache-file=./config.cache --srcdir=../../../rtems-4.5.0/c
creating cache ./config.cache
checking for RTEMS Version... 4.5.0
checking host system type... i386-unknown-netbsd1.5.2
checking target system type... powerpc-unknown-rtems
checking build system type... i386-unknown-netbsd1.5.2
checking rtems target cpu... powerpc
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking whether to enable maintainer-specific portions of Makefiles... no
checking if cpu powerpc is supported... yes
checking for bsps...  .cvsignore dmv177 eth_comm helas403 mvme2307 mcp750
papyrus ppcn_60x psim score603e .. done
checking for make/custom/.cvsignore.cfg... configure: error: no
configure: error: ../../../rtems-4.5.0/c/configure failed for c
Could not successfully configure into build-powerpc-rtems!

My directories look like the following after attempting to build
rtems-4.5.0
---------------------------------------------------------------------------

drwxr-xr-x  14 grunza  hardware  1024 Jan 13  2000 binutils-2.9.5.0.24
-rwxr-xr-x   1 grunza  hardware  6064 Jul 10  2000 bit
-rwxr-xr-x   1 grunza  hardware  4828 Jan  4  2000 bit_gdb
-rwxr-xr-x   1 grunza  hardware  8477 Jun 12  2000 bit_rtems
drwxr-xr-x   6 root    hardware   512 Apr 26 11:47 build-powerpc-rtems
-rwxr-xr-x   1 grunza  hardware  6558 Feb 11  2000 common.sh
drwxr-xr-x  16 grunza  hardware  1024 Apr 26 10:28 gcc-2.95.2
drwxr-xr-x  15 grunza  hardware  1024 Apr 26 10:58 gdb-4.18
drwxr-xr-x   7 grunza  hardware  1024 Nov 20  1999 newlib-1.8.2
drwxr-xr-x  10 grunza  hardware  1024 Jul 24  2000 rtems-4.5.0
-rw-r--r--   1 grunza  hardware  3066 Apr 26 11:38 user.cfg

My user.cfg is attached to this message.

My system is:

toor at pc-grunza-p 94% uname -a
NetBSD pc-grunza-p 1.5.2 NetBSD 1.5.2 (JAGUAR) #2: Tue Apr  9 11:05:01 EDT
2002     root at pc-grunza-p:/usr/src/sys/arch/i386/compile/JAGUAR i386

grunza at pc-grunza-p 178% make --version
GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.
Built for i386--netbsd
Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 2000
        Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

Report bugs to <bug-make at gnu.org>.

grunza at pc-grunza-p 179% sed --version
GNU sed version 3.02

Copyright (C) 1998 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE,

to the extent permitted by law.
grunza at pc-grunza-p 180% powerpc-rtems-gcc --version
2.95.2

NOTE:  I'm running as root for the ./bit scripts so the installation can
occur

Sorry for the long post...

Ralf Corsepius wrote:

> Am Fre, 2002-04-26 um 16.21 schrieb Mike Siers:
> >
> > Hi Joel,
> > Sorry for the confusion.  Here is the quick and dirty recipe:
> >
> > 1) Install OpenBSD
> > 2) Install the following packages or ports:
> >      - gettext
> >      - gmake
> >      - autoconf
> >      - automake
> >      - libtool
> >      - m4
> gettext and libtool are not required by RTEMS nor by any of the tools
> involved into RTEMS.
>
> > 3) Get and build GNU sed source (installs to /usr/local/bin)
> gm4 and gsed may be necessary on some platforms, because the native ones
> shipped on some systems are too limited or broken for use with autoconf.
>
> > 4) Get and build GNU patch source (installs to /usr/local/bin)
> I have no idea why you need this, may-be the native patch is not able to
> handle unified context diffs.
>
> > 5) Make symbolic link from /usr/local/bin/gmake to /usr/local/bin/make
> > 6) Make symbolic link from /usr/local/bin/gm4   to /usr/local/bin/m4
> > 7) Modify path to have /usr/local/bin before other directories
> In addition to this, you will need a sufficiently good shell for RTEMS
> and for the autotools, because some shells on some systems are known to
> be severly broken and the auto*tools not having yet been adapted to
> these shells' deficiencies
> (Known to be problematic at present time: Newer systems using zsh-3.0.x
> and ash as default shells)
>
> Ralf

--
"Luke, you're going to find that many | Steven Grunza
of the truths we cling to depend      | voice:  (856) 787 - 2759
greatly on our own point of view."    | fax:    (856) 866 - 2033
 - Obi Wan Kenobi, Return of the Jedi | e-mail: steven_grunza at ieee.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: user.cfg
Type: application/x-ns-proxy-autoconfig
Size: 3066 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20020426/b49d7fb6/attachment.bin>