Re: rm static libraries before rebuilding

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: rm static libraries before rebuilding
Date: 2015-03-01 06:39:09
Message-ID: 27684.1425191949@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Noah Misch <noah(at)leadboat(dot)com> writes:
> 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.

+1 ... I doubt anybody's thought about this.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Gierth 2015-03-01 06:55:55 Re: plpgsql versus domains
Previous Message Noah Misch 2015-03-01 06:27:45 rm static libraries before rebuilding