[ptxdist] getdev host packages

[ptxdist] getdev host packages

[Jon Ringle]

One issue that I've run across is that most of our developers have x86
machines and our build machine is x86_64, so the host-*-dev.tar.gz
packages don't work because they are built for the wrong kind of host.
However, is there any reason to think that the other non host
*-dev.tar.gz would be ok to use on x86 if they were built on x86_64
that are target arm?

Jon

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] getdev host packages

[Michael Olbrich]

Hi,

On Thu, Feb 13, 2014 at 09:40:13AM -0500, Jon Ringle wrote:
> One issue that I've run across is that most of our developers have x86
> machines and our build machine is x86_64, so the host-*-dev.tar.gz
> packages don't work because they are built for the wrong kind of host.

I never thought about that. Maybe we should add the host arch to the file
name here?

> However, is there any reason to think that the other non host
> *-dev.tar.gz would be ok to use on x86 if they were built on x86_64
> that are target arm?

Well, all "cross-*" packages will have the same problems. Other than that,
I don't think so. Some packages may create host tools, but those should not
be visible past the install stage. You can verify that easily: Just check
the architecture of all executables in the devpkgs with 'file'. Anything
!arm will be a problem.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] getdev host packages

[Jon Ringle]

On Thu, Feb 13, 2014 at 9:57 AM, Michael Olbrich
<m.olbrich@pengutronix.de> wrote:
> Hi,
>
> On Thu, Feb 13, 2014 at 09:40:13AM -0500, Jon Ringle wrote:
>> One issue that I've run across is that most of our developers have x86
>> machines and our build machine is x86_64, so the host-*-dev.tar.gz
>> packages don't work because they are built for the wrong kind of host.
>
> I never thought about that. Maybe we should add the host arch to the file
> name here?

That's a good idea. Do it for cross-* packages too. Then we won't try
to download {cross,host}-*-dev.tar.gz if the file names don't match
with the host arch.

>
>> However, is there any reason to think that the other non host
>> *-dev.tar.gz would be ok to use on x86 if they were built on x86_64
>> that are target arm?
>
> Well, all "cross-*" packages will have the same problems. Other than that,
> I don't think so. Some packages may create host tools, but those should not
> be visible past the install stage. You can verify that easily: Just check
> the architecture of all executables in the devpkgs with 'file'. Anything
> !arm will be a problem.
>
> Michael
>
> --
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] getdev host packages

[Jon Ringle]

On Thu, Feb 13, 2014 at 10:08 AM, Jon Ringle <jon@ringle.org> wrote:
> On Thu, Feb 13, 2014 at 9:57 AM, Michael Olbrich
> <m.olbrich@pengutronix.de> wrote:
>> Hi,
>>
>> On Thu, Feb 13, 2014 at 09:40:13AM -0500, Jon Ringle wrote:
>>> One issue that I've run across is that most of our developers have x86
>>> machines and our build machine is x86_64, so the host-*-dev.tar.gz
>>> packages don't work because they are built for the wrong kind of host.
>>
>> I never thought about that. Maybe we should add the host arch to the file
>> name here?
>
> That's a good idea. Do it for cross-* packages too. Then we won't try
> to download {cross,host}-*-dev.tar.gz if the file names don't match
> with the host arch.
>

I was trying to workaround this issue by defining in
${PTXDIST_WORKSPACE}/rules/post/host-nodev.make:
HOST_ACL_DEVPKG := NO
HOST_ATTR_DEVPKG := NO
HOST_FAKEROOT_DEVPKG := NO
HOST_FIGLET_DEVPKG := NO
HOST_KMOD_DEVPKG := NO
HOST_LZO_DEVPKG := NO
HOST_LZOP_DEVPKG := NO
HOST_NCURSES_DEVPKG := NO
HOST_OPKG_DEVPKG := NO
HOST_OPKG_UTILS_DEVPKG := NO
HOST_UBOOT_DEVPKG := NO
HOST_XZ_DEVPKG := NO

But the HOST_FAKEROOT_DEVPKG := NO causes the following error to occur:

-----------------------------
target: host-fakeroot.install
-----------------------------

make[1]: Entering directory
`/home/jringle/code/ptx/ec1k-linux-initramfs/platform-EC1K/build-host/fakeroot-1.14.4'
Making install in scripts
make[2]: Entering directory
`/home/jringle/code/ptx/ec1k-linux-initramfs/platform-EC1K/build-host/fakeroot-1.14.4/scripts'
make[3]: Entering directory
`/home/jringle/code/ptx/ec1k-linux-initramfs/platform-EC1K/build-host/fakeroot-1.14.4/scripts'
test -z "/bin" || /usr/local/lib/ptxdist-2014.02.1_GP/bin/mkdir -p "/bin"
 /usr/local/lib/ptxdist-2014.02.1_GP/bin/install -c fakeroot '/bin'
/usr/local/lib/ptxdist-2014.02.1_GP/bin/install: cannot create regular
file `/bin/fakeroot': Permission denied
make[3]: *** [install-binSCRIPTS] Error 1
make[3]: Leaving directory
`/home/jringle/code/ptx/ec1k-linux-initramfs/platform-EC1K/build-host/fakeroot-1.14.4/scripts'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory
`/home/jringle/code/ptx/ec1k-linux-initramfs/platform-EC1K/build-host/fakeroot-1.14.4/scripts'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
`/home/jringle/code/ptx/ec1k-linux-initramfs/platform-EC1K/build-host/fakeroot-1.14.4'
make: *** [/home/jringle/code/ptx/ec1k-linux-initramfs/platform-EC1K/state/host-fakeroot.install]
Error 2

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] getdev host packages

[Michael Olbrich]

On Thu, Feb 13, 2014 at 10:32:52AM -0500, Jon Ringle wrote:
> I was trying to workaround this issue by defining in
> ${PTXDIST_WORKSPACE}/rules/post/host-nodev.make:
> HOST_ACL_DEVPKG := NO
> HOST_ATTR_DEVPKG := NO
> HOST_FAKEROOT_DEVPKG := NO
> HOST_FIGLET_DEVPKG := NO
> HOST_KMOD_DEVPKG := NO
> HOST_LZO_DEVPKG := NO
> HOST_LZOP_DEVPKG := NO
> HOST_NCURSES_DEVPKG := NO
> HOST_OPKG_DEVPKG := NO
> HOST_OPKG_UTILS_DEVPKG := NO
> HOST_UBOOT_DEVPKG := NO
> HOST_XZ_DEVPKG := NO
> 
> But the HOST_FAKEROOT_DEVPKG := NO causes the following error to occur:

With _DEVPKG := NO you need to use HOST_AUTOCONF_SYSROOT instead of
HOST_AUTOCONF in the configure options.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de