./configure problem

William_Sundberg · 27 January 2004 16:26

uname -a
Linux localhost.localdomain 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002
i686 i686 i386 GNU/Linux

···

from /var/log/boot.log
OS Kernel: Linux version 2.4.18-14
(bhcompile@stripples.devel.redhat.com) (gcc version 3.2 20020903 (Red
Hat Linux 8.0 3.2-7))

I am running RedHat 9.0 on my laptop Pentium II
And I have the following problem when I try to install ruby 1.8.1.

./configure
checking build system type… Invalid configuration
i686-pc-linux-oldld': machinei686-pc-linux’ not recognized
configure: error: /bin/sh ./config.sub i686-pc-linux-oldld failed

Yukihiro_Matsumoto2 · 27 January 2004 17:00

Hi,

I am running RedHat 9.0 on my laptop Pentium II
And I have the following problem when I try to install ruby 1.8.1.

./configure
checking build system type… Invalid configuration
i686-pc-linux-oldld': machine i686-pc-linux’ not recognized
configure: error: /bin/sh ./config.sub i686-pc-linux-oldld failed

Try this patch.

						matz.

— config.sub 10 Apr 2003 08:37:12 -0000 1.15
+++ config.sub 27 Jan 2004 16:59:45 -0000
@@ -120,3 +120,3 @@ maybe_os=`echo $1 | sed 's/^(.*)-([^-
case $maybe_os in

nto-qnx* | linux-gnu* | freebsd*-gnu* | netbsd*-gnu* | storm-chaos* | os2-emx* | rtmk-nova*)

nto-qnx* | linux-* | freebsd*-gnu* | netbsd*-gnu* | storm-chaos* | os2-emx* | rtmk-nova*)
os=-$maybe_os

···

In message “./configure problem” on 04/01/28, William Sundberg william@m4trade.com writes:

William_Sundberg · 27 January 2004 19:02

Thank you for your reply but how do you “try this patch”? Should I add
this lines in config.sub if so where?

Best regards/William

···

On Tue, 2004-01-27 at 18:00, Yukihiro Matsumoto wrote:

Hi,

In message “./configure problem” > on 04/01/28, William Sundberg william@m4trade.com writes:

I am running RedHat 9.0 on my laptop Pentium II
And I have the following problem when I try to install ruby 1.8.1.

./configure
checking build system type… Invalid configuration
i686-pc-linux-oldld': machine i686-pc-linux’ not recognized
configure: error: /bin/sh ./config.sub i686-pc-linux-oldld failed

Try this patch.
  					matz.
— config.sub 10 Apr 2003 08:37:12 -0000 1.15
+++ config.sub 27 Jan 2004 16:59:45 -0000
@@ -120,3 +120,3 @@ maybe_os=`echo $1 | sed 's/^(.*)-([^-
case $maybe_os in

nto-qnx* | linux-gnu* | freebsd*-gnu* | netbsd*-gnu* | storm-chaos* | os2-emx* | rtmk-nova*)

nto-qnx* | linux-* | freebsd*-gnu* | netbsd*-gnu* | storm-chaos* | os2-emx* | rtmk-nova*)
os=-$maybe_os

Daniel_Kelley8 · 28 January 2004 01:54

matz@ruby-lang.org (Yukihiro Matsumoto) writes:

Hi,

I am running RedHat 9.0 on my laptop Pentium II
And I have the following problem when I try to install ruby 1.8.1.

./configure
checking build system type… Invalid configuration
i686-pc-linux-oldld': machine i686-pc-linux’ not recognized
configure: error: /bin/sh ./config.sub i686-pc-linux-oldld failed

I get exactly this error if the gcc packages are not installed - fresh
minimal install (Fedora core/1), and ruby is the first thing I
compile!

You should be able to type from the prompt:

1097>gcc
gcc: no input files

···

In message “./configure problem” > on 04/01/28, William Sundberg william@m4trade.com writes:

–
Daniel Kelley - San Jose, CA For email, replace the first dot in the
domain with an at.

Benny · 27 January 2004 19:19

usually you can patch a patch with

patch < patch.file

just make sure that the filenames in the patch file (e.g. config.sub) can be found

benny

···

Am Wed, 28 Jan 2004 04:02:16 +0900 schrieb William Sundberg william@m4trade.com:

Thank you for your reply but how do you “try this patch”? Should I add
this lines in config.sub if so where?

William_Sundberg · 27 January 2004 19:43

Thank you again, now I feel even more stupid. I tried with this. Cut out
the text from the first mail(the patch) and put it in a “file”.
-----------file: patch_m
@@ -120,3 +120,3 @@ maybe_os=`echo $1 | sed 's/^(.*)-([^-
case $maybe_os in

nto-qnx* | linux-gnu* | freebsd*-gnu* | netbsd*-gnu* | storm-chaos* |
os2-emx* | rtmk-nova*)

nto-qnx* | linux-* | freebsd*-gnu* | netbsd*-gnu* | storm-chaos* |
os2-emx* | rtmk-nova*)
os=-$maybe_os

···

Then I tried the following without luck:
[william@localhost ruby-1.8.1]$ config.sub < patch_m
bash: config.sub: command not found
[william@localhost ruby-1.8.1]$ patch_m < config.sub
bash: patch_m: command not found
[william@localhost ruby-1.8.1]$ chmod +x patch_m
[william@localhost ruby-1.8.1]$ patch_m < config.sub
bash: patch_m: command not found

What am I missing?

On Tue, 2004-01-27 at 20:19, benny wrote:

Am Wed, 28 Jan 2004 04:02:16 +0900 > schrieb William Sundberg william@m4trade.com:

Thank you for your reply but how do you “try this patch”? Should I add
this lines in config.sub if so where?

usually you can patch a patch with

patch < patch.file

just make sure that the filenames in the patch file (e.g. config.sub) can be found

benny

William_Sundberg · 27 January 2004 19:51

Sorry my fault, “patch” is a script/pgm I shuld have looked in the old
arcives.

Thank you/William

···

On Tue, 2004-01-27 at 20:43, William Sundberg wrote:

Thank you again, now I feel even more stupid. I tried with this. Cut out
the text from the first mail(the patch) and put it in a “file”.
-----------file: patch_m
@@ -120,3 +120,3 @@ maybe_os=`echo $1 | sed 's/^(.*)-([^-
case $maybe_os in

nto-qnx* | linux-gnu* | freebsd*-gnu* | netbsd*-gnu* | storm-chaos* |
os2-emx* | rtmk-nova*)

nto-qnx* | linux-* | freebsd*-gnu* | netbsd*-gnu* | storm-chaos* |
os2-emx* | rtmk-nova*)
os=-$maybe_os

Then I tried the following without luck:
[william@localhost ruby-1.8.1]$ config.sub < patch_m
bash: config.sub: command not found
[william@localhost ruby-1.8.1]$ patch_m < config.sub
bash: patch_m: command not found
[william@localhost ruby-1.8.1]$ chmod +x patch_m
[william@localhost ruby-1.8.1]$ patch_m < config.sub
bash: patch_m: command not found

What am I missing?

On Tue, 2004-01-27 at 20:19, benny wrote:

Am Wed, 28 Jan 2004 04:02:16 +0900 > > schrieb William Sundberg william@m4trade.com:

Thank you for your reply but how do you “try this patch”? Should I add
this lines in config.sub if so where?

usually you can patch a patch with

patch < patch.file

just make sure that the filenames in the patch file (e.g. config.sub) can be found

benny

Benny · 27 January 2004 19:54

What am I missing?

Thank you for your reply but how do you “try this patch”? Should I add
this lines in config.sub if so where?

usually you can patch a patch with

patch < patch.file

just make sure that the filenames in the patch file (e.g. config.sub) can be found

benny

ok, even more detailed:

“patch” is the name of the program you use to change the files and “patch.file” was the name I took
as placeholder for the file with the patch in it.

so do the following:

copy the text in a file and save it under the name “mypatch” in the directory where the
file config.sub lies
login in a shell and use the command ‘cd’ to go into that directory
enter the command
```
 patch < mypatch
```

in the shell

read the man page:

man patch
feel happy

cheers,

benny

···

On Tue, 2004-01-27 at 20:19, benny wrote:

Am Wed, 28 Jan 2004 04:02:16 +0900 > > schrieb William Sundberg william@m4trade.com:

Topic		Replies	Views
Compiling 1.8.0 Preview ruby-talk	1	111	13 February 2003
Problem Configuring Ruby Source in Linux ruby-talk	4	101	1 March 2007
Build suite: “configure: error: cannot run /bin/sh tool/config.sub” ruby-talk	2	1476	1 June 2020
1.9.3 fails to install via rvm on OS X Lion ruby-talk	4	142	28 November 2011
URGENT: Ruby 1.8 in IBM PowerPC ruby-talk	3	89	25 July 2003

./configure problem

from /var/log/boot.log OS Kernel: Linux version 2.4.18-14 (bhcompile@stripples.devel.redhat.com) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7))

Related Topics

from /var/log/boot.log
OS Kernel: Linux version 2.4.18-14
(bhcompile@stripples.devel.redhat.com) (gcc version 3.2 20020903 (Red
Hat Linux 8.0 3.2-7))