Comments on: building sed for osx http://blog.apokalyptik.com/2008/04/24/building-sed-for-osx/ The random things that spew forth from my brain... Mon, 16 Jan 2012 18:43:29 +0000 hourly 1 http://wordpress.org/?v=3.4-alpha-19620 By: Toby http://blog.apokalyptik.com/2008/04/24/building-sed-for-osx/comment-page-1/#comment-9444 Toby Sat, 16 Oct 2010 16:06:32 +0000 http://blog.apokalyptik.com/?p=282#comment-9444 Austin, Try /usr/sfw/bin/gsed - it's bundled with various Solaris releases. Austin, Try /usr/sfw/bin/gsed – it's bundled with various Solaris releases.

]]> By: apokalyptik http://blog.apokalyptik.com/2008/04/24/building-sed-for-osx/comment-page-1/#comment-8375 apokalyptik Fri, 20 Mar 2009 08:38:41 +0000 http://blog.apokalyptik.com/?p=282#comment-8375 I dont forsee any problems with that except for portability. if you specify /usr/local/bin/sed and move the script to another box you have to remember to move sed. I guess in this case you could have your script put /usr/local/bin at a higher precedence in your $PATH (or QV) and then test (or not) the version at runtime. by using "sed' and not "/path/to/sed" this would allow a more graceful failover on a new system (with a new sed) I dont forsee any problems with that except for portability. if you specify /usr/local/bin/sed and move the script to another box you have to remember to move sed. I guess in this case you could have your script put /usr/local/bin at a higher precedence in your $PATH (or QV) and then test (or not) the version at runtime. by using "sed' and not "/path/to/sed" this would allow a more graceful failover on a new system (with a new sed)

]]> By: Austin Tashis http://blog.apokalyptik.com/2008/04/24/building-sed-for-osx/comment-page-1/#comment-8373 Austin Tashis Fri, 20 Mar 2009 02:35:56 +0000 http://blog.apokalyptik.com/?p=282#comment-8373 I also got that error. I was trying to install sed so I could develop a script to be used on an ancient Sun server with an ancient version of sed that doesn't even know about extended regex, as far as I can tell. It doesn't have a manpage or even an option to display the version. At least if you give it an option it doesn't understand it spits out the minimal "usage" message. So anyway, thanks for the suggestion about installing an older version of sed to build the latest version. I don't think that ever would have occurred to me. I'm surprised that the sed developers didn't realize there were different versions of sed with different options and write the configure script to recognize the rather predictable errors and respond to them by trying other options. Also, I was going to go ahead and install sed in /usr/local/bin and keep it out of the default command path, assuming that there are probably cron tasks and other system utilities that depend on sed -E. Have you run into any issues there? I also got that error. I was trying to install sed so I could develop a script to be used on an ancient Sun server with an ancient version of sed that doesn't even know about extended regex, as far as I can tell. It doesn't have a manpage or even an option to display the version. At least if you give it an option it doesn't understand it spits out the minimal "usage" message.

So anyway, thanks for the suggestion about installing an older version of sed to build the latest version. I don't think that ever would have occurred to me. I'm surprised that the sed developers didn't realize there were different versions of sed with different options and write the configure script to recognize the rather predictable errors and respond to them by trying other options.

Also, I was going to go ahead and install sed in /usr/local/bin and keep it out of the default command path, assuming that there are probably cron tasks and other system utilities that depend on sed -E. Have you run into any issues there?

]]> By: TjL http://blog.apokalyptik.com/2008/04/24/building-sed-for-osx/comment-page-1/#comment-8234 TjL Thu, 15 Jan 2009 10:48:48 +0000 http://blog.apokalyptik.com/?p=282#comment-8234 Thanks! I found this while trying to do the same thing for the same reasons. Wouldn't have thought to install an old version of sed. Thanks! I found this while trying to do the same thing for the same reasons.

Wouldn't have thought to install an old version of sed.

]]> By: David Cancel http://blog.apokalyptik.com/2008/04/24/building-sed-for-osx/comment-page-1/#comment-8047 David Cancel Wed, 17 Dec 2008 14:50:54 +0000 http://blog.apokalyptik.com/?p=282#comment-8047 Thanks brother for the tip. David Thanks brother for the tip.

David

]]> By: apokalyptik http://blog.apokalyptik.com/2008/04/24/building-sed-for-osx/comment-page-1/#comment-7784 apokalyptik Sat, 26 Apr 2008 12:29:18 +0000 http://blog.apokalyptik.com/?p=282#comment-7784 You absolutely can, and up till now i have. still doesn't help when you spend a lot of time in both, and like to be able to copy and paste one-liners between the two... doesn't feel right to have to sed your sed scripts... ya know? You absolutely can, and up till now i have. still doesn't help when you spend a lot of time in both, and like to be able to copy and paste one-liners between the two… doesn't feel right to have to sed your sed scripts… ya know?

]]> By: Joseph Scott http://blog.apokalyptik.com/2008/04/24/building-sed-for-osx/comment-page-1/#comment-7783 Joseph Scott Sat, 26 Apr 2008 12:26:29 +0000 http://blog.apokalyptik.com/?p=282#comment-7783 For BSD sed you can use -E, which does the same thing as -r in GNU sed. For BSD sed you can use -E, which does the same thing as -r in GNU sed.

]]>