bug-autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

'od' portability problem


From: Bruno Haible
Subject: 'od' portability problem
Date: Tue, 2 May 2006 16:44:12 +0200
User-agent: KMail/1.5

Hi,

These days I stumbled across a portability pitfall with POSIX 'od', while
writing an autoconf macro. How about documenting it in autoconf?


2006-05-01  Bruno Haible  <address@hidden>

        * doc/autoconf.texi (Limitations of Usual Tools): Add a paragraph
        about 'od'.

*** autoconf.texi.bak   2006-04-29 18:17:13.000000000 +0200
--- autoconf.texi       2006-05-01 22:15:21.000000000 +0200
***************
*** 13098,13103 ****
--- 13098,13114 ----
  rm -f foo
  @end example
  
+ 
+ @item @command{od}
+ @c ---------------
+ @prindex @command{od}
+ 
+ MacOS X has an @command{od} program that shows an error message when any
+ of the standard POSIX options @code{-A}, @code{-j}, @code{-N}, or @code{-t}
+ is used.  The only supported POSIX option is @code{-v}.  On this platform,
+ the BSD @command{hexdump} program is available instead.
+ 
+ 
  @item @command{sed}
  @c ----------------
  @prindex @command{sed}





reply via email to

[Prev in Thread] Current Thread [Next in Thread]