PostgreSQL related NEW PORTS need committers

[Jov]

​​
Hi hackers,
 I ported some PostgreSQL related tools/extensions to FreeBSD several weeks
ago，the PR links are as follows. All of them passed portlint and tested
by poudriere testport. Review, comment，test or commit all are welcome，I
really hope some of them can be committed before Q3 quarterly branch
cut.Thanks very much！

pgloader3, Replace of pgloader2 as pgloader2 is not maintained:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219165

postgres-xl,Scalable open source PostgreSQL-based database cluster:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219164

orafce, Oracle's compatibility functions and packages for PostgreSQL:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219616

zhparser,PostgreSQL extension for full-text search of Chinese:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219649

tds_fdw, PostgreSQL foreign data wrapper to connect to MS SQLserver and
Sybase: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219671

pg_repack, Reorganize tables in PostgreSQL databases with minimal
locks.Replace of pg_reorg as it is not maintained:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219679

plpgsql_check, PostgreSQL extension to check PL/pgSQL code:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219680

pgformatter,PostgreSQL SQL syntax beautifier:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219681

ip4r（not new port，update to 2.2）:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219766

Regard
Jov
___
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: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work

[Gerald Pfeifer]

Am 29. Juni 2017 18:55:59 GMT+08:00 schrieb Mark Millard :
>I'm not currently set up to run more than head on
>any of amd64, powerpc64, powerpc, aarch64, or armv6/7
>(which are all I target). And I'm in the middle of
>attempting a fairly large jump to head -r320458 on
>those.

Oh, then I had misunderstood your previous mail. No worries, I'll gently 
proceed then.

I expect to update gcc5 in the next 24 hours.

>[In my normal/head environment I'm switching to lang/gcc7-devel
>for gcc (from lang/gcc6 ) but I'm odd that way.]

The compiler should be fine, it's a number of ports that are not (even blocking 
the move from GCC 5 to 6 as default).

Gerald
___
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: New Healthcare Industry Email List 2017

[Susan Mullins]

Hi,

I trust this email finds you well.

We have the New Healthcare Industry Email List 2017 with emails, and complete 
Contact information

List Contains: Name, Company's Name, Phone Number, Fax Number, Title, Email 
address, Complete Mailing Address, Company revenue, size, Web address etc.

Our Specialties:


  *   Anesthesiologists, Cardiologist, Cardiovascular Disease, Registered Nurse 
Anesthetists
  *   Chiropractor, Dentist, Dermatology, Diagnostic Radiology, Doctor of 
Dental Surgery
  *   Doctor of Medicine, Emergency Medicine, Family Medicine, 
Gastroenterology, General Dentistry
  *   General Practice, General Surgery, Internal Medicine, Marriage & Family 
Therapist,
  *   Medical Director, Naturopathic Medicine, Nephrology, Neurology, Nurse, 
Nurse Practitioner
  *   Obstetrics & Gynaecologist, Occupational Therapist, Oncology, 
Ophthalmology
  *   Optometrist, Orthopaedic Surgery, Orthopedics, Otolaryngology, Pathology, 
Paediatrician
  *   Physical Medicine & Rehabilitation, Physical Therapist, Physician, 
Physician Assistant
  *   Podiatry, Psychiatry, Psychologist, Pulmonary Disease, Radiology, 
Registered Nurse
  *   Social Worker, Speech-Language Pathologist, Surgery, Urology, 
Veterinarian, Massage Therapist


If this sounds of any value, please specify your requirement in detail so that 
I can share a few Healthcare professionals' business contacts just for your 
review.

I look forward to hearing from you soon.

Kind Regards,
Elina Lopez
Demand Generation Specialist

If you do not wish to receive future emails from us, please reply as 
"opt-out"

___
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: math/R: Build failure after PORTREVISION for shlib change

[David Wolfskill]

On Thu, Jun 29, 2017 at 12:39:50PM -0300, Joseph Mingrone wrote:
> ...
> Everything matches.  The successful build in poudriere even has the same
> line that generates the error for you.

I may try ktracing the build

> /usr/local/bin/gcc-ar5 -cr libtre.a regcomp.o regerror.o regexec.o tre-ast.o 
> tre-compile.o tre-match-approx.o tre-match-backtrack.o tre-match-parallel.o 
> tre-mem.o tre-parse.o tre-stack.o xmalloc.o
> 
> Could you have something in your environment or in make.conf that's
> causing a problem?

g1-227(11.1)[1] grep -v '^#' /etc/make.conf
NET_SNMP_SYS_CONTACT="da...@catwhisker.org"
NET_SNMP_SYS_LOCATION="variable"
NET_SNMP_LOGFILE=/var/log/snmpd.log
NET_SNMP_PERSISTENTDIR=/var/net-snmp
SENDMAIL_MC=/etc/mail/laptop.mc
WITH_BSD_JDK=TRUE
WITHOUT_RUNTIME_CPUDETECTION=   YES
WITHOUT_CJK=YES
NO_SUID_XSERVER=YES
DEFAULT_VERSIONS+=linux=c6
INSTALL_AS_NCFTP=yes
OPTIONS_SET=OPTIMIZED_CFLAGS
DEFAULT_VERSIONS+=  perl5=5.24
FORCE_PKG_REGISTER= YES
PKG_NOCOMPRESS=1
g1-227(11.1)[2] 

> Joseph

I'll be trying a poudriere run Saturday morning, and will report
anything "interesting."

Thanks!

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Do Congress's recent actions on health care qualify as "terrorist acts?"

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: math/R: Build failure after PORTREVISION for shlib change

[Joseph Mingrone]

David Wolfskill  writes:
> g1-227(11.1)[2] make -C /usr/ports/math/R showconfig
> ===> The following configuration options are available for R-3.4.0_1:
>  ICU=on: Unicode support via ICU
>  INFO=on: GNU info manuals
>  LDOUBLE=on: Long double data type
>  LETTER=on: US letter paper
>  LIBR=on: Shared R library
>  MEMPROF=off: Memory profiling via Rprofmem() and tracemem()
>  NLS=on: Native Language Support
>  RPROF=on: R profiling via Rprof()
>  X11=on: X11 graphics device
> > Require GCC
>  LTO=on: Use Link Time Optimization
>  OPENMP=on: Parallel processing support via OpenMP
> > Require X11
>  GHOSTSCRIPT=on: Graphics device for bitmap files via Ghostscript
>  JPEG=on: JPEG graphics device
>  CAIROPANGO=on: Cairo graphics device and Pango multi-language text
>  PNG=on: PNG graphics device
>  TCLTK=on: Tcl/Tk GUI toolkit support
>  TEXDOCS=on: Build/Install TeX-dependent documentation files
>  TIFF=on: TIFF image format support
> > Options available for the single BLAS: you have to select exactly one 
> of them
>  ATLAS=off: ATLAS BLAS implementation
>  OPENBLAS=off: OpenBLAS BLAS implementation
>  NETLIB=off: Netlib BLAS implementation
>  RBLAS=on: Use R-bundled BLAS implementation
> ===> Use 'make config' to modify these settings
> g1-227(11.1)[3] 

With those options, the build succeeds in an 11.0-RELEASE-p1 jail.
http://pkg.awarnach.mathstat.dal.ca/data/11amd64-default/2017-06-28_16h53m48s/logs/R-3.4.0_2.log

> Just in case it's relevant, as /usr/local/bin/gcc-ar5 is from gcc5-5.4.0_2:

> g1-227(11.1)[5] make -C /usr/ports/lang/gcc5 showconfig
> ===> The following configuration options are available for gcc5-5.4.0_2:
>  BOOTSTRAP=on: Build using a full bootstrap
>  GRAPHITE=off: Support for Graphite loop optimizations
>  JAVA=on: Java platform support
> ===> Use 'make config' to modify these settings


Everything matches.  The successful build in poudriere even has the same
line that generates the error for you.

/usr/local/bin/gcc-ar5 -cr libtre.a regcomp.o regerror.o regexec.o tre-ast.o 
tre-compile.o tre-match-approx.o tre-match-backtrack.o tre-match-parallel.o 
tre-mem.o tre-parse.o tre-stack.o xmalloc.o

Could you have something in your environment or in make.conf that's
causing a problem?

Joseph


signature.asc
Description: PGP signature

Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work

[Mark Millard]

On 2017-Jun-29, at 3:10 AM, Gerald Pfeifer  wrote:

> Am 28. Juni 2017 22:38:52 GMT+08:00 schrieb Mark Millard  dsl-only.net>:
>> A primary test is building lang/gcc5-devel under release/11.0.1
>> and then using it under stable/11 or some draft of release/11.1.0 .
> 
> Thank you, Mark. Let me know how it went. In the meantime I'll prepare the 
> change for gcc5 itself.

I'm not currently set up to run more than head on
any of amd64, powerpc64, powerpc, aarch64, or armv6/7
(which are all I target). And I'm in the middle of
attempting a fairly large jump to head -r320458 on
those. (powerpc 32-bit and 64-bit just failed
for libc++ time-usage compiling now that 32-bit has
64-bit time_t, including in world32/lib32 contexts
for powerpc64.)

It will likely be a while before I manage to have a
11.x context (without losing my head contexts), much
less examples from all "my" 5 TARGET_ARCH's. (Given past
wchar_t type handling problems (e.g.) for gcc targeting
powerpc family members I think it should be checked.)
I'll have to find and set up disks: I do not even have
such handy/ready at the moment.

[I got into this area by being asked questions, not by
my direct use of release/11.0.1 , stable/11 , or a
draft of release/11.1.0 .]

I'll let you know when I have some test results but
others may get some before I do.

> . . .
>> Eventually most of the lang/gcc* 's will need whatever
>> technique is used.
> 
> Yes, agreed. Version 5 is most important since it's the default; then 6; 4.x 
> is for retro computing fans ;-), so 7 will then be next.

[In my normal/head environment I'm switching to lang/gcc7-devel
for gcc (from lang/gcc6 ) but I'm odd that way.]

===
Mark Millard
markmi at dsl-only.net

___
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
+-+
graphics/gmt| 4.5.15  | 4.5.16
+-+
multimedia/lives| 2.8.4   | 2.8.7
+-+
print/mpage | 2.5.6   | 2.5.7
+-+


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

Thanks.
___
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: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work

[Gerald Pfeifer]

Am 28. Juni 2017 22:38:52 GMT+08:00 schrieb Mark Millard :
>A primary test is building lang/gcc5-devel under release/11.0.1
>and then using it under stable/11 or some draft of release/11.1.0 .

Thank you, Mark. Let me know how it went. In the meantime I'll prepare the 
change for gcc5 itself.

>It looks like the the lang/gcc5-devel build still creates and
>uses the headers that go in include-fixed/ but that they are
>removed from $(STAGEDIR}${TARGLIB} 's tree before installation
>or packaging.
>
>So, if I understand right, lang/gcc5-devel itself still does use
>the adjusted headers to produce its own materials but when
>lang/gcc5-devel is used later it does not. Definitely
>something to be testing since it is a mix overall.

I am not worried about that since that should not cause any binary 
incompatibilities (ABI). The problem we encountered was about source code and 
API in a wide sense of that term.

>Is some form of exp-like run needed that tries to force use
>of a release/11.0.1 built lang/gcc5-devel (-r444563) to build
>other things under, say, stable/11  or some draft of
>release/11.1.0 ? Is this odd combination even possible
>currently?

I am not aware of it, and while originally I was thinking to request an -exp 
run (after the GCC version update which is dragging due to broken ports), time 
is not on our side and the change should be low risk.

> [altermative approach] But I guess that did not work out.

Not with my current level of connectivity and my notebook a dead brick on top 
of that. And my preference is to still build, but stow away (unless explicitly 
requested to keep).

>Eventually most of the lang/gcc* 's will need whatever
>technique is used.

Yes, agreed. Version 5 is most important since it's the default; then 6; 4.x is 
for retro computing fans ;-), so 7 will then be next.

Gerald
___
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: What to do when the port fails in poudriere with "Too many open files" ?

[Matt Smith]

On Jun 28 22:38, Yuri wrote:
I have the port that builds fine without poudriere, but in poudriere 
it always fails with "Too many open files".


This happens during the Java build.


Where is the limit set in jail? /etc/login.conf doesn't have any limit.

What to do in such case? Maybe there is some way to tell Java to limit 
the number of open files?



Yuri



I would take a look at /usr/local/etc/poudriere.conf at the MAX_FILES 
setting.


--
Matt
___
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: /usr/ports -r444615 (e.g.) & head -r320458 (e.g.): sysutils/u-boot-pine64 build fails for arch/arm/dts/pine64_plus.dtb source handling error (gic in a64.dtsi)

[Emmanuel Vadot]

 Hello Mark,

On Wed, 28 Jun 2017 20:52:17 -0700
Mark Millard  wrote:

> On 2017-Jun-28, at 7:44 PM, Mark Millard  wrote:
> 
> > Is the below a BSDL vs. GPL DTS issue?
> > 
> > In my attempt to build sysutils/u-boot-pine64 I got:
> > 
> >  OBJCOPY u-boot.srec
> >  OBJCOPY u-boot-nodtb.bin
> > start=$(aarch64-none-elf-nm u-boot | grep __rel_dyn_start | cut -f 1 -d ' 
> > '); end=$(aarch64-none-elf-nm u-boot | grep __rel_dyn_end | cut -f 1 -d ' 
> > '); tools/relocate-rela u-boot-nodtb.bin 0x4a00 $start $end
> >  SYM u-boot.sym
> >  DTC arch/arm/dts/pine64_plus.dtb
> > Error at arch/arm/dts/.pine64_plus.dtb.dts.tmp:533:27: Expected unit address
> > gic: interrupt-controller@{
> >   ^
> > Error at arch/arm/dts/.pine64_plus.dtb.dts.tmp:533:27: Failed to find root 
> > node /.
> > gic: interrupt-controller@{
> >   ^
> > Failed to parse tree.
> > gmake[3]: *** [scripts/Makefile.lib:299: arch/arm/dts/pine64_plus.dtb] 
> > Error 1
> > gmake[2]: *** [dts/Makefile:36: arch-dtbs] Error 2
> > gmake[1]: *** [Makefile:821: dts/dt.dtb] Error 2
> > gmake[1]: *** Waiting for unfinished jobs
> > gmake[1]: Leaving directory 
> > '/usr/obj/portswork/usr/ports/sysutils/u-boot-pine64/work/u-boot-2016.05'
> > 
> > 
> > 
> > Looking at the gic part of the source. . .
> > 
> > # more 
> > /usr/obj/portswork/usr/ports/sysutils/u-boot-pine64/work/u-boot-2016.05/arch/arm/dts/a64.dtsi
> > . . .
> >gic: interrupt-controller@{
> >compatible = "arm,gic-400";
> >interrupt-controller;
> >#interrupt-cells = <3>;
> >#address-cells = <0>;
> > 
> >reg = <0x01C81000 0x1000>,
> >  <0x01C82000 0x2000>,
> >  <0x01C84000 0x2000>,
> >  <0x01C86000 0x2000>;
> >interrupts =  >  (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_HIGH)>;
> >};
> > 

 Yes the node is wrong but if gpl dtc can handle that maybe we should
to, I'll try to find time to fix that.

> > 
> > I'll be trying 3 other u-boot-*'s so I may have more to
> > report later.
> 
> The other 3 that I tried worked fine:
> 
>   Installation of sysutils/u-boot-rpi2 (u-boot-rpi2-2015.04)
>   Installation of sysutils/u-boot-rpi3 (u-boot-rpi3-2017.01)
>   Installation of sysutils/u-boot-sinovoip-bpi-m3 
> (u-boot-sinovoip-bpi-m3-2016.05)
> 
> So this may be unique to a64.dtsi and its lack of
> hexadecimal digits after the "@" in what I quoted.
> 
> Still, sysutils/u-boot-pine64 used to build. So it may
> be a BSDL vs. GPL DTS issue as far as the handling of
> the notation goes.
> 
> ===
> Mark Millard
> markmi at dsl-only.net

 I also a patch waiting for comment on the u-boot mailing list
that add the possibility to specify which dtc to use, this will be
needed for the next u-boot for arm64 board as it uses 'incbin'
directive which bsd dtc doesn't support yet (David is looking into it).

 Anyway, new u-boot should be out around july 10th so I'll update the
port right after.

 Thanks for reporting.

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