SPARC/Solaris compilation problem solved

[Derek Atkins]

Rob Browning <rlb@defaultvalue.org> writes:

> I tend to think it would be better to add a configure check to see if
> the sed in the user's PATH is the broken one (is there something we
> can test for?), and if it is, then issue an AC_MSG_ERROR stating that
> the user needs to arrange to have the real sed available sooner in
> their PATH.

I'm not sure what to check for.  I suppose you could:

	strings /path/to/sed | grep -i "output line too long"

but that's a fairly fragile test.  You might be able to test by
passing sed something > 4000 bytes and seeing if it fails, but I'm not
sure what is actually failing.

Perhaps just a note in the README? ;)

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord@MIT.EDU                        PGP key available