qzeitgeist failed to compile on FreeBSD 9-STABLE

Hi,

The port sysutils/qzeitgeist has failed to build on FreeBSD 9-STABLE.
The configure phase seem run without issue.
The build phase fails just after AUTOMOC4_EXECUTABLE-NOTFOUND was not found.

How can I fix it?

Cordially.

Q. Schwerkolt

===>  License LGPL21 accepted by the user
===>  Extracting for qzeitgeist-0.8.0
=> SHA256 Checksum OK for libqzeitgeist-0.8.0.tar.bz2.
=> SHA256 Checksum OK for zeitgeist-0.8.2.tar.gz.
cd /usr/ports/sysutils/qzeitgeist/work/zeitgeist-0.8.2 &&  /bin/cp zeitgeist/datamodel.py 
extra/ontology/*.trig  extra/rdfxml2py  extra/PythonSerializer.py  /usr/ports/sysutils/qzeitgeist/work/libqzeitgeist-0.8.0/scripts
===>  Patching for qzeitgeist-0.8.0
===>  Applying FreeBSD patches for qzeitgeist-0.8.0
/usr/bin/sed -i.bak -e '/\.pc/ s|pkgconfig|../libdata/pkgconfig|'  -e
's|share/qzeitgeist/cmake|lib/cmake/qzeitgeist|'  -e "/add_subdirectory(tests)/ d" 
/usr/ports/sysutils/qzeitgeist/work/libqzeitgeist-0.8.0/CMakeLists.txt 
/usr/ports/sysutils/qzeitgeist/work/libqzeitgeist-0.8.0/src/CMakeLists.txt  /usr/ports/sysutils/qzeitgeist/work/libqzeitgeist-0.8.0/QZeitgeistConfig.cmake.in
/usr/bin/sed -i.bak -e '/import _config/ d'  -e 's|_config.datadir,
"zeitgeist/ontology/zeitgeist.py"|runpath, "zeitgeist.py"|'  /usr/ports/sysutils/qzeitgeist/work/libqzeitgeist-0.8.0/scripts/datamodel.py
/usr/bin/sed -i.bak -e 's|zeitgeist.datamodel|datamodel|'  /usr/ports/sysutils/qzeitgeist/work/libqzeitgeist-0.8.0/scripts/onto2cpp.py
/usr/bin/sed -i.bak -e 's|/usr/bin/python|/usr/local/bin/python2.7|g'  /usr/ports/sysutils/qzeitgeist/work/libqzeitgeist-0.8.0/scripts/rdfxml2py
===>   qzeitgeist-0.8.0 depends on executable: rapper - found

TeXLive merge into FreeBSD ports tree - is this going to happen or not?

Hi FreeBSD fellows,

Those who are using LaTeX on FreeBSD must know that tetex has been
discontinued years ago and that TeXLive is now recommended, however TeXLive
has never been merged in the ports tree on FreeBSD and that tetex is still
used on FreeBSD ports. Although there have been some "customized" work so
that FreeBSD users can install and use TeXLive on FreeBSD machine (for
example, http://code.google.com/p/freebsd-texlive/wiki/Installing), this is
quite confusing and may still cause conflict on the system side when using
or maintaining it.

There has also been years of gossips that a Japanese developer Hiroki Sato
(hrs <at> freebsd) has been working on this matter for the last years and
therefore the FreeBSD admin panel don't want anyone else to work on this
and merge it into the ports tree.

I actually contacted Hiroki Sato in the beginning of last year (2011)
regarding this, and in his reply he said that there had been several
technical issues but most of them had been solved and almost ready to merge
into the port tree, and that he was planning to go forward after the
8.2/7.4 releases (one or two weeks later from that time stage) are out.
However, more than a year has passed since then and still nothing happened.
I tried to contact him several times after that (email, tweet, etc) but
haven't heard anything back from him at all.

Is TeXLive really going to be merged into the FreeBSD ports tree as Hiroki
Sato mentioned previously? Or is this just a myth??

I am now thinking that this should be put into the "FreeBSD Project ideas
List" [http://wiki.freebsd.org/IdeasPage].

libX11 and clang: compile error

Hi!

Somewhere in config* or Makefile are a hardcoded /usr/bin/cpp ...

Script started on Sat May 26 10:51:06 2012

op has logged on :0 from local.
root@opn libX11# make

===>  License MIT accepted by the user
===>  Extracting for libX11-1.4.4,1
=> SHA256 Checksum OK for xorg/lib/libX11-1.4.4.tar.bz2.
===>  Patching for libX11-1.4.4,1
===>   libX11-1.4.4,1 depends on file: /usr/local/libdata/pkgconfig/xcb.pc - found
===>   libX11-1.4.4,1 depends on file: /usr/local/share/aclocal/xorg-macros.m4 - found
===>   libX11-1.4.4,1 depends on file: /usr/local/libdata/pkgconfig/bigreqsproto.pc - found
===>   libX11-1.4.4,1 depends on file: /usr/local/libdata/pkgconfig/xcmiscproto.pc - found
===>   libX11-1.4.4,1 depends on file: /usr/local/libdata/pkgconfig/xextproto.pc - found
===>   libX11-1.4.4,1 depends on file: /usr/local/libdata/pkgconfig/xtrans.pc - found
===>   libX11-1.4.4,1 depends on file: /usr/local/libdata/pkgconfig/kbproto.pc - found
===>   libX11-1.4.4,1 depends on file: /usr/local/libdata/pkgconfig/inputproto.pc - found
===>   libX11-1.4.4,1 depends on file: /usr/local/libdata/pkgconfig/xf86bigfontproto.pc - found
===>   libX11-1.4.4,1 depends on file: /usr/local/libdata/pkgconfig/xau.pc - found
===>   libX11-1.4.4,1 depends on file: /usr/local/libdata/pkgconfig/xdmcp.pc - found
===>   libX11-1.4.4,1 depends on file: /usr/local/libdata/pkgconfig/xproto.pc - found
===>   libX11-1.4.4,1 depends on executable: pkg-config - found
===>  Configuring for libX11-1.4.4,1
checking build system type... amd64-portbld-freebsd9.0
checking host system type... amd64-portbld-freebsd9.0
checking for gcc... cc

kdebase3 + clang

Hi!

The attached patch make kdebase3 compilable with clang-3.1 on FreeBSD 9-STABLE.

_______________________________________________
freebsd-ports <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe <at> freebsd.org"

KDE 4.8

I use portmaster for KDE 4.8 updtae and it stopped:

The devel/kdebindings4-python port has been deleted: kdebindings ports have 
been refactored.

What do I need to do, please?

Thanks in advance.

Mitja
--------
http://jpgmag.com/people/lumiwa
_______________________________________________
freebsd-ports <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe <at> freebsd.org"

graphics/djvulibre

Are there many users of the QT3 djvulibre GUI in
ports/graphics/djvulibre who would have difficulties switching to one
of the other GUIs?  The upstream developers have removed it from the
latest versions of the djvulibre distribution, and I am wondering
whether it is worth some special effort to retain it when I update the
djvulibre ports.

b.
_______________________________________________
freebsd-ports <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe <at> freebsd.org"

Xorg freezes since last update

Hi there!

I am running a box with FreeBSD 9.0-Release amd64 and a GeForce GTS450.
This setup is was running for several months without any issues.

Since the last Xorg-update I have freezes of XOrg every day (minimum
one, sometimes more). I first did an update without setting
"WITH_NEW_XORG". I got failures. Later I set "WITH_NEW_XORG" and did a
build of xorg and all depended ports. Again freezes. I switched back
and disabled "WITH_NEW_XORG" and again I build xorg and all
dependencies.
I was using the current nvidia-driver from the ports-tree. I switched
to the current betra-driver. Again freezes.
We tried shrinking the "physmem"-sysctl.

Freezes look like this: The screen does not update any windows. The
mouse can be moved but it can't interact with the GUI. If the screen
was black (screensaving) it stays black. If the screen showed a desktop
this will be shown (no screensaver oder backlight-offs). Pressing
CTRL+ALT+Fx does nothing.
The only thing I can do is to log in with my smartphone using ssh and
kill Xorg. This needs a lot of time but then it stops.

The last messages in the XOrg-log are:

(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(WW) May 25 21:13:00 NVIDIA(0): WAIT (2, 6, 0x8000, 0x00000858, 0x000021a4)
(WW) May 25 21:13:07 NVIDIA(0): WAIT (1, 6, 0x8000, 0x00000858, 0x000021a4)
(WW) May 25 21:13:10 NVIDIA(0): WAIT (2, 6, 0x8000, 0x00000858, 0x00003d50)
(WW) May 25 21:13:17 NVIDIA(0): WAIT (1, 6, 0x8000, 0x00000858, 0x00003d50)

You can earn more! We offer a personal decision from medicine clinic.

I would like to take this time to welcome you to our hiring process 
and give you a brief synopsis of the position's benefits and requirements.

If you are taking a career break, are on a maternity leave,
recently retired or simply looking for some part-time job, this position is for you.

Occupation: Flexible schedule 2 to 8 hours per day. We can guarantee a minimum 20 hrs/week occupation
Salary: Starting salary is 2000 EURO per month plus commission, paid every month.
Business hours: 9:00 AM to 5:00 PM, MON-FRI, 9:00 AM to 1:00 PM SAT or part time (Europe time).

Region: Europe.

Please note that there are no startup fees or deposits to start working for us.

To request an application form, schedule your interview and receive more information about this position 
please reply to Jerold <at> topeuropajobs.com,with your personal identification number for this position
IDNO: 7450

_______________________________________________
freebsd-ports <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe <at> freebsd.org"

Re: bash 4.2 patchlevel 28

On Fri, May 25, 2012 at 04:58:48PM +0100, Chris Rees wrote:
> 
> 
> Jason Hellenthal <jhellenthal <at> dataix.net> wrote:
> 
> >
> >
> >On Fri, May 25, 2012 at 07:44:39AM +0200, Trond Endrest?l wrote:
> >> On Thu, 24 May 2012 13:07-0700, Sean Bruno wrote:
> >> 
> >> > Noted that the following syntax is broken somewhere between 4.2
> >> > patchlevel 10 and 28.  I'm sure its because we shouldn't be doing
> >that
> >> > over here at big purple, but we do ... and its a PITA.  I'm
> >bisecting to
> >> > find out what is going on.
> >> > 
> >> > test:
> >> > VARIABLE="$(uname)"
> >> > bash: command substitution: line 3: syntax error near unexpected
> >token
> >> > `)'
> >> > bash: command substitution: line 3: `uname)"'
> >> > 
> >> > Odd, but his works at patchlevel 10
> >> 
> >> I'm unable to reproduce this behaviour on one of my systems:
> >> 
> >> trond <at> enterprise:~>bash --version

Ports with duplicate LATEST_LINKs

Dear port maintainers,

The following list includes ports maintained by you that have duplicate
LATEST_LINK values.  They should either be modified to use a unique
LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting
each other in the packages/Latest directory.  If your ports conflict with
ports maintained by another person, please coordinate your efforts with
them.

Thanks,
Erwin "Annoying Reminder Guy III" Lansing

LATEST_LINK          PORTNAME                       MAINTAINER          
==========================================================================
kdeaccessibility     accessibility/kdeaccessibility4 kde <at> FreeBSD.org     
kdeaccessibility     accessibility/kdeaccessibility ports <at> FreeBSD.org   

Total: 2 ports
_______________________________________________
freebsd-ports <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe <at> freebsd.org"

Packages target

Hi,

over the past few weeks I've been using the ports system without any
ports-mgmt tool and have become utterly convinced that the PACKAGE_SEQ
needs to be PACKAGE_SUSEQ for all but package-message.
The primary reason is that the install target can install hierarchies or
files not readable by the unprivileged user and as such the package
target will fail.

I'm not aware of any downsides to making this change in bpm or am I
overlooking something?
--

-- 
Mel
_______________________________________________
freebsd-ports <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe <at> freebsd.org"