19 Mar
2011
19 Mar
'11
9:58 p.m.
If I use a 64-bit system, how do I compile 32-bit packages for other people?
Thanks.
Darrell
19 Mar
19 Mar
10:15 p.m.
New subject: [trinity-devel] Creating 64-bit and 32-bit packages
On Sat, Mar 19, 2011 at 17:58, Darrell Anderson <humanreadable(a)yahoo.com> wrote:
If I use a 64-bit system, how do I compile 32-bit
packages for other people?
Thanks.
Darrell
Truthfully, you'll have to use an emulator such as qemu or a
virtualbox instance.
:(
--
later, Robert Xu
10:58 p.m.
New subject: [trinity-devel] Creating 64-bit and 32-bit packages
On 19 March 2011 18:15, Robert Xu <robxu9(a)gmail.com> wrote:
On Sat, Mar 19, 2011 at 17:58, Darrell Anderson
<humanreadable(a)yahoo.com> wrote:
That is 100% false. It seems to me that almost all of these people
think that virtualization is the answer. the real answer is cross
compilation. for example you can cross compile stuff for an ARM
architecture on your regular Intel machine.
Maybe we need to do our homework before we post to the thread :)
Calvin Morrison
If I use a 64-bit system, how do I compile 32-bit
packages for other people?
Thanks.
Darrell
Truthfully, you'll have to use an emulator such as qemu or a
virtualbox instance.
:(
--
later, Robert Xu
11:04 p.m.
New subject: [trinity-devel] Creating 64-bit and 32-bit packages
On Sat, Mar 19, 2011 at 18:58, Calvin Morrison <mutantturkey(a)gmail.com> wrote:
On 19 March 2011 18:15, Robert Xu
<robxu9(a)gmail.com> wrote:
Heh - well, I've always used virtualization - I guess
cross-compilation also works - well, provided you have the
libraries... right? (/me is not so familiar with it)
--
later, Robert Xu
On Sat, Mar 19, 2011 at 17:58, Darrell Anderson
<humanreadable(a)yahoo.com> wrote:
That is 100% false. It seems to me that almost all of these people
think that virtualization is the answer. the real answer is cross
compilation. for example you can cross compile stuff for an ARM
architecture on your regular Intel machine.
Maybe we need to do our homework before we post to the thread :)
Calvin Morrison If I use a 64-bit system, how do I compile 32-bit
packages for other people?
Thanks.
Darrell
Truthfully, you'll have to use an emulator such as qemu or a
virtualbox instance.
:(
--
later, Robert Xu
11:10 p.m.
New subject: [trinity-devel] Creating 64-bit and 32-bit packages
On Sunday 20 March 2011 00:58:26 Calvin Morrison wrote:
[...]
That is 100% false. It seems to me that almost all of
these people
think that virtualization is the answer. the real answer is cross
compilation. for example you can cross compile stuff for an ARM
architecture on your regular Intel machine.
Maybe we need to do our homework before we post to the thread :)
Calvin Morrison
I'm not so sure that trinity can be crosscompiled easy (do not forget that you
need kdelibs installed, to be able to compile kdebase). A possible solution
can be chroot.
linux32 chroot /path/to/32bit_distro
--
Serghei
11:20 p.m.
New subject: [trinity-devel] Creating 64-bit and 32-bit packages
A chroot or virtual machine seems like less hassle than multi-lib support.
I presume some folks here have been compiling and testing Trinity on 64-bit systems?
Darrell
11:39 p.m.
New subject: [trinity-devel] Creating 64-bit and 32-bit packages
A chroot or virtual machine seems like less hassle
than multi-lib support.
I presume some folks here have been compiling and testing Trinity on
64-bit systems?
Darrell
I have.
Also, I would highly recommend the chroot environment--the kernel itself
supports i386 (even if it is natively x64), so a chroot will run at very
high speed. I have successfully done this manuallly in the past, and
QuickBuild uses this method exclusively.
Any other architecture (ARM, etc.) will require virtualization.
Tim
20 Mar
20 Mar
12:17 a.m.
New subject: [trinity-devel] Creating 64-bit and 32-bit packages
As long as your kernel AND cpu support it, you can cross compile for
it. Maybe you can create a shell script that will pass your build
scripts into a 64bit chroot, then to a 32bit chroot? That would be
faster than a VM, won't require you to do it twice in a row, and will
eliminate the time it takes you to realize that the first build is
done and start the other. You can also have it play a sound based on
if it failed or succeeded, and put different sounds for each arch.
--
Kris
"Piki"
Ark Linux Webmaster
Trinity Desktop Environment Packager
22 Mar
22 Mar
1:33 a.m.
New subject: [trinity-devel] Creating 64-bit and 32-bit packages
cross compilation are no possible, theres too much depends on kdelibs and so
related shared files, so chroot jail ist the solution, virtualization are a
not better option due some CPU/Mem access violations on gcc
runtime-compiling job..
On Sun, Mar 20, 2011 at 1:17 AM, Kristopher Gamrat <pikidalto(a)gmail.com>wrote;wrote:
As long as your kernel AND cpu support it, you can
cross compile for
it. Maybe you can create a shell script that will pass your build
scripts into a 64bit chroot, then to a 32bit chroot? That would be
faster than a VM, won't require you to do it twice in a row, and will
eliminate the time it takes you to realize that the first build is
done and start the other. You can also have it play a sound based on
if it failed or succeeded, and put different sounds for each arch.
--
Kris
"Piki"
Ark Linux Webmaster
Trinity Desktop Environment Packager
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Cofundador de Venenux;
http://shutendouji.net
creador de massenkoh linux.
4809
days inactive
4812
days old
8 comments
7 participants
participants (7)
-
Calvin Morrison -
Darrell Anderson -
Kristopher Gamrat -
PICCORO McKAY Lenz -
Robert Xu -
Serghei Amelian -
Timothy Pearson