[Ltib] Re: Attempting to port netcat 1.84 to PPC

[John Weber]

OK - I've actually made it build - here's what I did -

Found out that pkg-config does exist in the LTIB install under
/opt/freescale/ltib/usr/bin/pkg-config

I made a directory called /opt/freescale/ltib/usr/bin/pkg-configs and
copied the glib-2.0.pc there.

Then I set the PKG_CONFIG_PATH to
/opt/freescale/ltib/usr/bin/pkg-configs and exported it (this was
key).

Ran ./ltib -m scbuild -p nc.spec and it worked fine.  I now have a
compiled nc binary that works on the PPC.

Why did I do this?  I need a version of netcat that allows UDP...  The
busybox version doesn't support a -u switch.

John

On Thu, May 29, 2008 at 9:50 PM, John Weber <address@hidden> wrote:
> Hi there -
>
> OK - I've figured out from looking at the email archives that having
> "Requires" and "BuildRequires" in a package meant to be built by LTIB
> is not a good idea.  So, I've commented these out and the prep step
> works fine.  I now have patched source for nc.
>
> However, the next issue is that nc really does depend on glib2.  I've
> prepped the source for glib2 into rpm/BUILD/glib-2.14.3.
>
> So, what I get from ./ltib -m scbuild -p nc.spec is the following:
>
> rpmbuild --dbpath /mnt/FREESCALE/LTIB/ltib-mpc837xerdb-20080409/rpmdb
> --target ppc --define '_unpackaged_files_terminate_build 0' --define
> '_target_cpu ppc' --define '__strip strip' --define '_topdir
> /mnt/FREESCALE/LTIB/ltib-mpc837xerdb-20080409/rpm' --define '_prefix
> /usr' --define '_tmppath
> /mnt/FREESCALE/LTIB/ltib-mpc837xerdb-20080409/tmp' --define '_mandir
> /usr/share/man' --define '_sysconfdir /etc' --define '_localstatedir
> /var' -bc --short-circuit
> /mnt/FREESCALE/LTIB/ltib-mpc837xerdb-20080409/dist/lfs-5.1/nc/nc.spec
> Building target platforms: ppc
> Building for target ppc
> Executing(%build): /bin/sh -e
> /mnt/FREESCALE/LTIB/ltib-mpc837xerdb-20080409/tmp/rpm-tmp.88506
> + umask 022
> + cd /mnt/FREESCALE/LTIB/ltib-mpc837xerdb-20080409/rpm/BUILD
> + cd nc
> ++ pkg-config --cflags --libs glib-2.0
> Package glib-2.0 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `glib-2.0.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'glib-2.0' found
> ...
>
> I've confirmed that a glib-2.0.pc exists in the directory 
> rpm/BUILD/glib-2.14.3/
>
> I've tried creating an environment variable called PKG_CONFIG_PATH
> with the path to this file and the LTIB builder doesn't seem to see
> it.
>
> How can I make pkg-config (verified installed on my Centos5 based
> machine) work with LTIB?  Saw some threads on a pkg-config patch on
> this list, but all referenced a file in
> /opt/freescale/usr/bin/pkg-config.  This doesn't get installed with
> the default ISO download of the MPC837x BSP from Freescale.  The only
> directory in that is /opt/freescale/usr/local - that's it.
>
> I've verified that the version of LTIB, as reported in the ./ltib
> --version is 7.4.1.
>
> Thanks,
> John
>
> On Thu, May 29, 2008 at 5:01 PM, John Weber <address@hidden> wrote:
>> Has anyone attempted to port nc (netcat) to PPC?  Not the GNU netcat,
>> but the OpenBSD netcat.
>>
>> Downloaded the SRPM and installed it with rpm -i in order to get at
>> the spec and source files.
>>
>> The issue is that the spec file has a dependency on a couple of things
>> - pkg-config and glibc-2.0.
>>
>> Here is a snippet of the spec file:
>>
>> Version: 1.84
>> Release: 10%{?dist}
>> URL:     http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/nc/
>> Source0: nc-%{version}.tar.bz2
>> Patch0: nc-1.84-glib.patch
>> Patch1: nc-1.78-pollhup.patch
>> Patch2: nc-1.82-reuseaddr.patch
>> Patch3: nc-gcc_signess.patch
>> Patch4: nc-1.84-connect_with_timeout.patch
>> Patch5: nc-1.84-udp_stop.patch
>> Patch6: nc-1.84-udp_port_scan.patch
>> Patch7: nc-1.84-crlf.patch
>> Patch8: nc-1.84-verb.patch
>> License: GPL
>> Group: Applications/Internet
>> BuildRoot: %{_tmppath}/%{name}-root
>> BuildRequires: pkgconfig, glib2-devel
>> Requires: glib2
>>
>> I know that I can add the glib2 package, so run time support shouldn't
>> be a problem.  How do I get around the other dependencies, though?
>>
>> John
>>
>