LDFLAGS support for bsd.port.mk and CPPFLAGS/LDFLAGS cleanup
Lev Serebryakov
lev at FreeBSD.org
Sun Sep 25 11:11:43 UTC 2011
Hello, Erik.
You wrote 25 сентября 2011 г., 14:49:19:
>> > The patch was committed, LDFLAGS and CPPFLAGS and now handled
>> > similarily, shouldn't be passed to CONFIGURE_ENV and should be
>> > altered by += like C/CXXFLAGS.
>> Add devel/dbus-glib to the list...
>> Should I make formal PR for all these ports?
> I could build all those ports just fine ysterday (after the referenced
> commit went in) and there has not yet been a wide outcry of people
> having trouble building ports, so I suspect the problem is local to
> your machine.
It is very strange, as I have csup'ped ports tree without any local
changes, and try to "portmaster -a" my installation. When I've
rollback latest changes in these ports, everything works (and
upgraded) perfectly. Ports database is Ok, no lost files or
dependencies, etc.
Many other ports are built without problems, but these three fails
to apply proper LDFLAGS, sqlite3 to actual build commands (please
note, that problem is only if ICU support is turned on for sqlite3,
which is off by default), and tow dbus-related ports on configure
stage.
--
// Black Lion AKA Lev Serebryakov <lev at FreeBSD.org>
More information about the freebsd-ports
mailing list