Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0002674]: patch-kernel.sh failes on newer versions of Ubuntu
Date: Tue, 25 Mar 2008 20:45:11 -0700	[thread overview]
Message-ID: <5bb6a2fd210abaa08061822182ced615@bugs.uclibc.org> (raw)


A NOTE has been added to this issue. 
====================================================================== 
http://busybox.net/bugs/view.php?id=2674 
====================================================================== 
Reported By:                antab
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   2674
Category:                   Standards Compliance
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             03-25-2008 08:20 PDT
Last Modified:              03-25-2008 20:45 PDT
====================================================================== 
Summary:                    patch-kernel.sh failes on newer versions of Ubuntu
Description: 
The patch-kernel.sh script fails on newer versions of Ubuntu (and debian)
where the /bin/sh link has been changed form /bin/bash to /bin/dash. The
script will fail at line 23:
for i in `cd ${patchdir}; ls -d ${patchpattern} 2> /dev/null` ; do

where dash dosen't expand the ${patchpattern} but passes it directly to
ls. Quick fix is to relink /bin/sh to bash, but scripts that depend on
bash only features should NOT use /bin/sh but /bin/bash directly.

more about the difference between dash and bash at:
https://wiki.ubuntu.com/DashAsBinSh.
====================================================================== 

---------------------------------------------------------------------- 
 hmoffatt - 03-25-08 20:45  
---------------------------------------------------------------------- 
Can't reproduce this on Debian (changed top of script to #!/bin/dash
instead). Which package?

Mind you there doesn't seem to be any need to use ${x} throughout the
script rather than $x. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-25-08 08:20  antab          New Issue                                    
03-25-08 08:20  antab          Status                   new => assigned     
03-25-08 08:20  antab          Assigned To               => buildroot       
03-25-08 20:45  hmoffatt       Note Added: 0005944                          
======================================================================

             reply	other threads:[~2008-03-26  3:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26  3:45 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-25 15:20 [Buildroot] [buildroot 0002674]: patch-kernel.sh failes on newer versions of Ubuntu bugs at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5bb6a2fd210abaa08061822182ced615@bugs.uclibc.org \
    --to=bugs@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox