Re: What causes libtool to relink?

2015-02-23 Thread Tijl Coosemans 
On Sun, 22 Feb 2015 20:11:51 + (UTC) Christian Weisgerber 
 wrote:
> I'm completely stuck on a problem report that comes down to this:
> "/bin/sh ../../libtool --mode=install" for a loadable module triggers
> libtool to attempt to relink the .la file on the reporter's system,
> which eventually fails.  I cannot reproduce this.  No such relinking
> happens here, libtool simply installs the .so file.
> 
> What causes libtool to "relink" a .la file?

When it links to another library in the work directory.  Then it needs
to be relinked so it links to the installed copy of that library.
___
freebsd-ports@freebsd.org mailing list
http://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

2015-02-23 Thread 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
+-+
net-p2p/qbittorrent | 3.1.11  | 3.1.12
+-+
net-p2p/qbittorrent-nox11   | 3.1.11  | 3.1.12
+-+


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
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

net-mgmt/net-snmp: compile error: error: variable has incomplete type 'struct ifaddr' struct ifaddr ifaddr;

2015-02-23 Thread O. Hartmann 
Portnet-mgmt/net-snmp fails to update/build on CURRENT:

libtool: compile:  cc -I../../include -I. -I../../agent
-I../../agent/mibgroup -I../../snmplib -I/usr/include
-DNETSNMP_ENABLE_IPV6 -fno-strict-aliasing -O2 -pipe -O3 -march=native
-I/usr/local/include -I/include -D_WANT_IFADDR -fstack-protector
-fno-strict-aliasing -std=c99 -Ufreebsd11 -Dfreebsd11=freebsd11
-DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe
-fstack-protector -I/usr/local/include
-I/usr/local/lib/perl5/5.18/mach/CORE -c mibII/ipv6.c  -fPIC -DPIC -o
mibII/.libs/ipv6.o mibII/ipv6.c:806:20: warning: returning 'char *'
from a function with result type 'u_char *' (aka 'unsigned char *')
converts between pointers to integer types with different sign
[-Wpointer-sign] return p; ^ mibII/ipv6.c:848:29: error: variable has
incomplete type 'struct ifaddr' struct ifaddr   ifaddr;
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

editors/libreoffice[-i18n]: compile failure: cannot install: the port wants postgresql-client

2015-02-23 Thread O. Hartmann 
Updating and installig of port editors/libreoffice[-i18n] fails with
the strange error shown below. Port
databases/postgresql94-[server|client] is installed on the system in
question, running 

11.0-CURRENT FreeBSD 11.0-CURRENT #1 r279201: Mon Feb 23 10:00:43 CET
2015 amd64

What is wrong with this installation/with the ports tree? Deleting the
port doesn't solve the problem.

Please CC 

Regards and thanks in advance,

OH

===>>> Port directory: /usr/ports/editors/libreoffice

===>>> This port is marked IGNORE
===>>> cannot install: the port wants postgresql-client version
9.0 9.1 9.2 9.3 9.4 and you have version 9.4 installed


===>>> If you are sure you can build it, remove the
   IGNORE line in the Makefile and try again.

===>>> Update for editors/libreoffice failed
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: editors/libreoffice[-i18n]: compile failure: cannot install: the port wants postgresql-client

2015-02-23 Thread Ben Woods 
I think the issue is simply that you have the DEBUG options enabled for
your ports building (most likely in /etc/make.conf).

According to editors/libreoffice/Makefile, building libreoffice with DEBUG
enabled is broken.

Try building without DEBUG and see how you go.

Regards,
Ben

On Monday, February 23, 2015, O. Hartmann 
wrote:

> Updating and installig of port editors/libreoffice[-i18n] fails with
> the strange error shown below. Port
> databases/postgresql94-[server|client] is installed on the system in
> question, running
>
> 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r279201: Mon Feb 23 10:00:43 CET
> 2015 amd64
>
> What is wrong with this installation/with the ports tree? Deleting the
> port doesn't solve the problem.
>
> Please CC
>
> Regards and thanks in advance,
>
> OH
>
> ===>>> Port directory: /usr/ports/editors/libreoffice
>
> ===>>> This port is marked IGNORE
> ===>>> cannot install: the port wants postgresql-client version
> 9.0 9.1 9.2 9.3 9.4 and you have version 9.4 installed
>
>
> ===>>> If you are sure you can build it, remove the
>IGNORE line in the Makefile and try again.
>
> ===>>> Update for editors/libreoffice failed
> ___
> freebsd-ports@freebsd.org  mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org
> "
>


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: squid 3.5 plans

2015-02-23 Thread Nick Rogers 
On Fri, Feb 20, 2015 at 11:28 PM, Marko Cupać  wrote:

> On Thu, 19 Feb 2015 21:23:15 -0500
> Robert Simmons  wrote:
>
>
> > That is true. It looks like an update to both 3.5 and 3.4 were
> > released on the same day. How about dropping www/squid33 and creating
> > a www/squid34 port. Then updating the www/squid port to 3.5.2.
>
> I would say this is a bad idea, as squid 3.5 does not work on FreeBSD
> 10.1 with GENERIC kernel. Furthermore, it won't be fixed with
> binary patches (ie. until 10.2 or 11.0).


> I think www/squid should be recommended squid version for FreeBSD
> users. It wouldn't be appropriate to recommend version which does not
> work without recompiling kernel.
>
> We discussed it not so long ago:
>
> https://www.mail-archive.com/search?l=freebsd-ports@freebsd.org&q=subject:%22Re%3A+www%2Fsquid+does+not+shutdown+via+rc%22&o=newest


The same kernel bug affects squid 3.4.12 (i.e., www/squid) in the same way.


>
> --
> Marko Cupać
> https://www.mimar.rs
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: squid 3.5 plans

2015-02-23 Thread Marko Cupać 
On Sat, 21 Feb 2015 08:28:40 +0100
Marko Cupać  wrote:

> On Thu, 19 Feb 2015 21:23:15 -0500
> Robert Simmons  wrote:
> 
> 
> > That is true. It looks like an update to both 3.5 and 3.4 were
> > released on the same day. How about dropping www/squid33 and
> > creating a www/squid34 port. Then updating the www/squid port to
> > 3.5.2.
> 
> I would say this is a bad idea, as squid 3.5 does not work on FreeBSD
> 10.1 with GENERIC kernel. Furthermore, it won't be fixed with
> binary patches (ie. until 10.2 or 11.0).
> 
> I think www/squid should be recommended squid version for FreeBSD
> users. It wouldn't be appropriate to recommend version which does not
> work without recompiling kernel.
> 
> We discussed it not so long ago:
> https://www.mail-archive.com/search?l=freebsd-ports@freebsd.org&q=subject:%22Re%3A+www%2Fsquid+does+not+shutdown+via+rc%22&o=newest

I have just installed www/squid33 because I wanted to avoid compiling
custom kernel, but apparently it does not shutdown via rc either.

I think we are closer to conclusion that no version of squid can be
controlled with included rc scripts on 10.1-pX. Perhaps users who
install squid on 10.1 should be warned somehow (pkg message or
something).
-- 
Marko Cupać
https://www.mimar.rs
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: squid 3.5 plans

2015-02-23 Thread Johan Hendriks 


Op 23-02-15 om 16:31 schreef Marko Cupać:

On Sat, 21 Feb 2015 08:28:40 +0100
Marko Cupać  wrote:


On Thu, 19 Feb 2015 21:23:15 -0500
Robert Simmons  wrote:



That is true. It looks like an update to both 3.5 and 3.4 were
released on the same day. How about dropping www/squid33 and
creating a www/squid34 port. Then updating the www/squid port to
3.5.2.

I would say this is a bad idea, as squid 3.5 does not work on FreeBSD
10.1 with GENERIC kernel. Furthermore, it won't be fixed with
binary patches (ie. until 10.2 or 11.0).

I think www/squid should be recommended squid version for FreeBSD
users. It wouldn't be appropriate to recommend version which does not
work without recompiling kernel.

We discussed it not so long ago:
https://www.mail-archive.com/search?l=freebsd-ports@freebsd.org&q=subject:%22Re%3A+www%2Fsquid+does+not+shutdown+via+rc%22&o=newest

I have just installed www/squid33 because I wanted to avoid compiling
custom kernel, but apparently it does not shutdown via rc either.

I think we are closer to conclusion that no version of squid can be
controlled with included rc scripts on 10.1-pX. Perhaps users who
install squid on 10.1 should be warned somehow (pkg message or
something).
Just a me to,  Squid33 on FreeBSD 10.1-RELEASE-p5 does not kill squid 
with /usr/local/etc/rc.d/squid stop


regards





___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: squid 3.5 plans

2015-02-23 Thread Nick Rogers 
On Mon, Feb 23, 2015 at 8:18 AM, Johan Hendriks 
wrote:

>
> Op 23-02-15 om 16:31 schreef Marko Cupać:
>
>> On Sat, 21 Feb 2015 08:28:40 +0100
>> Marko Cupać  wrote:
>>
>>  On Thu, 19 Feb 2015 21:23:15 -0500
>>> Robert Simmons  wrote:
>>>
>>>
>>>  That is true. It looks like an update to both 3.5 and 3.4 were
 released on the same day. How about dropping www/squid33 and
 creating a www/squid34 port. Then updating the www/squid port to
 3.5.2.

>>> I would say this is a bad idea, as squid 3.5 does not work on FreeBSD
>>> 10.1 with GENERIC kernel. Furthermore, it won't be fixed with
>>> binary patches (ie. until 10.2 or 11.0).
>>>
>>> I think www/squid should be recommended squid version for FreeBSD
>>> users. It wouldn't be appropriate to recommend version which does not
>>> work without recompiling kernel.
>>>
>>> We discussed it not so long ago:
>>> https://www.mail-archive.com/search?l=freebsd-ports@
>>> freebsd.org&q=subject:%22Re%3A+www%2Fsquid+does+not+
>>> shutdown+via+rc%22&o=newest
>>>
>> I have just installed www/squid33 because I wanted to avoid compiling
>> custom kernel, but apparently it does not shutdown via rc either.
>>
>> I think we are closer to conclusion that no version of squid can be
>> controlled with included rc scripts on 10.1-pX. Perhaps users who
>> install squid on 10.1 should be warned somehow (pkg message or
>> something).
>>
> Just a me to,  Squid33 on FreeBSD 10.1-RELEASE-p5 does not kill squid with
> /usr/local/etc/rc.d/squid stop
>

Yeah, the FreeBSD bug definitely affects all 3.x versions of squid,
possibly even the old 2.7 stuff. Nobody on the FreeBSD side yet seems to
think its a big enough of a regression to patch 10.1-RELEASE. I tried
raising the problem with the squid team, thinking perhaps there is some
workaround they could implement, but there was no response.

http://lists.squid-cache.org/pipermail/squid-users/2015-January/001745.html

For now the consensus is you must patch the 10.1 kernel for the shutdown
behavior to work correctly. And the problem is not unique to the rc script.


> regards
>
>
>
>
>
>
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Could someone with a commit bit check this PR: 196814

2015-02-23 Thread Freddie Cash 
It's been exactly 1 month since the patch[1] was posted and the port
maintainer approved it.  :)

There's also a separate PR[2] (197035) that details the issues (with
testing and logs and whatnot) that this PR should fix.

If there's anyone available that could commit this before the automated
package building on Wednesday, it would be muchly appreciated.

Thanks!


​[1] ​https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196814
​[2] ​https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197035


-- 
Freddie Cash
fjwc...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

[TESTING] BIND9 chroot trying to get back

2015-02-23 Thread Mathieu Arnold 
Hi,

While I don't see a real need for it, I've heard you, and I'm getting the
named chroot back in the port.  I've only worked on dns/bind99 for now, but
when it's ready, I'll apply the patch to all the available BIND9 ports that
there is.

The diff is available on our phabric, at
 you don't need an account to see, or
download the patch.  To download the patch, there is a "download raw diff"
on the right of the header.

Any testing done by someone else that me is appreciated, comments,
changes... are welcome too, as long as they are constructive ones.

WARNING: while I've tested it, it may unleash a troll that will your
configuration, or something, if you test on production servers, don't come
bitching about it breaking everything afterwards. :-)

-- 
Mathieu Arnold
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: squid 3.5 plans

2015-02-23 Thread Dewayne Geraghty 

On 24/02/2015 3:45 AM, Nick Rogers wrote:
> On Mon, Feb 23, 2015 at 8:18 AM, Johan Hendriks 
> wrote:
>
>> Op 23-02-15 om 16:31 schreef Marko Cupać:
>>
>>> On Sat, 21 Feb 2015 08:28:40 +0100
>>> Marko Cupać  wrote:
>>>
>>>  On Thu, 19 Feb 2015 21:23:15 -0500
 Robert Simmons  wrote:


  That is true. It looks like an update to both 3.5 and 3.4 were
> released on the same day. How about dropping www/squid33 and
> creating a www/squid34 port. Then updating the www/squid port to
> 3.5.2.
>
 I would say this is a bad idea, as squid 3.5 does not work on FreeBSD
 10.1 with GENERIC kernel. Furthermore, it won't be fixed with
 binary patches (ie. until 10.2 or 11.0).

 I think www/squid should be recommended squid version for FreeBSD
 users. It wouldn't be appropriate to recommend version which does not
 work without recompiling kernel.

 We discussed it not so long ago:
 https://www.mail-archive.com/search?l=freebsd-ports@
 freebsd.org&q=subject:%22Re%3A+www%2Fsquid+does+not+
 shutdown+via+rc%22&o=newest

>>> I have just installed www/squid33 because I wanted to avoid compiling
>>> custom kernel, but apparently it does not shutdown via rc either.
>>>
>>> I think we are closer to conclusion that no version of squid can be
>>> controlled with included rc scripts on 10.1-pX. Perhaps users who
>>> install squid on 10.1 should be warned somehow (pkg message or
>>> something).
>>>
>> Just a me to,  Squid33 on FreeBSD 10.1-RELEASE-p5 does not kill squid with
>> /usr/local/etc/rc.d/squid stop
>>
> Yeah, the FreeBSD bug definitely affects all 3.x versions of squid,
> possibly even the old 2.7 stuff. Nobody on the FreeBSD side yet seems to
> think its a big enough of a regression to patch 10.1-RELEASE. I tried
> raising the problem with the squid team, thinking perhaps there is some
> workaround they could implement, but there was no response.
>
> http://lists.squid-cache.org/pipermail/squid-users/2015-January/001745.html
>
> For now the consensus is you must patch the 10.1 kernel for the shutdown
> behavior to work correctly. And the problem is not unique to the rc script.
>
>
Yes - that's correct.  This was covered late January and 10.1Stable contains 
the fix.

(Cut/paste of an email between ports@ and John Marshall which explains the 
situation :)

On Tue, 27 Jan 2015, 00:29 +0900, Yasuhiro KIMURA wrote:

> Yes, this is bug. But it is bug of 10.1-RELEASE rather than squid.
> See following bug report:
>
> Bug 195802 - www/squid restarts after shutdown and dumps core
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195802

Thank you so much for posting this link!  Merging r275456 and r275502
from stable/10 to my releng/10.1 src tree and rebuilding and installing
the kernel, means that I can once again manage squid 3.4.n via the rc.d
script instead of a prescribed series of kill(1) commands.

...and thank you rea@ and kib@ for the patches!

-- John Marshall

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"