[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Building latest snapshot
- Date: Wed, 25 Aug 1999 17:27:06 +0200
- From: corsepiu at faw.uni-ulm.de (Ralf Corsepius)
- Subject: Building latest snapshot
Peter Shoebridge wrote:
> Has any one experienced this problem building the new snapshot. I'm
> running on cygwin b20 on NT. configure run fine and creates a top
> level makefile and an m68k-rtemself directory with a directory c below
> that. Then running make, it fails trying to run configure in the
> gen68360 directory below the c directory saying: Configuring
> RTEMS_BSP=gen68360
> /bin/sh:
> ../../../rtems-19990820.new/../rtems-19990820.new/c/src/configure: No
> such file or directory The makefile has this code to create and
> configure the bsp: gen68360: src/configure
> @set fnord $(MAKEFLAGS); amf=$$2; \
> test -n "${RTEMS_BSP}" && for i in ${RTEMS_BSP}; do \
> echo "Configuring RTEMS_BSP=$$i"; \
> test -d $$i || mkdir $$i; \
> ( cd $$i && \
> RTEMS_BSP=$$i $(rtems_bsp_configure) \
> && $(MAKE) $(AM_MAKEFLAGS) preinstall ) \
> || case "$$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac;
> \
> doneand it seems as though it doesn't perform the cd $$i before
> trying to run the configure script. It does seem to create the
> directory and if I run it a second time, it complains that there is
> nothing to make for all in gen68360. Sorry for the long email, anyone
> have any ideas? Thanks Peter Oh
I guess this is a consequence of the problem below.
> BTW: I have to fix the following lines in the configure.in file in the
> c directory of the source tree else it didn;t even get this far: old
> code:
> ## Adjust paths
> case $srcdir in
> /*) rtems_bsp_configure="$srcdir/src/configure";;
> *) rtems_bsp_configure="../$srcdir/src/configure";;
> esac new code:
> ## Adjust paths
> case $srcdir in
> *) rtems_bsp_configure="$srcdir/src/configure";;
> /*) rtems_bsp_configure="../$srcdir/src/configure";;
> esac
Nope, the old code is correct. Your proposal breaks Unix path handling.
I guess you are experiencing problems with DOS-Drive-letters in paths.
Hence the correct fix for handling dos-drive-letters is to add
?:*) rtems_bsp_configure="$srcdir/src/configure";;
after the /*)-case in the "old" code.
However, at the moment we use autoconf-2.3, which is affected by the
same problem on M$-derivatives (BTW: a well-know problem with
autoconf), i.e. it is not capable to handle dos drive letters correctly.
Therefore a local fix to RTEMS will not help much.
Furthermore, I guess, both problems mentioned above probably are related
to using absolute paths with drive letters.
You may try to work around related problems by either not using
drive-letters in paths or using relative paths (don't use \\) for srcdir
when configuring. i.e.
../../../../configure --target=xxx-rtems --prefix=D:/rtems
and
/rtems/configure --target=xxx-rtems --prefix=D:/rtems
should work, but
C:/rtems/configure --target=xxx-rtems --prefix=D:/rtems can't work.
Please let me know if this helps.
Ralf
--
Ralf Corsepius
Forschungsinstitut fuer Anwendungsorientierte Wissensverarbeitung (FAW)
Helmholtzstr. 16, 89081 Ulm, Germany Tel: +49/731/501-8690
mailto:corsepiu at faw.uni-ulm.de FAX: +49/731/501-999
http://www.faw.uni-ulm.de