Re: rm static libraries before rebuilding

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
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 14:37:50
Message-ID: 20150301143750.GP2384@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Noah Misch wrote:
> 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 was (as I expect many were) bitten by this recently.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-03-01 15:01:25 Re: Buildfarm has got the measles
Previous Message Alvaro Herrera 2015-03-01 14:36:59 Re: Additional role attributes && superuser review