From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <3df301650910231945n522c4592ib25cef16e9830202@mail.gmail.com> References: <3df301650910231945n522c4592ib25cef16e9830202@mail.gmail.com> Date: Sat, 24 Oct 2009 10:32:00 -0700 Message-ID: Subject: Re: [9fans] Plan9 awk vs. GNU awk From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Topicbox-Message-UUID: 8f832206-ead5-11e9-9d60-3106f5b1d025 Back when I still ported software to (instead of from) Plan 9, I lost many hours to this kind of fiddling with making Plan 9 behave the way configure expects. It's not worth it. Start porting any piece of software by rm configure* auto*. Usually a good start is to write a mkfile that lists every .c file as a .$O, and then go from there. You can try to compile the files and tweak config.h.in (copied to config.h) as needed to make them compile. This is far less work, and at the end you have a Plan 9 mkfile that fits better into the build process. In the absolute worst case you can run configure on a Linux system and adapt the resulting Makefiles. Configure is supposed to adapt to the systems it runs on (that's the whole reason it exists!), not the other way around. If you choose to spend time on this problem, it would be better spent by fixing autoconf to handle running on Plan 9, submitting patches, and then following through to make sure those patches get accepted. This is probably the same amount of work as adapting Plan 9 but could have a more lasting effect. Russ