On 02/06/2011 10:33 PM, David C. Rankin wrote:
The makearchroot tool may be what drives me back to this approach. I can
get i686 done in VBox, but I can't do x86_64 in Virtualbox even on a 64-bit box.
So makearchroot work for the 'in source' build would be ideal.
Correction - I think I can
On 02/06/2011 09:05 PM, Ray Rashif wrote:
On 7 February 2011 10:38, David C. Rankin
wrote:
This fails with makechrootpkg because nothing gets copied to the chroot. Is
there a way to fix this?
Yes, the copying is "hardcoded". Things in the source array are
copied, and along with those additio
On 7 February 2011 10:38, David C. Rankin
wrote:
> This fails with makechrootpkg because nothing gets copied to the chroot. Is
> there a way to fix this?
Yes, the copying is "hardcoded". Things in the source array are
copied, and along with those additionally the changelog and install
scriptlet.
On 02/06/2011 10:49 AM, Tavian Barnes wrote:
On 4 February 2011 23:02, David C. Rankin
wrote:
How do I tell makechrootpkg to use the files in the same directory as the
PKGBUILD? In the PKGBUILD I simply have:
Why is the checkout in the same directory as the PKGBUILD? Have a
look at /usr/sha
On 4 February 2011 23:02, David C. Rankin
wrote:
> How do I tell makechrootpkg to use the files in the same directory as the
> PKGBUILD? In the PKGBUILD I simply have:
Why is the checkout in the same directory as the PKGBUILD? Have a
look at /usr/share/pacman/PKGBUILD-svn.proto, and every -svn p
On 02/04/2011 09:19 PM, David C. Rankin wrote:
21:02 archangel:/dat_e/david/bld/tmp/kdebase> sudo makechrootpkg -r
/dat_e/david/bld
==> Making package: trinity -1.0 (Sat Feb 5 03:02:26 UTC 2011)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Source
On 02/04/2011 07:21 PM, Ray Rashif wrote:
On 5 February 2011 08:34, David C. Rankin
wrote:
(1) use vbox?
or
(2) use a chroot?
(2)
pacman -S devtools
extra-i686-build (in PKGBUILD dir)
That makes use of mkarchroot and makechrootpkg [1], which makes use of chroot.
They are right, some KDE
On 05/02/11 11:48, David C. Rankin wrote:
On 02/04/2011 07:21 PM, Ray Rashif wrote:
On 5 February 2011 08:34, David C. Rankin
wrote:
(1) use vbox?
or
(2) use a chroot?
(2)
pacman -S devtools
extra-i686-build (in PKGBUILD dir)
That makes use of mkarchroot and makechrootpkg [1], which make
On 02/04/2011 07:21 PM, Ray Rashif wrote:
On 5 February 2011 08:34, David C. Rankin
wrote:
(1) use vbox?
or
(2) use a chroot?
(2)
pacman -S devtools
extra-i686-build (in PKGBUILD dir)
That makes use of mkarchroot and makechrootpkg [1], which makes use of chroot.
They are right, some KDE
On 5 February 2011 08:34, David C. Rankin
wrote:
> (1) use vbox?
>
> or
>
> (2) use a chroot?
(2)
pacman -S devtools
extra-i686-build (in PKGBUILD dir)
That makes use of mkarchroot and makechrootpkg [1], which makes use of chroot.
They are right, some KDE3 applications where no amount of
confi
On 02/04/2011 04:26 PM, Ray Rashif wrote:
On 5 February 2011 04:10, David C. Rankin
wrote:
Guys,
After getting kdelibs done, I have run into a wall with the building
kdebase:
http://websvn.kde.org/branches/trinity/kdebase/
(see bottom of page for admin and cmake links)
Ther
On 5 February 2011 04:10, David C. Rankin
wrote:
> Guys,
>
> After getting kdelibs done, I have run into a wall with the building
> kdebase:
>
> http://websvn.kde.org/branches/trinity/kdebase/
> (see bottom of page for admin and cmake links)
>
> There are 2 issues I'm having on Arch
Guys,
After getting kdelibs done, I have run into a wall with the building
kdebase:
http://websvn.kde.org/branches/trinity/kdebase/
(see bottom of page for admin and cmake links)
There are 2 issues I'm having on Arch:
(1) If kde4/Qt4 is installed, cmake fails when it uses
/usr/
13 matches
Mail list logo
