rm static libraries before rebuilding

From: Noah Misch <noah(at)leadboat(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: rm static libraries before rebuilding
Date: 2015-03-01 06:27:45
Message-ID: 20150301062745.GB685188@tornado.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

We build static libraries with "ar crs" or "ar cr". If the static library
already exists in the build directory, those commands will add new members and
replace existing members. They will not remove members present in the
existing library but not named on the "ar" command line. This matters when,
for example, you rerun ./configure in a way that removes a file from
$(LIBOBJS). libpgport carries the obsolete member until "make clean". Let's
fix that by issuing "rm -f" before running $(AR). I would back-patch this.

Attachment Content-Type Size
staticlib-rm-v1.patch text/plain 1.7 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-03-01 06:39:09 Re: rm static libraries before rebuilding
Previous Message Tom Lane 2015-03-01 05:26:26 Re: plpgsql versus domains