Re: pkg-fallout: duplicate symbols?

[Dimitry Andric]

On 22 Aug 2020, at 16:05, Christian Weisgerber  wrote:
> 
> I'm currently receiving pkg-fallout mail that some of the ports I
> maintain are failing to build with "duplicate symbol" errors.

See .

This is because clang 11 defaults to -fno-common now, causing some
programs that incorrectly define multiple copies of the same global
variables to no longer link.

It can be worked around by adding -fcommon to the compilation flags, but
in most cases it should not be too difficult to get rid of the multiply
defined symbols.


> It is unclear to me whether these are actual problems I need to
> take care of, or just some kind of screw-up on the package build
> server.  This part of each message doesn't inspire confidence:
> 
> !!! Jail is newer than host. (Jail: 1300110, Host: 1300100) !!!
> !!! This is not supported. !!!
> !!! Host kernel must be same or newer than jail. !!!
> !!! Expect build failures. !!!

Yeah, this warning is seen all the time, and while it sounds very
ominous, there is not much you can do about it.

-Dimitry



signature.asc
Description: Message signed with OpenPGP

Re: pkg-fallout: duplicate symbols?

[Bob Eager]

On Sat, 22 Aug 2020 14:05:27 - (UTC)
Christian Weisgerber  wrote:

> I'm currently receiving pkg-fallout mail that some of the ports I
> maintain are failing to build with "duplicate symbol" errors.
> 
> It is unclear to me whether these are actual problems I need to
> take care of, or just some kind of screw-up on the package build
> server.  This part of each message doesn't inspire confidence:
> 
> !!! Jail is newer than host. (Jail: 1300110, Host: 1300100) !!!
> !!! This is not supported. !!!
> !!! Host kernel must be same or newer than jail. !!!
> !!! Expect build failures. !!!
> 
> Can somebody clarify what's going on?
> 

I've had some of these. I know that at least some of them are because
CLANG 11 defaults to -no-fcommon (previous was -fcommon).

Basically, a symbol defined (but not extern) in more than one module
will cause this.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

pkg-fallout: duplicate symbols?

[Christian Weisgerber]

I'm currently receiving pkg-fallout mail that some of the ports I
maintain are failing to build with "duplicate symbol" errors.

It is unclear to me whether these are actual problems I need to
take care of, or just some kind of screw-up on the package build
server.  This part of each message doesn't inspire confidence:

!!! Jail is newer than host. (Jail: 1300110, Host: 1300100) !!!
!!! This is not supported. !!!
!!! Host kernel must be same or newer than jail. !!!
!!! Expect build failures. !!!

Can somebody clarify what's going on?

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
science/afni| 20.2.13 | afni_20.2.14
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Reported by:portscout!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"