Hi Reuben, On 8 Dec 2010, at 22:32, Reuben Thomas wrote: > On 8 December 2010 14:11, Gary V. Vaughan <[email protected]> wrote: >> If you are on a glibc system, I think the library provides the necessary >> symbol and you should be able to build a working libposix from the topic >> branch after a git pull. Otherwise you'll have to link in the progname >> module, or similar to resolve it... until we come up with a blessed >> method for dealing with it properly. > > Since I'm using glibc, I don't mind, but why is it a problem for a > library? Doesn't it just place a requirement on the program linking > against it, in the same way that the C runtime system does on main?
glibc actually doesn't put that requirement on the main program, because it automatically provides a suitable symbol to the gnulib error module. I haven't looked carefully or thought deeply about why my Mac OS X system chokes during the link of libposix for the lack of a program_name symbol or equivalent... but it's entirely likely that there's a reasonably portable ands straight-forward way to clean things up for libposix without shipping progname.c. When I'm not at the tail end of a long day of coding, I'll find some time to think it through properly if no one has beaten me to a good solution before then :) Cheers, -- Gary V. Vaughan ([email protected])
