Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.misc > #13990 > unrolled thread

Why does the make have error?

Back to article view | Back to comp.os.linux.misc

Contents

  Why does the make have error? fl <rxjwg98@gmail.com> - 2015-03-09 08:31 -0700
    Re: Why does the make have error? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2015-03-09 17:57 +0200
    Re: Why does the make have error? William Unruh <unruh@invalid.ca> - 2015-03-09 16:40 +0000
    Re: Why does the make have error? Richard Kettlewell <rjk@greenend.org.uk> - 2015-03-09 17:14 +0000
      Re: Why does the make have error? Aragorn <thorongil@telenet.be.invalid> - 2015-03-09 18:28 +0100
        Re: Why does the make have error? Richard Kettlewell <rjk@greenend.org.uk> - 2015-03-09 19:21 +0000
          Re: Why does the make have error? fl <rxjwg98@gmail.com> - 2015-03-09 19:23 -0700
          Re: Why does the make have error? Robert Riches <spamtrap42@jacob21819.net> - 2015-03-10 03:46 +0000
            Re: Why does the make have error? William Unruh <unruh@invalid.ca> - 2015-03-10 04:15 +0000
            Re: Why does the make have error? Richard Kettlewell <rjk@greenend.org.uk> - 2015-03-10 08:48 +0000
            Re: Why does the make have error? Unknown <dog@gmail.com> - 2015-03-16 18:13 +0000

#13990 — Why does the make have error?

Hi,

There is an on-line video tutorial of Sitara SDK 6, which talked about uboot
 build with CCS 5. Now I install Sitara SDK 8 on a Ubuntu PC. I try to build
 uboot after selecting the appropriate the new toolchain in the path in Make
 Target, CCS 6. It has error:

22:02:15 **** Build of configuration Default for project u-boot-2014.07
-g7e537bf ****
make ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- am335x_evm_config 
/bin/sh: 1: uname: not found
/bin/sh: 1: sed: not found
/bin/sh: 1: sed: not found
/bin/sh: 1: uname: not found
/home/ruwan2/ti-sdk-am335x-evm-08.00.00.00/board-support/u-boot-2014.07-
g7e537bf/mkconfig: 1: /home/ruwan2/ti-sdk-am335x-evm-08.00.00.00/board
-support/u-boot-2014.07-g7e537bf/mkconfig: sed: not found
make: *** [am335x_evm_config] Error 127

In the Makefile, I suspect the following lines generates the error:

HOSTARCH := $(shell uname -m | \
    sed -e s/i.86/x86/ \
        -e s/sun4u/sparc64/ \
        -e s/arm.*/arm/ \
        -e s/sa110/arm/ \
        -e s/ppc64/powerpc/ \
        -e s/ppc/powerpc/ \
        -e s/macppc/powerpc/\
        -e s/sh.*/sh/)

HOSTOS := $(shell uname -s | tr '[:upper:]' '[:lower:]' | \
        sed -e 's/\(cygwin\).*/cygwin/')


Especially the last two lines, have all the command names in the error.
Description	Resource	Path	Location	Type
make: *** [am335x_evm_config] Error 127	u-boot-2014.07-g7e537bf	C/C++ 
Problem

 I am still new to Linux. I have check /bin folder. Both sed and uname are
 there. But the following error message has the extra /sh after /bin.

'sh' means shell here? How to make the original command, which is in the
 Makefile, to know these commands are in /bin? It looks like something './'
 in the command line can do, but I don't know how to deal with it for the
 Makefile. 


Thanks,

[toc] | [next] | [standalone]

#13991

On 9.3.15 17:31, fl wrote:
> Hi,
>
> There is an on-line video tutorial of Sitara SDK 6, which talked about uboot
>   build with CCS 5. Now I install Sitara SDK 8 on a Ubuntu PC. I try to build
>   uboot after selecting the appropriate the new toolchain in the path in Make
>   Target, CCS 6. It has error:
>
> 22:02:15 **** Build of configuration Default for project u-boot-2014.07
> -g7e537bf ****
> make ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- am335x_evm_config
> /bin/sh: 1: uname: not found
> /bin/sh: 1: sed: not found
> /bin/sh: 1: sed: not found
> /bin/sh: 1: uname: not found
> /home/ruwan2/ti-sdk-am335x-evm-08.00.00.00/board-support/u-boot-2014.07-
> g7e537bf/mkconfig: 1: /home/ruwan2/ti-sdk-am335x-evm-08.00.00.00/board
> -support/u-boot-2014.07-g7e537bf/mkconfig: sed: not found
> make: *** [am335x_evm_config] Error 127
>
> In the Makefile, I suspect the following lines generates the error:
>
> HOSTARCH := $(shell uname -m | \
>      sed -e s/i.86/x86/ \
>          -e s/sun4u/sparc64/ \
>          -e s/arm.*/arm/ \
>          -e s/sa110/arm/ \
>          -e s/ppc64/powerpc/ \
>          -e s/ppc/powerpc/ \
>          -e s/macppc/powerpc/\
>          -e s/sh.*/sh/)
>
> HOSTOS := $(shell uname -s | tr '[:upper:]' '[:lower:]' | \
>          sed -e 's/\(cygwin\).*/cygwin/')
>
>
> Especially the last two lines, have all the command names in the error.
> Description	Resource	Path	Location	Type
> make: *** [am335x_evm_config] Error 127	u-boot-2014.07-g7e537bf	C/C++
> Problem
>
>   I am still new to Linux. I have check /bin folder. Both sed and uname are
>   there. But the following error message has the extra /sh after /bin.
>
> 'sh' means shell here? How to make the original command, which is in the
>   Makefile, to know these commands are in /bin? It looks like something './'
>   in the command line can do, but I don't know how to deal with it for the
>   Makefile.

Your installation is missing the tools sed and uname, maybe many others 
as well. You could begin by installing the package build-essential from
the Ubuntu repository.

-- 

-TV

[toc] | [prev] | [next] | [standalone]

#13992

On 2015-03-09, fl <rxjwg98@gmail.com> wrote:
> Hi,
>
> There is an on-line video tutorial of Sitara SDK 6, which talked about uboot
>  build with CCS 5. Now I install Sitara SDK 8 on a Ubuntu PC. I try to build
>  uboot after selecting the appropriate the new toolchain in the path in Make
>  Target, CCS 6. It has error:
>
> 22:02:15 **** Build of configuration Default for project u-boot-2014.07
> -g7e537bf ****
> make ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- am335x_evm_config 
> /bin/sh: 1: uname: not found
> /bin/sh: 1: sed: not found
> /bin/sh: 1: sed: not found
> /bin/sh: 1: uname: not found

Well, do you have uname and sed installed on your system?

You seem to be compiling this as user. Try adding to your path
export PATH=$PATH:/bin
before running make.

> /home/ruwan2/ti-sdk-am335x-evm-08.00.00.00/board-support/u-boot-2014.07-
> g7e537bf/mkconfig: 1: /home/ruwan2/ti-sdk-am335x-evm-08.00.00.00/board
> -support/u-boot-2014.07-g7e537bf/mkconfig: sed: not found
> make: *** [am335x_evm_config] Error 127
>
> In the Makefile, I suspect the following lines generates the error:
>
> HOSTARCH := $(shell uname -m | \
>     sed -e s/i.86/x86/ \
>         -e s/sun4u/sparc64/ \
>         -e s/arm.*/arm/ \
>         -e s/sa110/arm/ \
>         -e s/ppc64/powerpc/ \
>         -e s/ppc/powerpc/ \
>         -e s/macppc/powerpc/\
>         -e s/sh.*/sh/)
>
> HOSTOS := $(shell uname -s | tr '[:upper:]' '[:lower:]' | \
>         sed -e 's/\(cygwin\).*/cygwin/')
>
>
> Especially the last two lines, have all the command names in the error.
> Description	Resource	Path	Location	Type
> make: *** [am335x_evm_config] Error 127	u-boot-2014.07-g7e537bf	C/C++ 
> Problem
>
>  I am still new to Linux. I have check /bin folder. Both sed and uname are
>  there. But the following error message has the extra /sh after /bin.
>
> 'sh' means shell here? How to make the original command, which is in the
>  Makefile, to know these commands are in /bin? It looks like something './'
>  in the command line can do, but I don't know how to deal with it for the
>  Makefile. 
>
>
> Thanks,

[toc] | [prev] | [next] | [standalone]

#13993

fl <rxjwg98@gmail.com> writes:

> Hi,
>
> There is an on-line video tutorial of Sitara SDK 6, which talked about uboot
>  build with CCS 5. Now I install Sitara SDK 8 on a Ubuntu PC. I try to build
>  uboot after selecting the appropriate the new toolchain in the path in Make
>  Target, CCS 6. It has error:
>
> 22:02:15 **** Build of configuration Default for project u-boot-2014.07
> -g7e537bf ****
> make ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- am335x_evm_config 
> /bin/sh: 1: uname: not found
> /bin/sh: 1: sed: not found
> /bin/sh: 1: sed: not found
> /bin/sh: 1: uname: not found
> /home/ruwan2/ti-sdk-am335x-evm-08.00.00.00/board-support/u-boot-2014.07-
> g7e537bf/mkconfig: 1: /home/ruwan2/ti-sdk-am335x-evm-08.00.00.00/board
> -support/u-boot-2014.07-g7e537bf/mkconfig: sed: not found
> make: *** [am335x_evm_config] Error 127
>
> In the Makefile, I suspect the following lines generates the error:
>
> HOSTARCH := $(shell uname -m | \
>     sed -e s/i.86/x86/ \
>         -e s/sun4u/sparc64/ \
>         -e s/arm.*/arm/ \
>         -e s/sa110/arm/ \
>         -e s/ppc64/powerpc/ \
>         -e s/ppc/powerpc/ \
>         -e s/macppc/powerpc/\
>         -e s/sh.*/sh/)
>
> HOSTOS := $(shell uname -s | tr '[:upper:]' '[:lower:]' | \
>         sed -e 's/\(cygwin\).*/cygwin/')
>
>
> Especially the last two lines, have all the command names in the error.
> Description	Resource	Path	Location	Type
> make: *** [am335x_evm_config] Error 127	u-boot-2014.07-g7e537bf	C/C++ 
> Problem
>
>  I am still new to Linux. I have check /bin folder. Both sed and uname are
>  there. But the following error message has the extra /sh after /bin.

If sed is present but make can’t find it then /bin must not be on your
path.  Since the default path generally does include it, I would guess
that it’s been changed somehow.

-- 
http://www.greenend.org.uk/rjk/

[toc] | [prev] | [next] | [standalone]

#13994

On Monday 09 March 2015 18:14, Richard Kettlewell conveyed the following 
to comp.os.linux.misc...

> fl <rxjwg98@gmail.com> writes:
> 
>>  I am still new to Linux. I have check /bin folder. Both sed and
>>  uname are there. But the following error message has the extra /sh
>>  after /bin.
> 
> If sed is present but make can’t find it then /bin must not be on your
> path.  Since the default path generally does include it, I would guess
> that it’s been changed somehow.

That, or /bin/sed has somehow been set up with incorrect permissions.

-- 
= Aragorn =

         http://www.linuxcounter.net - registrant #223157

[toc] | [prev] | [next] | [standalone]

#13995

Aragorn <thorongil@telenet.be.invalid> writes:
> Richard Kettlewell conveyed the following to comp.os.linux.misc...
>> fl <rxjwg98@gmail.com> writes:
>> 
>>>  I am still new to Linux. I have check /bin folder. Both sed and
>>>  uname are there. But the following error message has the extra /sh
>>>  after /bin.
>> 
>> If sed is present but make can’t find it then /bin must not be on your
>> path.  Since the default path generally does include it, I would guess
>> that it’s been changed somehow.
>
> That, or /bin/sed has somehow been set up with incorrect permissions.

No; that would yield ‘Permission denied’, not ‘not found’.

-- 
http://www.greenend.org.uk/rjk/

[toc] | [prev] | [next] | [standalone]

#13998

On Monday, March 9, 2015 at 12:21:11 PM UTC-7, Richard Kettlewell wrote:
> Aragorn <thorongil@telenet.be.invalid> writes:
> > Richard Kettlewell conveyed the following to comp.os.linux.misc...
> >> fl <rxjwg98@gmail.com> writes:
> >> 
> >>>  I am still new to Linux. I have check /bin folder. Both sed and
> >>>  uname are there. But the following error message has the extra /sh
> >>>  after /bin.
> >> 
> >> If sed is present but make can't find it then /bin must not be on your
> >> path.  Since the default path generally does include it, I would guess
> >> that it's been changed somehow.
> >
> > That, or /bin/sed has somehow been set up with incorrect permissions.
> 
> No; that would yield 'Permission denied', not 'not found'.
> 
> -- 
> http://www.greenend.org.uk/rjk/




Thanks.

Somebody asks me the question. I have the answer also list here.
Hopefully you can help me.

Aspire-M5100:~$ ls -al /bin/sh
lrwxrwxrwx 1 root root 4 Mar 4 21:03 /bin/sh -> dash

[toc] | [prev] | [next] | [standalone]

#13999

On 2015-03-09, Richard Kettlewell <rjk@greenend.org.uk> wrote:
> Aragorn <thorongil@telenet.be.invalid> writes:
>> Richard Kettlewell conveyed the following to comp.os.linux.misc...
>>> fl <rxjwg98@gmail.com> writes:
>>> 
>>>>  I am still new to Linux. I have check /bin folder. Both sed and
>>>>  uname are there. But the following error message has the extra /sh
>>>>  after /bin.
>>> 
>>> If sed is present but make can???t find it then /bin must not be on your
>>> path.  Since the default path generally does include it, I would guess
>>> that it???s been changed somehow.
>>
>> That, or /bin/sed has somehow been set up with incorrect permissions.
>
> No; that would yield ???Permission denied???, not ???not found???.

If the shell (or perhaps make) is using $PATH to find
executables, and if /bin/sed should be executable but is not,
then wouldn't the shell (or perhaps make) report that it could
not find an executable 'sed' in $PATH?

-- 
Robert Riches
spamtrap42@jacob21819.net
(Yes, that is one of my email addresses.)

[toc] | [prev] | [next] | [standalone]

#14000

On 2015-03-10, Robert Riches <spamtrap42@jacob21819.net> wrote:
> On 2015-03-09, Richard Kettlewell <rjk@greenend.org.uk> wrote:
>> Aragorn <thorongil@telenet.be.invalid> writes:
>>> Richard Kettlewell conveyed the following to comp.os.linux.misc...
>>>> fl <rxjwg98@gmail.com> writes:
>>>> 
>>>>>  I am still new to Linux. I have check /bin folder. Both sed and
>>>>>  uname are there. But the following error message has the extra /sh
>>>>>  after /bin.
>>>> 
>>>> If sed is present but make can???t find it then /bin must not be on your
>>>> path.  Since the default path generally does include it, I would guess
>>>> that it???s been changed somehow.
>>>
>>> That, or /bin/sed has somehow been set up with incorrect permissions.
>>
>> No; that would yield ???Permission denied???, not ???not found???.
>
> If the shell (or perhaps make) is using $PATH to find
> executables, and if /bin/sed should be executable but is not,
> then wouldn't the shell (or perhaps make) report that it could
> not find an executable 'sed' in $PATH?
>

wormhole:0[unruh]>touch t
wormhole:0[unruh]>./t
bash: ./t: Permission denied

Nope. It will find sed and find that its permissions do not allow
execution.

[toc] | [prev] | [next] | [standalone]

#14001

Robert Riches <spamtrap42@jacob21819.net> writes:
> Richard Kettlewell <rjk@greenend.org.uk> wrote:
>> Aragorn <thorongil@telenet.be.invalid> writes:
>>> Richard Kettlewell conveyed the following to comp.os.linux.misc...
>>>> If sed is present but make can’t find it then /bin must not be on
>>>> your path.  Since the default path generally does include it, I
>>>> would guess that it’s been changed somehow.
>>>
>>> That, or /bin/sed has somehow been set up with incorrect permissions.
>>
>> No; that would yield ‘Permission denied’, not ‘not found’.
>
> If the shell (or perhaps make) is using $PATH to find
> executables, and if /bin/sed should be executable but is not,
> then wouldn't the shell (or perhaps make) report that it could
> not find an executable 'sed' in $PATH?

No, it would not.

     $ ls -l /bin/sed.not.really
     -rw-r--r-- 1 root root 69096 Mar 10 08:39 /bin/sed.not.really
     $ dash -c sed.not.really
     dash: 1: sed.not.really: Permission denied
     $ bash -c sed.not.really
     bash: /bin/sed.not.really: Permission denied

(...and make invokes commands via the shell, as you can tell from the
message at the start of the thread.)

-- 
http://www.greenend.org.uk/rjk/

[toc] | [prev] | [next] | [standalone]

#14100

On Tue, 10 Mar 2015 03:46:32 +0000, Robert Riches wrote:

> On 2015-03-09, Richard Kettlewell <rjk@greenend.org.uk> wrote:
>> Aragorn <thorongil@telenet.be.invalid> writes:
>>> Richard Kettlewell conveyed the following to comp.os.linux.misc...
>>>> fl <rxjwg98@gmail.com> writes:
>>>> 
>>>>>  I am still new to Linux. I have check /bin folder. Both sed and
>>>>>  uname are there. But the following error message has the extra /sh
>>>>>  after /bin.
>>>> 
>>>> If sed is present but make can???t find it then /bin must not be on
>>>> your path.  Since the default path generally does include it, I would
>>>> guess that it???s been changed somehow.
>>>
>>> That, or /bin/sed has somehow been set up with incorrect permissions.
>>
>> No; that would yield ???Permission denied???, not ???not found???.
> 
> If the shell (or perhaps make) is using $PATH to find executables, and
> if /bin/sed should be executable but is not, then wouldn't the shell (or
> perhaps make) report that it could not find an executable 'sed' in
> $PATH?

See what's there by:
which sed
ls -l `which sed`
whoami

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.misc

csiph-web