problem with ct-ng 1.5.1: "fragment: command not found"

View: New views
5 Messages — Rating Filter:   Alert me  

problem with ct-ng 1.5.1: "fragment: command not found"

by Matthias Kaehlcke-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

hi,

the build of a uclibc toolchain for i686 using crosstool-ng v1.5.1
fails with the following error:

[ALL  ]    LIB_PATH='' /bin/bash /usr/local/src/ct-ng-build/targets/src/binutils-2.18/ld/genscripts.sh "/usr/local/src/ct-ng-build/targets/src/binutils-2.18/ld" "/home/matze/i386-unknown-linux-uclibc/lib" "/home/matze/i386-unknown-linux-uclibc" "/home/matze/i386-unknown-linux-uclibc" i486-build_pc-linux-gnu i386-unknown-linux-uclibc i386-unknown-linux-uclibc "elf_i386" "/usr/local/lib /lib /usr/lib" yes elf_i386 "i386-unknown-linux-uclibc"
[ALL  ]
/usr/local/src/ct-ng-build/targets/src/binutils-2.18/ld/emultempl/elf32.em: line 11: fragment: command not found
... (more lines with the same error)

the offending lines look like this one:

fragment <<EOF
/* This file is is generated by a shell script.  DO NOT EDIT! */
...
EOF

anyone ran into this issue and knows how to solve it?

best regards

--
Matthias Kaehlcke
Embedded Linux Engineer
Barcelona

     La guerra es un acto abominable en el que se matan personas que no
      se conocen, dirigidas por personas que se conocen y no se matan
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-

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


Re: problem with ct-ng 1.5.1: "fragment: command not found"

by Yann E. MORIN :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello Matthias!
Hello All!

On Thursday 29 October 2009 21:24:42 Matthias Kaehlcke wrote:
> the build of a uclibc toolchain for i686 using crosstool-ng v1.5.1
> fails with the following error:
> [ALL  ]
> /usr/local/src/ct-ng-build/targets/src/binutils-2.18/ld/emultempl/elf32.em:
> line 11: fragment: command not found
> ... (more lines with the same error)
> anyone ran into this issue and knows how to solve it?

Set "Paths and misc options" -> "Shell to use as CONFIG_SHELL" -> bash

This fixed it for me, binutils 2.18 seems to be sensible to such stuff.
(In my case /bin/sh pointed to bash, but it was still failing if I did
 not explicitly set CONFIG_SHELL to bash).

Regards,
Yann E. MORIN.

--
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
`------------------------------^-------^------------------^--------------------'



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


Re: problem with ct-ng 1.5.1: "fragment: command not found"

by Matthias Kaehlcke-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

hi yann,

El Fri, Oct 30, 2009 at 09:50:03AM +0100 Yann E. MORIN ha dit:

> On Thursday 29 October 2009 21:24:42 Matthias Kaehlcke wrote:
> > the build of a uclibc toolchain for i686 using crosstool-ng v1.5.1
> > fails with the following error:
> > [ALL  ]
> > /usr/local/src/ct-ng-build/targets/src/binutils-2.18/ld/emultempl/elf32.em:
> > line 11: fragment: command not found
> > ... (more lines with the same error)
> > anyone ran into this issue and knows how to solve it?
>
> Set "Paths and misc options" -> "Shell to use as CONFIG_SHELL" -> bash
>
> This fixed it for me, binutils 2.18 seems to be sensible to such stuff.
> (In my case /bin/sh pointed to bash, but it was still failing if I did
>  not explicitly set CONFIG_SHELL to bash).

thanks for your reply

CONFIG_SHELL was already set to bash :(

any other ideas?

--
Matthias Kaehlcke
Embedded Linux Engineer
Barcelona

          We can't solve problems by using the same kind
             of thinking we used when we created them
                         (Albert Einstein)
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-

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


Re: problem with ct-ng 1.5.1: "fragment: command not found"

by Yann E. MORIN :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Matthias,
All,

On Friday 30 October 2009 12:27:38 Matthias Kaehlcke wrote:

> El Fri, Oct 30, 2009 at 09:50:03AM +0100 Yann E. MORIN ha dit:
> > On Thursday 29 October 2009 21:24:42 Matthias Kaehlcke wrote:
> > > the build of a uclibc toolchain for i686 using crosstool-ng v1.5.1
> > > fails with the following error:
> > > [ALL  ]
> > > /usr/local/src/ct-ng-build/targets/src/binutils-2.18/ld/emultempl/elf32.em:
> > > line 11: fragment: command not found
> > > ... (more lines with the same error)
> > > anyone ran into this issue and knows how to solve it?
> > This fixed it for me, binutils 2.18 seems to be sensible to such stuff.
> > (In my case /bin/sh pointed to bash, but it was still failing if I did
> >  not explicitly set CONFIG_SHELL to bash).
> CONFIG_SHELL was already set to bash :(
> any other ideas?

Care to test the following, please?

===8<===
--- binutils-2.18/ld/genscripts.sh.orig 2009-10-30 19:15:25.000000000 +0100
+++ binutils-2.18/ld/genscripts.sh      2009-10-30 19:16:30.000000000 +0100
@@ -390,23 +390,6 @@
     *" ${EMULATION_NAME} "*) COMPILE_IN=true;;
 esac

-if test -n "${BASH+set}"; then
-  source_em()
-  {
-    local current_script="$em_script"
-    em_script=$1
-    . $em_script
-    em_script=$current_script
-  }
-
-  alias fragment='em_lineno=$LINENO; fragment_em'
-  fragment_em()
-  {
-    local lineno=$[$em_lineno + 1]
-    echo >> e${EMULATION_NAME}.c "#line $lineno \"$em_script\""
-    cat >> e${EMULATION_NAME}.c
-  }
-else
   source_em()
   {
     . $1
@@ -415,7 +398,6 @@
   {
     cat >> e${EMULATION_NAME}.c
   }
-fi

 # Generate e${EMULATION_NAME}.c.
 # Start with an empty file, then the sourced .em script
===8<===

Regards,
Yann E. MORIN.

--
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
`------------------------------^-------^------------------^--------------------'



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


Re: problem with ct-ng 1.5.1: "fragment: command not found"

by Matthias Kaehlcke-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

hi yann,

El Fri, Oct 30, 2009 at 07:18:19PM +0100 Yann E. MORIN ha dit:

> On Friday 30 October 2009 12:27:38 Matthias Kaehlcke wrote:
> > El Fri, Oct 30, 2009 at 09:50:03AM +0100 Yann E. MORIN ha dit:
> > > On Thursday 29 October 2009 21:24:42 Matthias Kaehlcke wrote:
> > > > the build of a uclibc toolchain for i686 using crosstool-ng v1.5.1
> > > > fails with the following error:
> > > > [ALL  ]
> > > > /usr/local/src/ct-ng-build/targets/src/binutils-2.18/ld/emultempl/elf32.em:
> > > > line 11: fragment: command not found
> > > > ... (more lines with the same error)
> > > > anyone ran into this issue and knows how to solve it?
> > > This fixed it for me, binutils 2.18 seems to be sensible to such stuff.
> > > (In my case /bin/sh pointed to bash, but it was still failing if I did
> > >  not explicitly set CONFIG_SHELL to bash).
> > CONFIG_SHELL was already set to bash :(
> > any other ideas?
>
> Care to test the following, please?

the problem disappeared, but another one showed up. finally i chose to
start with a clean configuration (the other one was based on a
toolchain built some time ago). with the configuration from scratch
and without your patch the toolchain builded with success.

thanks for your help

--
Matthias Kaehlcke
Embedded Linux Engineer
Barcelona

      Anyone who has never made a mistake has never tried anything new
                            (Albert Einstein)
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-

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