Great!

At this point I am going to start drafting an ARC case. Should I draft
up a combined ARC case due to the circular dependencies?

Thanks,
Brian

P.S. - I pinged the GNU maintainer to see if this circular dependancy
can be resolved, but I am guessing it won't happen in short order.

On Tue, Mar 31, 2009 at 1:18 AM, Norm Jacobs <Norm.Jacobs at sun.com> wrote:
>
> I'm sure that we can make it work by building and installing against a proto
> area and then building against that proto area.
>
> ? -Norm
>
> Brian Gupta wrote:
>>
>> Norm,
>>
>> Thanks for your quick reply. One more question if I may.
>>
>> According to the build instructions for GNU libiconv, it has a
>> circular dependency against GNU gettext (on non-Linux platforms):
>>
>> http://www.gnu.org/software/libiconv/
>>
>> "On systems other than GNU/Linux, the iconv program will be
>> internationalized only if GNU gettext has been built and installed
>> before GNU libiconv. This means that the first time GNU libiconv is
>> installed, we have a circular dependency between the GNU libiconv and
>> GNU gettext packages, which can be resolved by building and installing
>> either:
>>
>> - first libiconv, then gettext, then libiconv again,
>>
>> or (on systems supporting shared libraries, excluding AIX)
>>
>> - first gettext, then libiconv, then gettext again.
>> "
>>
>> Is this gonna be doable? I'm thinking if not, we might have to include
>> a degraded GNU gettext.
>>
>> Thanks,
>> Brian
>>
>> On Tue, Mar 31, 2009 at 12:55 AM, Norm Jacobs <Norm.Jacobs at sun.com> wrote:
>>
>>>
>>> See http://arc.opensolaris.org/caselog/PSARC/2007/047/ conflicts go into
>>> /usr/gnu/lib.
>>>
>>> ? ? -Norm
>>>
>>> Brian Gupta wrote:
>>>
>>>>
>>>> What is the current policy for integrating GNU libraries that have a
>>>> Solaris equivalent? (eg. - gettext and libiconv)
>>>>
>>>> Thanks,
>>>> Brian
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>>
>
>



-- 
- Brian Gupta

New York City user groups calendar:
http://nyc.brandorr.com/

Reply via email to