Re: patch to unhook libxpg4 and liby from build

[David Rhodus <drhodus@xxxxxxxxxxx>]

On Mar 27, 2004, at 7:41 PM, Chris Pressey wrote:

> Howdy once again,
>
> There's an afwul lot of good build re-engineering going on lately, and 
> I
> wanted to contribute a tiny bit to it.  I was looking through src/lib
> and found two libraries that appear to be obsolete (as they are
> essentially empty,) libxpg4 and liby.  So, I unhooked them from my
> build, and as I suspected, everything still builds fine.  The (small)
> patch to achieve this is here:
>
> http://catseye.webhop.net/DragonFlyBSD/patch/unhook_libxpg4_liby.diff
>
> If someone can confirm that these libraries really are really and truly
> 100% obsolete, I'll enqueue the patch.
>
> -Chris

Chris, I first off want to say thanks to bringing this up and just 
making
hasty decisions that may or may not have repercussions on the
system that aren't felt right away.

On FreeBSD the XPG4 support was started in a separate library other
than libc. During 4.5-RELEASE the basic functionality that FreeBSD
had was merged into libc. With that in mind, there are still some ISV's
that try to link BSD against libxpg4. A quick search on the machine
next to me here shows about 6 ports that made a compile time link.
These would have resulted in a ports breakage. I'm not sure there is
really any over-head associated with leaving this stub around. Though,
I'm open to any cleaver idea's people might have for this stub 
relocation.
Perhaps it would be best to leave this, at least for now.

Liby is also something I don't think we want to remove. One thing in
particular that still uses it is yacc and some other compiler tools.
I also think libipsec or something along those lines pulls an external
reference from it.  Again, I think this functionality could be masked
some place else but would most likely add increased linking overhead
in general.

-DR