Message: previous - next
Month: July 2012

Re: [trinity-devel] (glibc 2.16.0?) [was Re: [trinity-devel] tdebase - ftbfs - rpcgen - cannot find any C preprocessor]

From: "David C. Rankin" <drankinatty@...>
Date: Mon, 09 Jul 2012 22:23:50 -0500
On 07/09/2012 07:16 PM, Darrell Anderson wrote:
> Just a guess, based on the forum link you provided.
> As a test you could run sed -i in real time in your build script against the
> following two files, or edit them and create a patch:
> tdebase/kioslave/nfs/CMakeLists.txt:34:  COMMAND rpcgen -c -o mount_xdr.c
> ${CMAKE_CURRENT_SOURCE_DIR}/mount.x tdebase/kioslave/nfs/CMakeLists.txt:38:
> COMMAND rpcgen -c -o nfs_prot_xdr.c ${CMAKE_CURRENT_SOURCE_DIR}/nfs_prot.x
> tdebase/kioslave/nfs/    cd $(srcdir) && rpcgen ./mount.x 
> tdebase/kioslave/nfs/    cd $(srcdir) && rpcgen ./nfs_prot.x

Sounds like you do some 'pretty darn good guessing'...

> On my system, 'whereis -b cpp' indicates the location is /usr/bin --- an FHS
> standard location. Where is that file installed in Arch? Or is the file name
> changed in Arch? That would be the path to add with the -Y switch.

In the same spot:

22:13 archangel:/dat_e/abs/util-linux> whereis -b cpp
cpp: /usr/bin/cpp

> Long term we probably need to patch the CMakeLists.txt file:
> * Discover the path of cpp * Add the -Y switch
> Searching the GIT repository indicates tdebase is the only packages that
> calls rpcgen.

That looks like the information we need for a bug report. Since the fix looks
simple from this standpoint, I'll open the bug and mark it a "Blocker" for R14.
Hopefully, this will be the last little 'surprise' of the gcc/glib update
season. But, since we are working on making R14 the best stable TDE release to
date, I want it to build and run on the current libs -- that way we get a bit of
longevity from the initial release and not a flood of bug reports filed right
off the bat as each distro moves to glibc 2.16.

> Darrell

((You really need to install and run at least one partition of Arch. Talk about
the excitement of trying to iterate down to a final finished project the size of
TDE when the foundation is constantly changing -- wow!  It never gets old...))

Seriously, I think there has rarely been any 3 month stretch before in recent
history where so many of the underlying libraries have had significant upstream
changes as TDE has tried to dial in a next release -- not to mention one with
the polish and improvement that TDE has undergone to get to the point of this
R14 release.

Little more time on the front end -- better reviews, less bugs on the backend :)

David C. Rankin, J.D.,P.E.