RE: [Ltib] host side questions

[Rodney Lott]

Yeah, I am worried about this very detail.  I am trying to build the full X11 package and some of the things that I needed to build required a newer version of autotools. So, that was one of the motivations behind my question.

Autotools aside, though, is my process that I outlined the correct way to add a new host-side package?  I would just like to know the correct process for adding a host side package, in the event that I needed to create a host-side tool. 

Thanks.

Rodney

-----Original Message-----
From: Stuart Hughes [mailto:address@hidden]
Sent: Fri 11/19/2010 2:25 PM
To: Rodney Lott
Cc: Aaron Wegner; Bruce; address@hidden
Subject: Re: [Ltib] host side questions

Hi Rodney,

You need to be very careful about updates to autoconf etc, this will
likely break other package builds.

Rodney Lott wrote:
> Hi, Aaron and Bruce.
>
> I'm a little new to things so let me ask a clarifying question regarding
> installing a host side package.  Let's say a package I am creating needs
> a newer version of autoconf and intltool, but I don't want to break any
> of the existing packages by updating the autoconf.spec.  So, would the
> steps be as follows?
>
> 1. Create (let's say) a autoconf-2.61.spec in the dist/lfs-5.1/autoconf
> directory.
> 2. Build it with ./ltib -p autoconf-2.61.spec
> 3. Edit the config/platform/host/{pkg_map,packages.lkc} to add my spec
> file and such.
> 4. Run ./ltib -m config --hostcf to select and ./ltib --hostcf to refresh.
>
> Is there a document somewhere that talks about the difference between
> host side and target side configuration in more detail?
>
> Thanks.
>
> Rodney Lott
>
> -----Original Message-----
> From: address@hidden on behalf of Aaron Wegner
> Sent: Fri 11/19/2010 1:32 PM
> To: Bruce
> Cc: address@hidden
> Subject: Re: [Ltib] host side questions
>
> That doesn't seem like too bad of a hack to me.  You could also install
> your host side package using the LTIB in a location that doesn't overwrite
> the other tools, and just be explicit with your path by making it
> absolute.  Also, if your spec file sets the PATH you won't need to reset
> it since it doesn't get carried over to the next spec file.
>
> You install host side packages like
>
> ./ltib --hostcf
>
> That's assuming you've correctly edited
> config/platform/host/{pkg_map,packages.lkc} and put your spec file
> somewhere where LTIB can find it, i.e. dist/lfs-5.1, and then you run
>
> ./ltib -m config --hostcf
>
> to select it.
>
> You can check what's installed on your host side like
>
> sudo /opt/ltib/usr/bin/rpm --root / --dbpath /opt/ltib/var/lib/rpm -qa
>
> Aaron
>
>> Hey Aaron,
>> I have a similar question out as well.
>> If you have a package that needs to use a specific version of host tools
>> (or
>> a new one) that may break the rest of the build if you update it, I have
>> installed it onto my host separately from ltib. In your .spec file you can
>> explicitly call the tool like /usr/bin/foo. Normally, ltib has it's spoof
>> path first (in my case it's /opt/ltib/usr/bin or whatever).  So if you
>> call
>> 'foo' in your spec file it finds ltib's version first. Or you can pre-pend
>> the PATH to find your tools before ltib.
>> You can capture the path before modifying it:
>> ORIG_PATH=$PATH
>> PATH=/usr/bin:$PATH
>> ... use your tools...
>>
>> .. Reset the path...
>> PATH=$ORIG_PATH
>> OK. Is that a hack? Sorry... But it works and confines it to just one
>> package.
>>
>> I would be careful about making a global change that affects all the
>> package
>> builds;) could get ugly!
>>
>> Thanks,
>> Bruce
>>
>>
>>
>> On Fri, Nov 19, 2010 at 8:34 AM, Aaron Wegner <address@hidden> wrote:
>>
>>> Hi Stuart.  I was wondering if there is a way to add a package to the
>>> host
>>> side without modifying the following files.
>>>
>>> ltib/config/platform/host/ltib.preconfig
>>> ltib/config/platform/host/packages.lkc
>>> ltib/config/platform/host/pkg_map
>>>
>>> Also, is it possible to have a host-side spec file that is not in
>>> dist/lfs-5.1?  I've got my build down to only having to put one new
>>> directory into the LTIB, which is for my board,
>>> config/platform/my-board.
>>> I like that because I can update the LTIB as much as I want and not have
>>> to touch the files I introduced.  I guess I was thinking it might be
>>> nice
>>> to be able to add additional stuff to the host side by putting files in
>>> a
>>> separate area like I do for the target side with the files
>>>
>>> config/platform/my-board/{*.spec,packages.lkc,pkg_map,defconfig}
>>>
>>> I noticed that when configuring the host-side the LTIB will not check
>>> the
>>> my-board directory for spec files.  I guess that makes sense since the
>>> LTIB builds the host packages before you even select your platform, but
>>> maybe there could be an area to put non-standard host side mods.  Also,
>>> it
>>> seems like
>>>
>>> ./ltib --hostcf -m listpkgsbuild
>>>
>>> returns the packages of the target side.  I have to issue the rpm
>>> command
>>> to view the packages installed on the host side.
>>>
>>>
>>> Thanks,
>>>
>>> Aaron
>>>
>>> > Hi Carolyn,
>>> >
>>> >    It's a different problem, we are talking about the LPC31xx NXP
>>> > processor MMC support,
>>> > that seems to be broken with NXP last patches (not related to
>>> MPCxxxxx)
>>> >
>>> >    For your case, dont know, try to make an ext2 partition (using
>>> fdisk,
>>> > and then mkfs.ext2) on the SD
>>> > card and put your rootfs inside, then at boot pass the boot parameters
>>> > to kernel(for the 1st partition):
>>> > root=/dev/mmcblk0p1 rootdelay=2
>>> >
>>> >
>>> > Good luck!
>>> > El 17/11/2010 17:42, Reer, Carolyn (SA-1) escribió:
>>> >>
>>> >> This sounds like same problem I am having:
>>> >>
>>> >> Has anyone booted the kernel from SDHC card?
>>> >>
>>> >> I have 2.6.28 kernel built for Freescale MPC8536E and booting from
>>> NFS.
>>> >>
>>> >> I would like to copy the kernel & file system over to SD card to
>>> >> eliminate NFS from my Ethernet traffic timing tests.
>>> >>
>>> >> I have tried 2-4GB SDHC cars and they are pre-formatted with W95
>>> FAT16
>>> >> partitions.
>>> >>
>>> >> I can mount the partition:
>>> >>
>>> >> mount /dev/mmcblk0p1 /mnt/tmp/
>>> >>
>>> >> But I can't write to it.
>>> >>
>>> >> I tried using fdisk to delete the partition and make a new linux
>>> >> partition; tried changing the FAT16 partition to linux partition.
>>> >>
>>> >> But I can't save the changes.%0
>>>
>>>
>>> _______________________________________________
>>> LTIB home page: http://ltib.org
>>>
>>> Ltib mailing list
>>> address@hidden
>>> http://lists.nongnu.org/mailman/listinfo/ltib
>>>
>>
>
>
>
> _______________________________________________
> LTIB home page: http://ltib.org
>
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> LTIB home page: http://ltib.org
>
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib