FreeBSD 11.0 to FreeBSD 11.1 update concerns

[The Doctor]

All right

1)  Up to 28 July 2017  I was able to compile a openssl 1.0.2 mightly release
with FIPS.

On 29 July , I get

f [ -n "libcrypto.so.1.0.0 libssl.so.1.0.0" ]; then  (cd ..; make 
libcrypto.so.1.0.0);  fi
[ -z "libcrypto" ] || /usr/local/bin/clang40 -fPIC -DOPENSSL_PIC -DZLIB_SHARED 
-DZLIB -DOPENSSL_THREADS -pthread -D_THREAD_SAFE -D_REENTRANT -DDSO_DLFCN 
-DHAVE_DLFCN_H -DL_ENDIAN -O3 -Wall -DOPENSSL_EXPERIMENTAL_JPAKE 
-DOPENSSL_EXPERIMENTAL_STORE -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -I/usr/local/ssl/fips-2.0/include 
-DRC4_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM 
-DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -Iinclude  
-DFINGERPRINT_PREMAIN_DSO_LOAD -o fips_premain_dso   
/usr/local/ssl/fips-2.0/lib/fips_premain.c 
/usr/local/ssl/fips-2.0/lib/fipscanister.o  libcrypto.a 
/usr/lib/libpthread.so: undefined reference to 
`__sys_clock_nanosleep@FBSDprivate_1.0'
/usr/lib/libpthread.so: undefined reference to `__sys_fdatasync@FBSDprivate_1.0'
clang-4.0: error: linker command failed with exit code 1 (use -v to see 
invocation)
*** Error code 1

Stop.
make[2]: stopped in /usr/source/openssl-1.0.2-stable-SNAP-20170729
*** Error code 1

Stop.
make[1]: stopped in /usr/source/openssl-1.0.2-stable-SNAP-20170729/crypto
*** Error code 1

Stop.
make: stopped in /usr/source/openssl-1.0.2-stable-SNAP-20170729


Huh??

2)

Updating dns/bind911  with threads

checking for fseeko... yes
checking for static inline breakage... no
checking for size_t... (cached) yes
checking for ssize_t... (cached) yes
checking for uintptr_t... (cached) yes
checking for socklen_t... (cached) yes
checking whether time.h and sys/time.h may both be included... yes
checking for long long... yes
checking for uname... yes
checking for GCC noreturn attribute... yes
checking for struct lifconf... no
checking for kqueue... yes
checking epoll support... no
checking sys/devpoll.h usability... no
checking sys/devpoll.h presence... no
checking for sys/devpoll.h... no
checking devpoll.h usability... no
checking devpoll.h presence... no
checking for devpoll.h... no
checking if unistd.h or sys/types.h defines fd_set... yes
checking whether byte ordering is bigendian... no
checking GeoIP.h usability... yes
checking GeoIP.h presence... yes
checking for GeoIP.h... yes
checking for library containing GeoIP_id_by_addr_gl... -lGeoIP
checking for library containing fabsf... -lm
checking for GeoIP support... yes
checking for GeoIP Country IPv6 support... yes
checking for GeoIP City IPv6 support... yes
checking for GSSAPI library... disabled
checking for random device... using "/dev/random"
checking for arc4random... (cached) yes
checking for arc4random_stir... yes
checking for arc4random_addrandom... yes
checking whether to build with thread support... yes
checking for gcc -pthread support... no
checking for pthread_create in -lpthread... no
checking for thread_create in -lthr... no
checking for pthread_create in -lc_r... no
checking for pthread_create in -lc... no
configure: error: "could not find thread libraries"
===>  Script "configure" failed unexpectedly.
Please report the problem to m...@freebsd.org [maintainer] and attach the
"/usr/ports/dns/bind911/work/bind-9.11.2/config.log" including the output of
the failure of your make command. Also, it might be a good idea to provide
an overview of all packages installed on your system (e.g. a
/usr/local/sbin/pkg-static info -g -Ea).
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/dns/bind911
*** Error code 1

Stop.
make: stopped in /usr/ports/dns/bind911


All right yet on my other server running a similar hardware configuration
no errors.

What gives?

Also, the FreBSD 11.0 -> 11.1 did not go as smoothly as expeacted.

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
Talk Sense to a fool and he calls you foolish - Euripides
___
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"

Re: Trying to get poudriere to start

[Willem Jan Withagen]

Op 29-7-2017 om 13:34 schreef Chris Rees:



On 29 Jul 2017 11:56, Willem Jan Withagen  wrote:



Op 28-7-2017 om 22:50 schreef Chris Rees:



On 26 Jul 2017 23:59, Willem Jan Withagen 
 wrote:

Op 27-7-2017 om 00:48 schreef Miroslav Lachman:
> Willem Jan Withagen wrote on 2017/07/26 23:24:
>> Hi,
>>
>> This has been working, but now the jail does not even
start
>> Any suggestions why the linux module is giving me trouble?
>>
>>  >  sudo poudriere bulk -vv -j ceph -p local net/ceph
>> kldload: an error occurred while loading module linux.
Please check
>> dmesg(8) for more details.
>> [00:00:00] >> Error: Required kernel module 'linux'
not found
>>
>> The parent system has linux stuff mounted in
/compat/linux/proc
>>
>> Running 12-CURRENT.
>
> Did you tried "kldload linux" in host system? Will
kldstat show you
> loaded kernel module "linux"?
>
Right,
I feel rather stupid... Because I do kknow how most of
this works.
So indeed this is all at the upper level:

Looks like a incompatability
link_elf_obj: symbol freebsd32_exec_copyin_args undefined
linker_load_file: /boot/kernel/linux.ko - unsupported file
type

But why

[~] w...@freetest.digiware.nl
> ls -asl
/boot/kernel/*linux*
  14 -r-xr-xr-x  1 root  wheel   13232 Jul 19 12:55
/boot/kernel/amr_linux.ko*
  47 -r-xr-xr-x  1 root  wheel   47480 Jul 19 12:55
/boot/kernel/geom_linux_lvm.ko*
  14 -r-xr-xr-x  1 root  wheel   13312 Jul 19 12:55
/boot/kernel/ipmi_linux.ko*
771 -r-xr-xr-x  1 root  wheel  659248 Jul 19 12:55
/boot/kernel/linux.ko*
643 -r-xr-xr-x  1 root  wheel  590328 Jul 19 12:55
/boot/kernel/linux64.ko*
  56 -r-xr-xr-x  1 root  wheel   55936 Jul 19 12:55
/boot/kernel/linux_common.ko*
259 -r-xr-xr-x  1 root  wheel  186336 Jul 19 12:55
/boot/kernel/linuxkpi.ko*
  16 -r-xr-xr-x  1 root  wheel   15120 Jul 19 12:55
/boot/kernel/mfi_linux.ko*
  16 -r-xr-xr-x  1 root  wheel   15448 Jul 19 12:55
/boot/kernel/mrsas_linux.ko*
102 -r-xr-xr-x  1 root  wheel  103416 Jul 19 12:55
/boot/kernel/systrace_linux.ko*
112 -r-xr-xr-x  1 root  wheel  113416 Jul 19 12:55
/boot/kernel/systrace_linux32.ko*

[~] w...@freetest.digiware.nl
> file /boot/kernel/linux.ko
/boot/kernel/linux.ko: ELF 64-bit LSB relocatable, x86-64,
version 1
(FreeBSD), not stripped

Are the jail and host the same version?


Nope,

But if I check the jail scripts, the modules are loaded outside of
the jail in the host.
So I would expect that not to mater.

--WjW


Well, depends entirely on which modules are loaded!  Are you loading 
host modules?




This is the code I commented out:

/usr/local/share/poudriere/common.sh: 1780
#   if [ -z "${NOLINUX}" ]; then
#   if [ "${arch}" = "i386" -o "${arch}" = "amd64" ]; then
#   needfs="${needfs} linprocfs"
#   needkld="${needkld} linuxelf:linux"
#   if [ "${arch}" = "amd64" ] && \
#   [ ${HOST_OSVERSION} -ge 1002507 ]; then
#   needkld="${needkld} linux64elf:linux64"
#   fi
#   fi
#   fi

Which suggest that it is the host that is loading the modules.

--WjW
___
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"

Re: rust problem

[Jochen Neumeister]

Am 29.07.2017 um 14:01 schrieb Christoph Moench-Tegeder:
> ## Christoph Moench-Tegeder (c...@burggraben.net):
>
>>> I mailed it the maintainer. He said it is a local problem.
>> I'd like to disagree: the problem is caused by this:
> I have to retract this: a poudriere build (10.3 again) completes.
> That shows that the rust build suffers from some environmental
> poisoning... damn.
>
> Regards,
> Christoph
>
I open a PR for this problem:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221088

Cheers
Jochen
___
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"

Re: rust problem

[Walter Schwarzenfeld]

But you are right. I got it to compile in the port with 
WITHOUT_FBSD10_FIX=yes (I think this unlogical, but it seems to work).


___
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"

Re: rust problem

[Christoph Moench-Tegeder]

## Christoph Moench-Tegeder (c...@burggraben.net):

> > I mailed it the maintainer. He said it is a local problem.
> 
> I'd like to disagree: the problem is caused by this:

I have to retract this: a poudriere build (10.3 again) completes.
That shows that the rust build suffers from some environmental
poisoning... damn.

Regards,
Christoph

-- 
Spare Space
___
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"

Re: rust problem

[Christoph Moench-Tegeder]

## Walter Schwarzenfeld (w.schwarzenf...@utanet.at):

> Rust does not compile in the port on 10.3 amd64.

I'm just debugging the very same problem.

> I mailed it the maintainer. He said it is a local problem.

I'd like to disagree: the problem is caused by this:

===>  Configuring for rust-1.19.0
===>   FreeBSD 10 autotools fix applied to 
/wrkdirs/usr/ports/lang/rust/work/rustc-1.19.0-src/src/vendor/libssh2-sys/libssh2/config.rpath
===>   FreeBSD 10 autotools fix applied to 
/wrkdirs/usr/ports/lang/rust/work/rustc-1.19.0-src/src/vendor/lzma-sys/xz-5.2.3/build-aux/config.rpath
===>   FreeBSD 10 autotools fix applied to 
/wrkdirs/usr/ports/lang/rust/work/.cargo/registry/src/github.com-1ecc6299db9ec823/libssh2-sys-0.2.6/libssh2/config.rpath
===>   FreeBSD 10 autotools fix applied to 
/wrkdirs/usr/ports/lang/rust/work/.cargo/registry/src/github.com-1ecc6299db9ec823/lzma-sys-0.1.4/xz-5.2.3/build-aux/config.rpath

and that comes from bsd.port.mk line 3091 ff.

But I can't figure out why this shouldn't happen on FreeBSD 11 - as far
as I can figure out right now WITHOUT_FBSD10_FIX isn't set automatically,
nor will the run-autotools-fixup be overridden (but I've limited access
to FreeBSD 11 right now).

Regards,
Christoph

-- 
Spare Space
___
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"

Re: Trying to get poudriere to start

[Chris Rees]

___
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"

Re: FreeBSD Port: MailScanner-5.0.3

[Chris Rees]

___
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"

rust problem

[Walter Schwarzenfeld]

Rust does not compile in the port on 10.3 amd64.

error: the listed checksum of 
`/usr/ports/lang/rust/work/rustc-1.19.0-src/src/vendor/lzma-sys/xz-5.2.3/build-aux/config.rpath` 
has changed:

expected: c8b4c017079da9dfb3086a0583e60ffe736184d89005dc5973f0bb0fd17c04bb
actual: 561b00eb30ecaef2c9da17bc195e7d2a7ea63facea38ea9849fbb0ed340bebba

directory sources are not intended to be edited, if modifications are 
required then it is recommended that [replace] is used with a forked 
copy of the source



command did not execute successfully: 
"/usr/ports/lang/rust/work/rustc-1.19.0-src/build/x86_64-unknown-freebsd/stage0/bin/cargo" 
"build" "-j" "4" "--target" "x86_64-unknown-freebsd" "-v" "--release" 
"--frozen" "--manifest-path" 
"/usr/ports/lang/rust/work/rustc-1.19.0-src/src/tools/rust-installer/Cargo.toml"

expected success, got: exit code: 101


Traceback (most recent call last):
  File "/usr/ports/lang/rust/work/rustc-1.19.0-src/x.py", line 20, in 


bootstrap.main()
  File 
"/usr/ports/lang/rust/work/rustc-1.19.0-src/src/bootstrap/bootstrap.py", 
line 678, in main

bootstrap()
  File 
"/usr/ports/lang/rust/work/rustc-1.19.0-src/src/bootstrap/bootstrap.py", 
line 670, in bootstrap

run(args, env=env, verbose=rb.verbose)
  File 
"/usr/ports/lang/rust/work/rustc-1.19.0-src/src/bootstrap/bootstrap.py", 
line 142, in run

raise RuntimeError(err)
RuntimeError: failed to run: 
/usr/ports/lang/rust/work/rustc-1.19.0-src/build/bootstrap/debug/bootstrap 
install --verbose --config ./config.toml --jobs 4

*** Error code 1

Stop.
make[1]: stopped in /usr/ports/lang/rust
*** Error code 1

Stop.
make: stopped in /usr/ports/lang/rust


I mailed it the maintainer. He said it is a local problem.


So my question: Does anybody know this error?

___
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"

Re: FreeBSD Port: MailScanner-5.0.3

[Piotr Kubaj via freebsd-ports]

After your commit, I now get an error during staging:
(00:00:54) 
===
(00:00:54) ===
(00:00:54) ===>  Staging for MailScanner-5.0.3_1
(00:00:54) ** Missing /usr/ports/mail/mailscanner/files/pkg-deinstall.in for 
MailScanner-5.0.3_1.
(00:00:54) *** Error code 1


On 17-07-28 21:48:31, Chris Rees wrote:
>I've committed a fix using @sample for the config files, and fixed the
>regexes for paths.  @sample keyword was made for ports like this...
>The port will no longer destroy your configuration.
>Cheers,
>Chris
> 
>--
>This message has been scanned for viruses and
>dangerous content by [1]MailScanner, and is
>believed to be clean.
>--
>This message has been scanned for viruses and
>dangerous content by [2]MailScanner, and is
>believed to be clean.
> 
> References
> 
>1. http://www.mailscanner.info/
>2. http://www.mailscanner.info/

-- 
  
/ Fog Lamps, n.: \
||
| Excessively (often obnoxiously) bright |
| lamps mounted on the   |
||
| fronts of automobiles; used on dry,|
| clear nights to indicate   |
||
| that the driver's brain is in a fog.   |
||
\ See also "Idiot Lights".   /
  
\   ^__^
 \  (oo)\___
(__)\   )\/\
||w |
|| ||


signature.asc
Description: PGP signature

Re: Trying to get poudriere to start

[Willem Jan Withagen]

Op 28-7-2017 om 22:50 schreef Chris Rees:



On 26 Jul 2017 23:59, Willem Jan Withagen  wrote:

Op 27-7-2017 om 00:48 schreef Miroslav Lachman:
> Willem Jan Withagen wrote on 2017/07/26 23:24:
>> Hi,
>>
>> This has been working, but now the jail does not even start
>> Any suggestions why the linux module is giving me trouble?
>>
>>  >  sudo poudriere bulk -vv -j ceph -p local net/ceph
>> kldload: an error occurred while loading module linux. Please
check
>> dmesg(8) for more details.
>> [00:00:00] >> Error: Required kernel module 'linux' not found
>>
>> The parent system has linux stuff mounted in /compat/linux/proc
>>
>> Running 12-CURRENT.
>
> Did you tried "kldload linux" in host system? Will kldstat show you
> loaded kernel module "linux"?
>
Right,
I feel rather stupid... Because I do kknow how most of this works.
So indeed this is all at the upper level:

Looks like a incompatability
link_elf_obj: symbol freebsd32_exec_copyin_args undefined
linker_load_file: /boot/kernel/linux.ko - unsupported file type

But why

[~] w...@freetest.digiware.nl> ls -asl /boot/kernel/*linux*
  14 -r-xr-xr-x  1 root  wheel   13232 Jul 19 12:55
/boot/kernel/amr_linux.ko*
  47 -r-xr-xr-x  1 root  wheel   47480 Jul 19 12:55
/boot/kernel/geom_linux_lvm.ko*
  14 -r-xr-xr-x  1 root  wheel   13312 Jul 19 12:55
/boot/kernel/ipmi_linux.ko*
771 -r-xr-xr-x  1 root  wheel  659248 Jul 19 12:55
/boot/kernel/linux.ko*
643 -r-xr-xr-x  1 root  wheel  590328 Jul 19 12:55
/boot/kernel/linux64.ko*
  56 -r-xr-xr-x  1 root  wheel   55936 Jul 19 12:55
/boot/kernel/linux_common.ko*
259 -r-xr-xr-x  1 root  wheel  186336 Jul 19 12:55
/boot/kernel/linuxkpi.ko*
  16 -r-xr-xr-x  1 root  wheel   15120 Jul 19 12:55
/boot/kernel/mfi_linux.ko*
  16 -r-xr-xr-x  1 root  wheel   15448 Jul 19 12:55
/boot/kernel/mrsas_linux.ko*
102 -r-xr-xr-x  1 root  wheel  103416 Jul 19 12:55
/boot/kernel/systrace_linux.ko*
112 -r-xr-xr-x  1 root  wheel  113416 Jul 19 12:55
/boot/kernel/systrace_linux32.ko*

[~] w...@freetest.digiware.nl> file /boot/kernel/linux.ko
/boot/kernel/linux.ko: ELF 64-bit LSB relocatable, x86-64, version 1
(FreeBSD), not stripped

Are the jail and host the same version?


Nope,

But if I check the jail scripts, the modules are loaded outside of the 
jail in the host.

So I would expect that not to mater.

--WjW
___
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"

Re: Clang5 crashing on RPI2 compiling gnome3

[Dimitry Andric]

On 29 Jul 2017, at 03:09, bob prohaska  wrote:
> 
> Attempts to compile gnome3 on an RPI2 have run hard aground on
> 
> :57:6: note: expanded from here
> Assertion failed: (0 <= N && N < static_cast(m_byteToColumn.size())), 
> function byteToContainingColumn, file 
> /usr/src/contrib/llvm/tools/clang/lib/Frontend/TextDiagnostic.cpp, line 281.

Yes, this is a relatively recent regression, see 
https://bugs.llvm.org/show_bug.cgi?id=33902


> Is there a workaround?

At the moment I don't know any.  I haven't had time to look into the bug itself.

-Dimitry



signature.asc
Description: Message signed with OpenPGP

Re: JVM based port dependencies?

[Pavel Timofeev]

2017-07-20 21:27 GMT+03:00 Dmytro Bilokha :
> 20 липня 2017 р. 18:17:13 GMT+02:00, Pavel Timofeev 
> написав:
>>
>> Hello!
>> What is the best practice for ports running on top of JVM (like
>> ZooKeeper or ElasticSearch):
>> use all bundled jars (for example, log4j) or take them from other
>> ports as dependencies?
>> 
>>
>> 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"
>
>
> Hello!
> As far as I see, ports running on top of JVM usually use bundled jars. To be
> sure about best practice you can check some already existing ports (Eclipse,
> Idea, Glassfish, Tomcat, etc).
> --
> Best regards,
> Dmytro Bilokha


Thanks a lot for your answer.
I found a documentation for this question
https://www.freebsd.org/doc/en/books/porters-handbook/using-java.html:
...

It is up the porter to decide whether the port installs the additional
JAR dependencies under this directory or uses the already installed
ones (from ${JAVAJARDIR}).
...

However I got even more question about porting a java application
after reading this doc. I'll ask them in freebsd-java@
___
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"

Re: Pkg does not upgrade if more than one repository is defined

[Matthias Fechner]

Am 28.07.2017 um 13:13 schrieb Matt Smith:
>
> This might also be related to the CONSERVATIVE_UPGRADE setting of
> pkg.conf. According to the man page:
>
> CONSERVATIVE_UPGRADE: boolean
> Ensure in multi repository mode that the priority is
> given as much as possible to the repository where a
> package was first installed from.  Default: YES. 

thanks, this helped.

Second solution that was working for me to temporarily disable the
standard repository (poudriere) and do the upgrade, after this enable
the standard repo again.


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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"