32-Bit Chroot How-To

**TSJason** · June 4th, 2009

Code:

uname -a

but all I get is

Code:

Linux mavaddat-desktop 2.6.24-23-generic #1 SMP Wed Apr 1 21:43:24 UTC 2009 x86_64 GNU/Linux

. Doesn't this mean I'm not in a 32-bit environment?

This just means that you're running a 64-bit kernel - which should support the 32-bit environment.

**mavaddat** · June 4th, 2009

This just means that you're running a 64-bit kernel - which should support the 32-bit environment.

Thanks, Jason. But shouldn't it be running the 32-bit kernel of the 32-bit environment? I thought that was the point. Also, is it true that

Code:

sudo chroot /chroot/

is the proper way to get into a 32-bit environment (with this tutoral)? How do I check to make sure I'm in the new environment and not the old one?

**TSJason** · June 7th, 2009

mavaddat,

You might be confusing a chroot with a virtual environment. The chroot is simply an environment running within your 64-bit system. The kernel does not change. If you bootstrap with the "--arch i386" then the chroot only contains i386 libraries and as such will only be able to execute the 32-bit binaries. The 64-bit kernel supports 32-bit backwards compatibility which is why we can do this sort of chroot. We could not, for instance, create a 64-bit chroot in a system running a 32-bit kernel.

To test, you should just try building a small 32-bit application from the chroot and they check the libraries that are linked in. There should only be the 32-bit ones there.

If you're looking for a fully 32-bit install (kernel and all), I might suggest taking a look at the free VirtualBox software - or VMWare server 2 (which is free with registration at the vmware site).

**mavaddat** · June 7th, 2009

Originally Posted by TSJason

[...]You might be confusing a chroot with a virtual environment. [...]

Yes, I definitely was having now read your post. (I am new to Linux. Can you tell?)

All this chroot business is only a means to an end for me to compile a program I'm trying to get going. The error I run into is this:

Code:

Linking obj/manager .....
============================
gcc -g -m32 -O3 -Wall -Wno-format -I/usr/include/gdbm -I../common -m32 -lpthread -lm -lgdbm -o obj/manager obj/benManagement.o obj/benMetadata.o obj/benSortedArray.o obj/manager.o obj/managerConfig.o obj/managerlib.o obj/metadata.o obj/metadata_db_ndbm.o obj/revBlockMap.o ../common/obj/blockmap.o ../common/obj/compatible.o ../common/obj/err.o ../common/obj/fllib.o ../common/obj/freeloader_comm.o ../common/obj/HashList.o ../common/obj/LinkList.o ../common/obj/logger.o ../common/obj/md5.o ../common/obj/metadata_common.o ../common/obj/parser.o ../common/obj/QBlockMap.o ../common/obj/queue.o ../common/obj/sha1.o ../common/obj/utility.o
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.2.4/../../../libgdbm.so when searching for -lgdbm
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.2.4/../../../libgdbm.a when searching for -lgdbm
/usr/bin/ld: skipping incompatible /usr/bin/../lib/libgdbm.so when searching for -lgdbm
/usr/bin/ld: skipping incompatible /usr/bin/../lib/libgdbm.a when searching for -lgdbm
/usr/bin/ld: skipping incompatible /usr/lib/libgdbm.so when searching for -lgdbm
/usr/bin/ld: skipping incompatible /usr/lib/libgdbm.a when searching for -lgdbm
/usr/bin/ld: cannot find -lgdbm
collect2: ld returned 1 exit status
make[1]: *** [obj/manager] Error 1

And I'm not sure what to do with it. It seems like the 32-bit program doesn't like my 64-bit object files. What can I do about that? I would appreciate any help you might be able to provide.

**TSJason** · June 8th, 2009

mavaddat,

It seems to me that you're probably just missing some required library. Offhand, I would try installing that dev package inside your chroot environment. For instance:

Code:

sudo apt-get install libgdbm-dev

**mavaddat** · June 8th, 2009

Originally Posted by TSJason

It seems to me that you're probably just missing some required library. Offhand, I would try installing that dev package inside your chroot environment. For instance:

Code:

sudo apt-get install libgdbm-dev

I tried this, but it doesn't seem to work. I do

Code:

sudo chroot /chroot/

and then

Code:

sudo apt-get install libgdbm-dev

but it tells me:

Code:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
libgdbm-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Then I run make on the program I'm trying to compile, and it tells me

Code:

Linking obj/manager .....
============================
gcc -g -m32 -O3 -Wall -Wno-format -I/usr/include/gdbm -I../common -m32 -lpthread -lm -lgdbm -o obj/manager obj/benManagement.o obj/benMetadata.o obj/benSortedArray.o obj/manager.o obj/managerConfig.o obj/managerlib.o obj/metadata.o obj/metadata_db_ndbm.o obj/revBlockMap.o ../common/obj/HashList.o ../common/obj/LinkList.o ../common/obj/QBlockMap.o ../common/obj/blockmap.o ../common/obj/compatible.o ../common/obj/err.o ../common/obj/fllib.o ../common/obj/freeloader_comm.o ../common/obj/logger.o ../common/obj/md5.o ../common/obj/metadata_common.o ../common/obj/parser.o ../common/obj/queue.o ../common/obj/sha1.o ../common/obj/utility.o
collect2: ld terminated with signal 11 [Segmentation fault]
/usr/bin/ld: i386:x86-64 architecture of input file `obj/benManagement.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `obj/benMetadata.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `obj/benSortedArray.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `obj/manager.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `obj/managerConfig.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `obj/managerlib.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `obj/metadata.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `obj/metadata_db_ndbm.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `obj/revBlockMap.o' is incompatible with i386 output

I'm really clueless about what to do.

**TSJason** · June 9th, 2009

mavaddat,

Out of curiosity, what are you trying to compile and have you done a "make clean" since the source was put into your chroot?

**baghery.farhad** · July 10th, 2009

I have installed it, and it works great!

But now I wanna install Oxford Dictionary, after "dchroot -d" and running ./installation.sh returns this error:

#./installation.sh
Verifying archive integrity... All good.
Uncompressing OALD7..........................
This installation doesn't support glibc-2.1 on Linux / x86_64

Please contact Loki Technical Support at support@lokigames.com
The program returned an error code (1)
#

Why returns this error? how fix it?

**nefurimu** · July 12th, 2009

I seem to have the all to common issue immediately after dchroot -d, however mine seems... slightly different unless I haven't paid that much attention.
Upon trying to install synaptic, I get the following issue:

Code:

nefurimu@Malakim:~$ dchroot -d
W: Failed to change to directory ‘/home/nefurimu’: No such file or directory
W: Falling back to directory ‘/’
I: [intrepid chroot] Running shell: ‘/bin/bash’
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

nefurimu@Malakim:/$ dchroot
bash: dchroot: command not found
nefurimu@Malakim:/$ dchroot -d
bash: dchroot: command not found
nefurimu@Malakim:/$ sudo apt-get install synaptic
Reading package lists... Done
Building dependency tree       
Reading state information... Done
synaptic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
13 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Can not write log, openpty() failed (/dev/pts not mounted?)
Setting up dbus (1.2.4-0ubuntu1) ...
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
The system user `messagebus' already exists. Exiting.
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
invoke-rc.d: initscript dbus, action "start" failed.
dpkg: error processing dbus (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of dbus-x11:
 dbus-x11 depends on dbus; however:
  Package dbus is not configured yet.
dpkg: error processing dbus-x11 (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
dpkg: dependency problems prevent configuration of policykit:
 policykit depends on dbus; however:
  Package dbus is not configured yet.
dpkg: error processing policykit (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
dpkg: dependency problems prevent configuration of hal:
 hal depends on dbus (>= 0.61); however:
  Package dbus is not configured yet.
 hal depends on policykit (>= 0.7); however:
  Package policykit is not configured yet.
dpkg: error processing hal (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of libgnomevfs2-0:
 libgnomevfs2-0 depends on dbus (>= 0.90); however:
  Package dbus is not configured yet.
dpkg: error processing libgnomevfs2-0 (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of policykit-gnome:
 policykit-gnome depends on libgnomevfs2-0 (>= 1:2.17.90); however:
  Package libgnomevfs2-0 is not configured yet.
 policykit-gnome depends on policykit; however:
  Package policykit is not configured yet.
 policykit-gnome depends on dbus-x11; however:
  Package dbus-x11 is not configured yet.
dpkg: error processing policykit-gnome (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of gnome-mount:
 gnome-mount depends on hal; however:
  Package hal is not configured yet.
 gnome-mount depends on policykit-gnome; however:
  Package policykit-gnome is not configured yet.
dpkg: error processing gnome-mount (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of libgnome2-0:
 libgnome2-0 depends on libgnomevfs2-0 (>= 1:2.17.90); however:
  Package libgnomevfs2-0 is not configured yet.
dpkg: error processing libgnome2-0 (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of libbonoboui2-0:
 libbonoboui2-0 depends on libgnome2-0 (>= 2.17.3); however:
  Package libgnome2-0 is not configured yet.
dpkg: error processing libbonoboui2-0 (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of libgnomeui-0:
 libgnomeui-0 depends on libbonoboui2-0 (>= 2.15.1); however:
  Package libbonoboui2-0 is not configured yet.
 libgnomeui-0 depends on libgnome2-0 (>= 2.17.3); however:
  Package libgnome2-0 is not configured yet.
 libgnomeui-0 depends on libgnomevfs2-0 (>= 1:2.17.90); however:
  Package libgnomevfs2-0 is not configured yet.
dpkg: error processing libgnomeui-0 (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of libgnome2-vfs-perl:
 libgnome2-vfs-perl depends on libgnomevfs2-0 (>= 1:2.17.90); however:
  Package libgnomevfs2-0 is not configured yet.
dpkg: error processing libgnome2-vfs-perl (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of libgnome2-perl:
 libgnome2-perl depends on libbonoboui2-0 (>= 2.15.1); however:
  Package libbonoboui2-0 is not configured yet.
 libgnome2-perl depends on libgnome2-0 (>= 2.17.3); however:
  Package libgnome2-0 is not configured yet.
 libgnome2-perl depends on libgnomeui-0 (>= 2.22.0); however:
  Package libgnomeui-0 is not configured yet.
 libgnome2-perl depends on libgnomevfs2-0 (>= 1:2.17.90); however:
  Package libgnomevfs2-0 is not configured yet.
 libgnome2-perl depends on libgnome2-vfs-perl (>= 1.00); however:
  Package libgnome2-vfs-perl is not configured yet.
dpkg: error processing libgnome2-perl (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of libgnomevfs2-extra:
 libgnomevfs2-extra depends on libgnomevfs2-0 (>= 1:2.17.90); however:
  Package libgnomevfs2-0 is not configured yet.
dpkg: error processing libgnomevfs2-extra (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
Errors were encountered while processing:
 dbus
 dbus-x11
 policykit
 hal
 libgnomevfs2-0
 policykit-gnome
 gnome-mount
 libgnome2-0
 libbonoboui2-0
 libgnomeui-0
 libgnome2-vfs-perl
 libgnome2-perl
 libgnomevfs2-extra
E: Sub-process /usr/bin/dpkg returned an error code (1)
nefurimu@Malakim:/$ ...sigh

Most of it is just repetitive nonsense, but being a pretty large nub, I hardly begin to assume it might not be relevant. The big issue it just at the bottom. I soooo hope that code tags are how you make posts shorter....

Anyone else encounter this? I'm trying to do a 32-bit intrepid on a 64-bit jaunty... so I wonder if there is anything else I should keep in mind (or should I just downgrade to breezy, which seems to have worked for people?)

EDIT: and just to prove myself a nub, I found it worked the second time (after a few hours), without doing anything differently... oh well... thanks anyway

**kiers** · August 20th, 2010

interesting discussion!
I don't however see use of "jail" command/utility, as in
http://manpages.ubuntu.com/manpages/....2freebsd.html
????

is it better to use chroot or the jail utility for firefox?

Thread: 32-Bit Chroot How-To

Thread Tools

Display

Re: 32-Bit Chroot How-To

Re: 32-Bit Chroot How-To

Re: 32-Bit Chroot How-To

Re: 32-Bit Chroot How-To

Re: 32-Bit Chroot How-To

Re: 32-Bit Chroot How-To

Re: 32-Bit Chroot How-To

Re: 32-Bit Chroot How-To

Re: 32-Bit Chroot How-To

Re: 32-Bit Chroot How-To

Bookmarks

Bookmarks

Posting Permissions