Re: Fwd: 2017-02-18 Update to Qt 4 and Qt 5

[Bartosz Fabianowski]

qtchooser conflicts with a number of Qt 4 ports, because they installed 
binaries into /usr/local/bin that qtchooser wants to replace with its 
own scripts now.


I just nuked all conflicting ports, installed qtchooser and reinstalled 
the ports afterward.


- Bartosz

On 19/02/2017 12:25, Raphael Kubo da Costa wrote:

Robert Burmeister  writes:


k...@freebsd.org is not accepting mail


 UPDATING
 Following what is already done in Qt 5, the Qt 4 ports no longer install
 their binaries into ${LOCALBASE}/bin (which is "/usr/local/bin" in most
 cases). Additionally, the "-qt4" suffix has been dropped from the file names
 of the binaries that had it, such as "qmake-qt4".



Could we have portupgrade instructions?


We'd be more than glad to add those if someone can provide them; I have
not used portupgrade myself since at least 2009, so it's hard for me to
provide any instructions.


Neither QT4 nor QT5 will build on my FreeBSD 11 i386 system.


Can you clarify? What errors are you seeing?


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

firefox 3.5 dying with __gnu_cxx::__concurrence_lock_error

[Bartosz Fabianowski]

Heya

After bringing all ports on my 7-STABLE i386 machine up to date, Firefox
3.5 now refuses to start. The /usr/local/bin/firefox3 wrapper script
launches the binary for a short moment, the main window may even pop up
for a second but then it dies with:

terminate called after throwing an instance of
'__gnu_cxx::__concurrence_lock_error'
  what():  __gnu_cxx::__concurrence_lock_error
Abort trap

From googling for the error I gather this is likely to be caused by an
incompatible combination of threaded and unthreaded code somewhere - but
I have no idea where to look for the source of the error.

I installed about four weeks' worth of port updates in the last couple
of days, all by building from source. Throughout most of the process,
Firefox 3.5 continued to run but then some update made it crash with
this error message. Unfortunately, I updated over 100 ports and have no
idea which one is at fault. I tried recompiling some of the most likely
candidates (including www/firefox35 itself) but the error persists.

Thunderbird is installed on the same machine and runs just fine - so it
is not like gecko in general refuses to work on this machine; it is
something specific to Firefox 3.5...

Any insight into how to track this down would be greatly appreciated.

Thanks,
- Bartosz

1. uname -a

FreeBSD takahe.local 7.2-STABLE FreeBSD 7.2-STABLE #0: Mon Jul  6
11:01:19 IST 2009 r...@takahe.local:/usr/obj/usr/src/sys/TAKAHE  i386

2. Port version

# $FreeBSD: ports/www/firefox35/Makefile,v 1.180 2009/08/19 01:58:37
beat Exp $
___
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: [HEADS UP] Re: setting gcc42 as default compiler

[Bartosz Fabianowski]

Are you planning to fix compilation with gcj as part of this commit? It 
has been broken for some time now. While I haven't had the time to do a 
test run with the most recent port yet, I don't expect the problems to 
have miraculously gone away:


http://www.freebsd.org/cgi/query-pr.cgi?pr=107645

- Bartosz
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

170kB patch - how to handle?

[Bartosz Fabianowski]

Good day

I would like to improve the audio/libvorbis port by optionally patching 
in the aoTuV psychoacoustics, which are considered to be superior to 
stock libvorbis. However, the patch file that does this is ~170kB in 
size. I am wondering whether it is OK to put such a large file directly 
into the ports tree or if it should be downloaded as a distfile by each 
user. Is there any guideline on which would be the correct method? I 
would hate for my suggestion to be rejected by the port's maintainer due 
to me getting a formality like this wrong.


Thanks,
- Bartosz
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

portupgrade-2.2.2_1,2 corrupts portsdb

[Bartosz Fabianowski]

Hi all

As part of the daily portupgrade run on my 6-STABLE box, I upgraded 
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried 
running this version, I got the following error message:


%portupgrade -ai
---  Session started at: Wed, 31 Jan 2007 15:44:44 +
[missing key: categories] [Updating the portsdb format:bdb_btree in 
/usr/ports ... - 15487 port entries found 
.1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000 
. done]

missing key: categories: Cannot read the portsdb!
---  Session ended at: Wed, 31 Jan 2007 15:44:50 + (consumed 00:00:05)
/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:548:in `open_db': database 
file error (PortsDB::DBError)

from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:702:in `port'
from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:890:in 
`all_depends_list'
from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:809:in 
`tsort_build'

from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:801:in `each'
from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:801:in 
`tsort_build'

from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:823:in `sort_build'
from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:827:in 
`sort_build!'

from /usr/local/sbin/portupgrade:721:in `main'
from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize'
from /usr/local/sbin/portupgrade:220:in `new'
from /usr/local/sbin/portupgrade:220:in `main'
from /usr/local/sbin/portupgrade:2084

Apparently, the portsdb database is corrupted somehow, gets rebuilt but 
is still not acceptable. According to the error message, a key named 
categories seems to be missing from some table. Has anyone else 
experience this? Is there a workaround or a fix?


- Bartosz
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: portupgrade-2.2.2_1,2 corrupts portsdb

[Bartosz Fabianowski]

Something broken in INDEX :(


For the record: I am using p5-FreeBSD-Portindex-1.8 to build INDEX-6 and 
have received a reply off list from somebody who has the same problems 
with an INDEX-6 retrieved via make fetchindex. So, it's not just a 
single broken INDEX-6 file on the server that needs rebuilding, it's 
something deeper within the ports infrastructure that will keep 
corrupting index builds until it gets fixed.


- Bartosz
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: openoffice.org-2.0 does not build on amd64 with 6.1

[Bartosz Fabianowski]

It seems that you have run into a know problem with the OpenOffice.org 
build system - it does not work when file names become too long. In the 
error message you posted, 
file:///mnt/files/usr/ports/editors/openoffice.org-2.0/work/OOD680_m5/udkapi/unxfbsdx.pro/ucr/com/sun/star/uno/Exception._idlc_ 
is clearly truncated and is also precisely 128 characters long. While 
your NFS mount point /mnt/files/ adds only 11 characters to the file 
name, this may be enough to overflow a fixed 128 character buffer used 
by the idlc. Try mounting the NFS file system at say /mnt or even /m 
to keep the file names as short as possible.


- Bartosz
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]