From: | Rui Hai Jiang <ruihaijiang(at)msn(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(at)2ndquadrant(dot)com>, 高 <pgf00a(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: How is the PostgreSQL debuginfo file generated |
Date: | 2017-11-27 09:13:09 |
Message-ID: | SG2PR02MB11027E19810E636C22694867A0250@SG2PR02MB1102.apcprd02.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thank you for your help.
I have tried many ways you suggested. I was not familiar with this area, so I did spend lots of time trying.
At last, I found the easiest way to do this is to build a new SRPM package, then build other RPMs from the new SRPM.
Thanks a lot,
Ruihai
________________________________
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Sent: Friday, November 24, 2017 12:50:37 AM
To: Rui Hai Jiang
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: How is the PostgreSQL debuginfo file generated
Rui Hai Jiang <ruihaijiang(at)msn(dot)com> writes:
> I’m wondering how to build the debuginfo package from the PostgreSQL source.
> For example to generate something like this one : postgresql91-debuginfo.x86_64.
On platforms where such things exist, that's handled by the packaging
system, not by PG proper. You should proceed by making a new SRPM
and building RPMs from that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | hubert depesz lubaczewski | 2017-11-27 09:15:08 | Re: explain analyze output with parallel workers - question about meaning of information for explain.depesz.com |
Previous Message | Kyotaro HORIGUCHI | 2017-11-27 09:04:57 | Re: default range partition and constraint exclusion |