Re: [Scratchbox-users] scratchbox-core breaking chroot in with multistrap

2011-12-08 Thread Jussi Hakala

On 12/07/2011 05:06 PM, Adam Magaluk wrote:

I figured it was something to do with that, Im just not
very knowledgeable on how exactly binfmt_misc works.

Any ideas on how I could get both of my development strategies working?


Well, the easiest way is to set qemu-arm from your host once again to 
handle the arm binaries.


However, that will break scratchbox in turn. When you want to go back to 
scratchbox, you need to set misc_runner to run arm binaries again. 
Easiest way to do this would be to stop and start scratchbox.


There's no way (but ugly) to get both working the same time.

You could try copying misc_runner, qemu-arm-sb and other files to your 
chroot. Use scratchbox.config from a generic arm target to get suitable 
configuration.


After that you should have a qemu available both in your chroot and your 
in your host from the same path.


Regards,

  Jussi
___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users


Re: [Scratchbox-users] scratchbox-core breaking chroot in with multistrap

2011-12-07 Thread Jussi Hakala

On 12/07/2011 01:54 AM, Adam Magaluk wrote:

Finally I normally run to chroot into my newly created arm emdebian system.

sudo chroot EmDebian /

But as soon as I install scratchbox-core I get the following error
on sudo chroot EmDebian

chroot: failed to run command `/bin/bash': No such file or directory/


It's not breaking chroot.

No such file or directory probably refers to the interepreter which is 
assigned to handle the foreign binary that is /bin/bash.


For emdebian, you have probably set something like /usr/bin/qemu-arm to 
run your arm binaries in binfmt_misc whilst scratchbox uses 
/scratchbox/tools/bin/misc_runner.


You have multiple conflicting assignments for arm binaries in 
binfmt_misc. If memory serves, the last one is the one that matters and 
after installing scratchbox, misc_runner has the arm binaries.


When chrooting to your emdebian root, there's no 
/scratchbox/tools/bin/misc_runner, and /bin/bash cannot be executed, 
hence the error message.


Regards,

  Jussi
___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users


Re: [Scratchbox-users] scratchbox-core breaking chroot in with multistrap

2011-12-07 Thread Adam Magaluk
I figured it was something to do with that, Im just not
very knowledgeable on how exactly binfmt_misc works.

Any ideas on how I could get both of my development strategies working?

I tried to copy /scratchbox/tools/bin/misc_**runner to my
chroot environment and it change the error to.

sudo chroot EmDebian/
/scratchbox/tools/bin/misc_runner: /targets/links/scratchbox.config: No
such file or directory


Seeing that I tried to make the file /targets/links/scratchbox.config in my
chroot env which, I just created a blank file as im not sure what should be
in it. It seems I would have to setup the entire Scratchbox environment
when trying to chroot into my directory that deals with arm binaries. Is
there an easier way?

1. Does scratchbox require binfmt_misc to be associated with it? If not can
is it possible to disable scratchbox from starting binfmt_misc?

2. Is there a way to select which binfmt_misc to associate with when
running chroot?

Cheers,
Adam



On Wed, Dec 7, 2011 at 4:30 AM, Jussi Hakala jussi.hak...@movial.comwrote:

 On 12/07/2011 01:54 AM, Adam Magaluk wrote:

 Finally I normally run to chroot into my newly created arm emdebian
 system.

sudo chroot EmDebian /


 But as soon as I install scratchbox-core I get the following error
 on sudo chroot EmDebian

chroot: failed to run command `/bin/bash': No such file or directory/


 It's not breaking chroot.

 No such file or directory probably refers to the interepreter which is
 assigned to handle the foreign binary that is /bin/bash.

 For emdebian, you have probably set something like /usr/bin/qemu-arm to
 run your arm binaries in binfmt_misc whilst scratchbox uses
 /scratchbox/tools/bin/misc_**runner.

 You have multiple conflicting assignments for arm binaries in binfmt_misc.
 If memory serves, the last one is the one that matters and after installing
 scratchbox, misc_runner has the arm binaries.

 When chrooting to your emdebian root, there's no
 /scratchbox/tools/bin/misc_**runner, and /bin/bash cannot be executed,
 hence the error message.

 Regards,

  Jussi
 __**_
 Scratchbox-users mailing list
 Scratchbox-users@lists.**scratchbox.orgScratchbox-users@lists.scratchbox.org
 http://lists.scratchbox.org/**cgi-bin/mailman/listinfo/**scratchbox-usershttp://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users

___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users


Re: [Scratchbox-users] scratchbox-core breaking chroot in with multistrap

2011-12-07 Thread wangji
hello Adam,
you could try to look at this (very small_rootfs to unfold;) running
mips using binfmt_misc ,

 to see how it is setup
http://wjhowto.googlepages.com/runningdd-wrtmipsinqemu

HTH


Le Wednesday 07 December 2011 à 10:06 -0500, Adam Magaluk a écrit :
 
 
 I figured it was something to do with that, Im just not
 very knowledgeable on how exactly binfmt_misc works.
 
 
 Any ideas on how I could get both of my development strategies
 working?
 
 
 I tried to copy /scratchbox/tools/bin/misc_runner to my
 chroot environment and it change the error to.
 
 
 sudo chroot EmDebian/
 /scratchbox/tools/bin/misc_runner: /targets/links/scratchbox.config: 
 No such file or directory
 
 
 Seeing that I tried to make the file /targets/links/scratchbox.config
 in my chroot env which, I just created a blank file as im not sure
 what should be in it. It seems I would have to setup the entire
 Scratchbox environment when trying to chroot into my directory that
 deals with arm binaries. Is there an easier way?
 
 
 1. Does scratchbox require binfmt_misc to be associated with it? If
 not can is it possible to disable scratchbox from
 starting binfmt_misc?
 
 
 2. Is there a way to select which binfmt_misc to associate with when
 running chroot?
 
 
 Cheers,
 Adam 
 
 
 
 
 
 On Wed, Dec 7, 2011 at 4:30 AM, Jussi Hakala jussi.hak...@movial.com
 wrote:
 On 12/07/2011 01:54 AM, Adam Magaluk wrote:
 
 Finally I normally run to chroot into my newly created
 arm emdebian system.
 
 
sudo chroot EmDebian /
 
 
 But as soon as I install scratchbox-core I get the
 following error
 on sudo chroot EmDebian
 
 
chroot: failed to run command `/bin/bash': No such
 file or directory/
 
 It's not breaking chroot.
 
 No such file or directory probably refers to the interepreter
 which is assigned to handle the foreign binary that
 is /bin/bash.
 
 For emdebian, you have probably set something
 like /usr/bin/qemu-arm to run your arm binaries in binfmt_misc
 whilst scratchbox uses /scratchbox/tools/bin/misc_runner.
 
 You have multiple conflicting assignments for arm binaries in
 binfmt_misc. If memory serves, the last one is the one that
 matters and after installing scratchbox, misc_runner has the
 arm binaries.
 
 When chrooting to your emdebian root, there's
 no /scratchbox/tools/bin/misc_runner, and /bin/bash cannot be
 executed, hence the error message.
 
 Regards,
 
  Jussi
 ___
 Scratchbox-users mailing list
 Scratchbox-users@lists.scratchbox.org
 http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
 
 
 ___
 Scratchbox-users mailing list
 Scratchbox-users@lists.scratchbox.org
 http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users


___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users


Re: [Scratchbox-users] scratchbox-core breaking chroot in with multistrap

2011-12-07 Thread Adam Magaluk
Thanks Ill take a look,

For now I just made a script that shuts down scratchbox chroot and turns it
back on.

Cheers,
Adam

On Wed, Dec 7, 2011 at 11:47 AM, wangji h...@wanadoo.fr wrote:

 hello Adam,
 you could try to look at this (very small_rootfs to unfold;) running
 mips using binfmt_misc ,

  to see how it is setup
 http://wjhowto.googlepages.com/runningdd-wrtmipsinqemu

 HTH


 Le Wednesday 07 December 2011 à 10:06 -0500, Adam Magaluk a écrit :
 
 
  I figured it was something to do with that, Im just not
  very knowledgeable on how exactly binfmt_misc works.
 
 
  Any ideas on how I could get both of my development strategies
  working?
 
 
  I tried to copy /scratchbox/tools/bin/misc_runner to my
  chroot environment and it change the error to.
 
 
  sudo chroot EmDebian/
  /scratchbox/tools/bin/misc_runner:
 /targets/links/scratchbox.config: No such file or directory
 
 
  Seeing that I tried to make the file /targets/links/scratchbox.config
  in my chroot env which, I just created a blank file as im not sure
  what should be in it. It seems I would have to setup the entire
  Scratchbox environment when trying to chroot into my directory that
  deals with arm binaries. Is there an easier way?
 
 
  1. Does scratchbox require binfmt_misc to be associated with it? If
  not can is it possible to disable scratchbox from
  starting binfmt_misc?
 
 
  2. Is there a way to select which binfmt_misc to associate with when
  running chroot?
 
 
  Cheers,
  Adam
 
 
 
 
 
  On Wed, Dec 7, 2011 at 4:30 AM, Jussi Hakala jussi.hak...@movial.com
  wrote:
  On 12/07/2011 01:54 AM, Adam Magaluk wrote:
 
  Finally I normally run to chroot into my newly created
  arm emdebian system.
 
 
 sudo chroot EmDebian /
 
 
  But as soon as I install scratchbox-core I get the
  following error
  on sudo chroot EmDebian
 
 
 chroot: failed to run command `/bin/bash': No such
  file or directory/
 
  It's not breaking chroot.
 
  No such file or directory probably refers to the interepreter
  which is assigned to handle the foreign binary that
  is /bin/bash.
 
  For emdebian, you have probably set something
  like /usr/bin/qemu-arm to run your arm binaries in binfmt_misc
  whilst scratchbox uses /scratchbox/tools/bin/misc_runner.
 
  You have multiple conflicting assignments for arm binaries in
  binfmt_misc. If memory serves, the last one is the one that
  matters and after installing scratchbox, misc_runner has the
  arm binaries.
 
  When chrooting to your emdebian root, there's
  no /scratchbox/tools/bin/misc_runner, and /bin/bash cannot be
  executed, hence the error message.
 
  Regards,
 
   Jussi
  ___
  Scratchbox-users mailing list
  Scratchbox-users@lists.scratchbox.org
 
 http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
 
 
  ___
  Scratchbox-users mailing list
  Scratchbox-users@lists.scratchbox.org
  http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users


 ___
 Scratchbox-users mailing list
 Scratchbox-users@lists.scratchbox.org
 http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users

___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users