On 27/10/2007, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > On Sat, 27 Oct 2007, Shawn Walker wrote: > > > On 27/10/2007, Chris Quenelle <[EMAIL PROTECTED]> wrote: > >> > >> > >> [EMAIL PROTECTED] wrote: > >>> The way to publish unsupported options is currently under discussion. > >>> For now check out > >>> http://www.genunix.org/wiki/index.php/OpenSolaris_Wizard_Options > >> > >> This page has moved to the new official Sun Studio wiki. > >> > >> http://wikis.sun.com/display/SunStudio/OpenSolaris+Wizard+Options > > > > I don't suppose you know that option that enables support for this > > code snippet then? > > > > #ifdef RE_ENABLE_I18N > > /* This static array is used for the map to single-byte characters when > > UTF-8 is used. Otherwise we would allocate memory just to initialize > > it the same all the time. UTF-8 is the preferred encoding so this is > > a worthwhile optimization. */ > > static const bitset_t utf8_sb_map = > > { > > /* Set the first 128 bits. */ > > [0 ... 0x80 / BITSET_WORD_BITS - 1] = BITSET_WORD_MAX > > }; > > #endif > > I don't think suncc has this particular extension. > But to be 100% sure I've asked the C frontend folks to give some response. > > > A Sun engineer told me that they could not disclose what flag it was. > > > > So, they're able to compile GNU sed with Sun Studio and use it, while > > I am not, even though we have the same tools. Lovely. > > This is probably because you have different source. > > AFAICT sun's version of source for sed-4.1.4 > has this patch applied: > > http://opensource.shivakumar.info/Porting_to_Solaris.html
Yes, I have 4.1.5, but, I can't access that URL you pasted either. It doesn't resolve here. -- Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ "Beware of bugs in the above code; I have only proved it correct, not tried it. " --Donald Knuth _______________________________________________ tools-discuss mailing list [email protected]
