[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Respecting CC/CFLAGS/etc (was: Re: update: enigma)
- To: ports@openbsd.org
- Subject: Respecting CC/CFLAGS/etc (was: Re: update: enigma)
- From: naddy@mips.inka.de (Christian Weisgerber)
- Date: Tue, 5 Nov 2002 00:46:10 +0000 (UTC)
- Newsgroups: list.openbsd.ports
- References: <20021030132138.A22413@daemonkitty.net> <appte9$2vhp$2@kemoauc.mips.inka.de> <20021031015859.GB1502@boetes.org>
Han Boetes <han@mijncomputer.nl> wrote:
> If I would like to keep in mind that I could send patches to the authors
> of the software so they can take these simple wishes in account what
> should the patches look like.
There is no general answer to this; the details depend on the build
framework of the affected piece of software.
> In the Makefile.in I mostly see something like : CC= @CC@ which is not a
> problem, just that the configure script doesn't take CC in account.
>
> But lots of configure files are now generated with automake. So what
> would be the best way to solve this situation?
configure and Makefile frameworks generated with autoconf and
automake correctly pick up CC/CFLAGS/CXX/CXXFLAGS by default. If
they don't, then that's because the authors have accidentally or
purposely overridden those variables. If it's an accident, you
study up on the GNU auto* tools and send a fix. If it's intentional,
you can talk to the authors, but they are likely to stubbornly
insist that their program be built by default with -O20 or some
similar nonsense. In that case you just lug the patch along in the
port.
--
Christian "naddy" Weisgerber naddy@mips.inka.de