Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Failure to build "current" emacs from pkgsrc on current



Riccardo Mottola <riccardo.mottola%libero.it@localhost> writes:

> Greg Troxel wrote:
>> Riccardo Mottola <riccardo.mottola%libero.it@localhost> writes:
>>
>>> while doing a full update with today's pkgsrc con current, I get:
>> by 'full update', what do you mean?
>
> I updated kernel, tools & distribtion to latest.
>
> Then I did update pkgsrc and run pkg_rolling-replace -uv

>> host os?
>
> amd64, NetBSD-current
>
> NetBSD disc 8.99.25 NetBSD 8.99.25 (HP620) #9: Mon Oct 22 10:51:47
> CEST 2018  multix@disc:/usr/obj/sys/arch/amd64/compile/HP620 amd64

So that should be ok.


>>> /usr/pkgsrc/editors/emacs26/work/.buildlink/lib/libgdk-3.so: undefined
>>> reference to `epoxy_has_glx'
>> I dimly remember seeing epoxy/glx issues where various systems have
>> different setings.
>>
>> Are you really sure gdk and everything it depended on had been rebuilt?
>>
>> Does anything else that depends on gdk fail?
>
> that is a good question, shouldn't pkg_rolling-replace -uv handle that
> for me?

Yes, but it can hit an error and exit without finishing.

So I would run it again and see if it reports that there's nothing to
do.

I don't have much useful advice, other than to start using nm or objdump
on the libraries in question and trace which symbols are defined where.

On netbsd-7 amd64, 2018Q3:

> nm -u /usr/pkg/lib/libgdk-3.so|egrep glx
U epoxy_glx_version
U epoxy_has_glx_extension

But I'm not really sure epoxy is.                                  

> I just did run lintpkgsrc -i
>
> disc$ lintpkgsrc -i
> Scan Makefiles: ................._________________________
> Bogus: ${GITHUB_PROJECT:tl}-6.3 (from /usr/pkgsrc/geography/gpxsee/Makefile)
> ...........
> /usr/pkgsrc/net/py-onionbalance/Makefile: Cannot locate
> net/py-onionbalance/Makefile.common in
> . /usr/pkgsrc/net/py-onionbalance
>
> /usr/pkgsrc/net/py-onionbalance/Makefile: make:
> "/usr/pkgsrc/net/py-onionbalance/Makefile" line 3: Could not find
> net/py-onionbalance/Makefile.common make: Fatal errors encountered --
> cannot continue
> Cannot extract py-onionbalance- version
> (/usr/pkgsrc/net/py-onionbalance/Makefile)
> 15993 packages
> Unknown package: 'ap24-subversion' version 1.10.3
> Version mismatch: 'py-expat' 3.6.7 vs 2.7.15
> Version mismatch: 'py-expat' 3.7.1 vs 2.7.15

that looks like you got an in-progress addition and the usual python
default vs 36/37 pkg_chk issue.  not really concerning.


My only other suggestions are

1) to make sure that you have rebuilt *everything* after any change from
X11_TYPE from native to/from modular (via "pkg_admin set rebuild-yes
\*").

2) to make sure you have no old headers that don't belong, in
/usr/include, /usr/X11R*/include, or /usr/pkg/include.  Use find with
ctime to find .h files not written during update, and pkg_admin check to
look at file checksums vs installed, and then find /usr/pkg -atime +7 to
find files not read by pkg_admin check and investigate.


Home | Main Index | Thread Index | Old Index