This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Trying to get crosstool-0.43 to work on Solaris 9


David Kahn wrote:


My fix was to not hardcode sh, and use the
env variable $SHELL in the crosstool scripts.
On Solaris, I had success with ksh as you did.
Actually, I think I defined the variable CONFIG_SHELL
in my version of the crosstool scripts, and
defined it in the config file.

That sounds like the right answer.

Patch attached.

I'm loosing my mind. These are the other two patches that go along with that one.

The mkoverride thing is because that also breaks
at the very end of a successful build on Solaris9 ...
Something weird with an 'install' command at
the end of the entire thing that isn't really
needed, and after a few attempts at trying to
make it work, I gave up and just deleted it,
since it isn't needed.


From Alex


Great. What was the answer?

Dan said he would pick them up. I reminded him when he sent out his recent mail about doing the next version. (maybe a week or two ago.)

One annoyance - if the script breaks, I re-run it. It'll then
remove the gcc, ... directories and recreate them. That's taking
"some" time. Can I somehow make crosstool skip this step?

Maybe, but the only way to do it right is with a complete clean run. It didn't bother me that much to start over every time. I think there's a way to not do that, but the individual component makefiles may not necessarily behave. (They usually do.)

Are you also building glibc? There's a couple more patches
you may need if you are. Search for my old posts to find them.

-David


--- all.sh.old	Tue Jun 27 16:05:14 2006
+++ all.sh	Wed Jun 28 04:40:53 2006
@@ -120,7 +120,7 @@
    	rm -rf $BUILD_DIR.del.$$ &
    fi
    mkdir -p $BUILD_DIR
-   sh getandpatch.sh
+   ${CONFIG_SHELL-sh} getandpatch.sh
 fi
 
 if test "$opt_no_build" = ""; then
@@ -134,23 +134,23 @@
     mkdir -p $BUILD_DIR
     cd $BUILD_DIR
     if test "${CYGWIN_DIR}" = ""; then
-        sh $TOP_DIR/crosstool.sh
+        ${CONFIG_SHELL-sh} $TOP_DIR/crosstool.sh
     else
-        sh ${TOP_DIR}/crosstool-cygwin.sh
+        ${CONFIG_SHELL-sh} ${TOP_DIR}/crosstool-cygwin.sh
     fi
     cd $TOP_DIR
 
-    sh testhello.sh
+    ${CONFIG_SHELL-sh} testhello.sh
 fi
 if test "$opt_gdb" = "1"; then
     # Build a debugger
     # kludge: don't abort if it doesn't build; we want to know if the kernel builds, too
-    sh gdb.sh || test "$opt_testlinux" = "1"
+    ${CONFIG_SHELL-sh} gdb.sh || test "$opt_testlinux" = "1"
 fi
 
 if test "$opt_testlinux" = "1"; then
     # Build a Linux kernel to see if we can
-    sh testlinux.sh
+    ${CONFIG_SHELL-sh} testlinux.sh
 fi
 
 if test "$opt_builduserland" = "1"; then
@@ -157,11 +157,11 @@
     # Build /bin/sh and any other non-toolchain things configured in ptx.config
     # Only needed if you can't run the target's normal /bin/sh with the new toolchain
     cd $BUILD_DIR
-    sh $TOP_DIR/ptx.sh
+    ${CONFIG_SHELL-sh} $TOP_DIR/ptx.sh
 fi
 
 if test "$opt_no_test" = ""; then
     # Beefy test that lasts for hours
     cd $BUILD_DIR
-    sh $TOP_DIR/crosstest.sh 
+    ${CONFIG_SHELL-sh} $TOP_DIR/crosstest.sh 
 fi
--- mkoverride.sh.old	Mon Mar  7 16:34:34 2005
+++ mkoverride.sh	Tue Jun 27 17:46:44 2006
@@ -57,5 +57,5 @@
 done
 
 # Oh, what the heck, also install the script :-)
-install -D -m755 install-shared-lib.sh $PREFIX/libexec/install-shared-lib.sh
+#${INSTALL-install} -D -m755 install-shared-lib.sh $PREFIX/libexec/install-shared-lib.sh
 

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]