Updating x11-toolkits/scintilla

[Naram Qashat]

Hello everyone,

I have been pretty behind on updating ports I maintain so I have been 
looking into updating x11-toolkits/scintilla from the current version in 
ports of 4.3.2 to the current actual version of 4.4.5. It appears as if 
scintilla is working towards making the lexers part of the library a 
separate component being named Lexilla. Although not planned to be the 
actual norm until Scintilla 5.0 comes out, currently it builds alongside 
the main Scintilla library.


In the ports tree, the only software utilizing x11-toolkits/scintilla is 
editors/scite (which I also maintain alongside it). The strange thing is 
that the Scintilla library currently includes the lexers AND builds the 
separate Lexilla library, and while SciTE by default statically links to 
the Scintilla library, it can at runtime load the Lexilla library (I'm 
not really sure why or how this would work if the main library also 
includes the same functionality).


The port for Scintilla was being modified to produce a separate lexer 
library anyways (although named scintilla_lexers instead of lexilla), 
and the SciTE port was being modified to link to a shared Scintilla 
library instead of the static library it expects.


Since SciTE is the only thing in the ports tree utilizing Scintilla 
directly, I am unsure how many projects external to the ports tree are 
being used by others with also utilize the Scintilla library. As such, I 
am wanting to change things up with the port so it produces the 
Scintilla and Lexilla libraries as the author has set out (so basically, 
scintilla and lexilla instead of scintilla and scintilla_lexers), and 
then making SciTE still continue with linking to the shared Scintilla 
library instead of the static one.


If anyone on the mailing list here does use the library as built by 
x11-toolkits/scintilla and would be affected if I do the above change 
for the installed shared libraries, please let me know. Otherwise I will 
be attempting to go forward with the change, especially since once the 
author releases Scintilla 5.0, it will be the norm anyways.


Thanks in advance,
Naram "CyberBotX" Qashat
___
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/openblas" will not build under poudriere

[Naram Qashat]

On 2019-12-04 09:27, Carmel NY wrote:

Attempting to build "math/openblas" using poudriere results in this
error message: Ignoring: has to be built manually: Optimizes for the
build machine. I can build it manually, however. Is this a bug or a
design feature?


Just a quick glance at the Makefile for math/openblas shows that if the 
DYNAMIC_ARCH option is turned off, then that message would happen. It 
should be default, though, from what I can tell.



The complete log of the failed poudriere build follows.

build started at Wed Dec  4 09:10:51 EST 2019
port directory: /usr/ports/math/openblas
package name: openblas-0.2.20_11,1
building for: FreeBSD amd64-default 11.3-RELEASE-p5 FreeBSD
11.3-RELEASE-p5 amd64 maintained by: phd_kimberl...@yahoo.co.jp
Makefile ident:  $FreeBSD: head/math/openblas/Makefile 516146
2019-10-31 13:21:45Z arrowd $ Poudriere version: 3.3.99.20190828
Host OSVERSION: 1103000
Jail OSVERSION: 1103000
Job Id:

---Begin Environment---
SHELL=/bin/csh
OSVERSION=1103000
UNAME_v=FreeBSD 11.3-RELEASE-p5
UNAME_r=11.3-RELEASE-p5
BLOCKSIZE=K
MAIL=/var/mail/root
STATUS=1
HOME=/root
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
USER=root
LIBEXECPREFIX=/usr/local/libexec/poudriere
POUDRIERE_VERSION=3.3.99.20190828
MASTERMNT=/usr/local/poudriere/data/.m/amd64-default/ref
POUDRIERE_BUILD_TYPE=bulk
PACKAGE_BUILDING=yes
SAVED_TERM=xterm-color
PWD=/usr/local/poudriere/data/.m/amd64-default/ref/.p
P_PYTHON_MAJOR_VER=3
P_PORTS_FEATURES=FLAVORS SELECTED_OPTIONS
MASTERNAME=amd64-default
SCRIPTPREFIX=/usr/local/share/poudriere
OLDPWD=/tmp
SCRIPTPATH=/usr/local/share/poudriere/bulk.sh
POUDRIEREPATH=/usr/local/bin/poudriere
P_PYTHON3_DEFAULT=3.6
P_PYTHON_DEFAULT_VERSION=
---End Environment---

---Begin Poudriere Port Flags/Env---
PORT_FLAGS=
PKGENV=
FLAVOR=
DEPENDS_ARGS=
MAKE_ARGS=
---End Poudriere Port Flags/Env---

---Begin OPTIONS List---
===> The following configuration options are available for
openblas-0.2.20_11,1: AVX=off: Support Advanced Vector Extensions (AVX)
 AVX2=off: Support Advanced Vector Extensions 2 (AVX2)
 DYNAMIC_ARCH=off: Support multiple CPU types on i386 and amd64
 INTERFACE64=off: Use 8 byte integers on 64-bit architectures
 OPENMP=off: Use OpenMP for threading
===> Use 'make config' to modify these settings
---End OPTIONS List---

--MAINTAINER--
phd_kimberl...@yahoo.co.jp
--End MAINTAINER--

--CONFIGURE_ARGS--

--End CONFIGURE_ARGS--

--CONFIGURE_ENV--
F77="gfortran9" FC="gfortran9" FFLAGS="-O
-Wl,-rpath=/usr/local/lib/gcc9"
FCFLAGS="-Wl,-rpath=/usr/local/lib/gcc9" MAKE=gmake
ac_cv_path_PERL=/usr/local/bin/perl
ac_cv_path_PERL_PATH=/usr/local/bin/perl  PERL_USE_UNSAFE_INC=1
XDG_DATA_HOME=/wrkdirs/usr/ports/math/openblas/work
XDG_CONFIG_HOME=/wrkdirs/usr/ports/math/openblas/work
HOME=/wrkdirs/usr/ports/math/openblas/work TMPDIR="/tmp"
PATH=/wrkdirs/usr/ports/math/openblas/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
SHELL=/bin/sh CONFIG_SHELL=/bin/sh --End CONFIGURE_ENV--

--MAKE_ENV--
F77="gfortran9" FC="gfortran9" FFLAGS="-O
-Wl,-rpath=/usr/local/lib/gcc9"
FCFLAGS="-Wl,-rpath=/usr/local/lib/gcc9" PERL_USE_UNSAFE_INC=1
XDG_DATA_HOME=/wrkdirs/usr/ports/math/openblas/work
XDG_CONFIG_HOME=/wrkdirs/usr/ports/math/openblas/work
HOME=/wrkdirs/usr/ports/math/openblas/work TMPDIR="/tmp"
PATH=/wrkdirs/usr/ports/math/openblas/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
NO_PIE=yes MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh
NO_LINT=YES ADDR2LINE="/usr/local/bin/addr2line" AR="/usr/local/bin/ar"
AS="/usr/local/bin/as" CPPFILT="/usr/local/bin/c++filt"
GPROF="/usr/local/bin/gprof" LD="/usr/local/bin/ld"
NM="/usr/local/bin/nm" OBJCOPY="/usr/local/bin/objcopy"
OBJDUMP="/usr/local/bin/objdump" RANLIB="/usr/local/bin/ranlib"
READELF="/usr/local/bin/readelf" SIZE="/usr/local/bin/size"
STRINGS="/usr/local/bin/strings" PREFIX=/usr/local
LOCALBASE=/usr/local  CC="cc" CFLAGS="-O2 -pipe
-fstack-protector-strong -fno-strict-aliasing "  CPP="cpp" CPPFLAGS=""
LDFLAGS=" -Wl,-rpath=/usr/local/lib/gcc9  -L/usr/local/lib/gcc9
-B/usr/local/bin -fstack-protector-strong " LIBS=""  CXX="c++"
CXXFLAGS="-O2 -pipe -fstack-protector-strong -fno-strict-aliasing  "
MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install  -s -m 555"
BSD_INSTALL_LIB="install  -s -m 0644"  BSD_INSTALL_SCRIPT="install  -m
555"  BSD_INSTALL_DATA="install  -m 0644"  BSD_INSTALL_MAN="install  -m
444" --End MAKE_ENV--

--PLIST_SUB--
 DYNARCH="@comment " OSREL=11.3 PREFIX=%D LOCALBASE=/usr/local
RESETPREFIX=/usr/local LIB32DIR=lib PERL_VERSION=5.30.1  PERL_VER=5.30
PERL5_MAN1=lib/perl5/site_perl/man/man1
PERL5_MAN3=lib/perl5/site_perl/man/man3  SITE_PERL=lib/perl5/site_perl
SITE_ARCH=lib/perl5/site_perl/mach/5.30 DOCSDIR="share/doc/openblas"
EXAMPLESDIR="share/examples/openblas"  DATADIR="share/openblas"
WWWDIR="www/openblas"  ETCDIR="etc/openblas" --End PLIST_SUB--

--SUB_LIST--
 PREFIX=/usr/local LOCALBASE=/usr/local
DATA

Looking for committer for Scintilla/SciTE update

[Naram Qashat]

Could I get a ports committer to look over 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238505 (update of 
x11-toolkits/scintilla and editors/scite) please? It has been about a 
month since I submitted it originally and I've had to update it a few 
times since then.


Thanks,
Naram Qashat
___
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"

Unable to build ftp/curl for i386 in poudriere jail on amd64 host

[Naram Qashat]

I use an i386 poudriere jail on my amd64 host to build my own copy of 
i386-wine-devel to use on the host. Recently, though, when that jail 
tries to build cURL, it gives me an error of "curl: error initializing 
curl library" before the build fails, as seen here:


http://kirby.cyberbotx.com:8765/poudriere/data/local_i386-default/2019-02-03_00h24m34s/logs/errors/curl-7.63.0_1.log

I have attempted this both with and without ccache support, but the same 
error occurs both ways. I'm at a loss as to what is happening. ftp/curl 
builds just fine for amd64 and even builds fine in my aarch64 poudriere 
jail, so only the i386 jail is failing on me.


Any help would be appreciated. If more info is needed, I will do my best 
to provide it.


Thanks,
Naram Qashat
___
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: www/waterfox: Why is it deprecated?

[Naram Qashat]

On 2018-02-28 06:22, Naram Qashat wrote:

Hi Jan,

I was wondering why www/waterfox currently has a deprecation notice
for 2018-03-20 of "Temporary experiment". Are there no plans to keep
Waterfox in the ports tree as an alternative to Firefox? The project
appears to be an active fork of Firefox.

Thanks,
Naram Qashat


Hi Jan,

I never got a reply to this inquiry, and the port looks to be set to 
expire in a week. I notice you still commit changes to the port as well. 
Is the port really going to be removed next week?


Thanks,
Naram Qashat
___
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"

www/waterfox: Why is it deprecated?

[Naram Qashat]

Hi Jan,

I was wondering why www/waterfox currently has a deprecation notice for 
2018-03-20 of "Temporary experiment". Are there no plans to keep 
Waterfox in the ports tree as an alternative to Firefox? The project 
appears to be an active fork of Firefox.


Thanks,
Naram Qashat
___
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"

Looking to give up maintainership of print/cups-filters

[Naram Qashat]

Hello all,

I've been the maintainer of the print/cups-filter port for a while now, 
but I'd like to give it up to someone else. It does need an update 
currently (it is at 1.16.0 but needs to be updated to 1.19.0). I just 
don't have the means to deal with the potential problems that each 
update bring up. So, if anyone wants to take over maintainership of the 
port and update it, please submit a PR for it and I'll give the port up.


Thanks,
Naram Qashat
___
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"

Unable to start 11.0-RELEASE aarch64 jail created by poudriere

[Naram Qashat]

I have been attempting to make an 11.0-RELEASE jail for aarch64 to use 
with poudriere, with my world source being existing sources in /usr/src, 
but I am unable to start the resulting jail. I am currently using 
poudriere-devel 3.1.99.20170803 and use UFS for the file system (I do 
not use ZFS at all). I have qemu-user-static installed and can verify 
that there is an aarch64 entry in 'binmiscctl list'. The following are 
the steps I have taken:


1) Made sure that there is no existing jail named local_aarch64 (the 
name I was using for the jail) in poudriere.


2) Made sure to delete my /usr/obj/arm64.aarch64 directory.

3) Built the aarch64 world from /usr/src using 'make -j4 buildworld 
TARGET_ARCH=aarch64'.


4) Created the poudriere jail using 'poudriere jail -c -J 4 -j 
local_aarch64 -a arm64.aarch64 -f none -m src=/usr/src -x'. (I was told 
on IRC by RootWyrm that poudriere-devel and the -x flag when creating 
the jail as required for aarch64.)


5) Attempting to chroot into the resulting jail using 'chroot 
/usr/local/poudriere/jails/local_aarch64 /bin/sh' results in this:

chroot: /bin/sh: No such file or directory

6) Attempting to start the jail with poudriere using 'poudriere jail -s 
-j local_aarch64' results in this:

[00:00:00] Cross-building ports for arm64.aarch64 on amd64 requires QEMU
[00:00:00] Creating the reference jail... done
[00:00:36] Mounting system devices for local_aarch64-default
[00:00:36] Mounting ports/packages/distfiles
[00:00:36] Mounting packages from:
[00:00:36] Setting up native-xtools environment in jail... done
[00:00:36] Raising MAX_EXECUTION_TIME and NOHANG_TIME for QEMU
[00:00:36] Copying latest version of the emulator from: 
/usr/local/bin/qemu-aarch64-static
[00:00:36] Copying aarch64-binutils ld from 
/usr/local/aarch64-freebsd/bin/ld
[00:00:36] Appending to make.conf: 
/usr/local/etc/poudriere.d/local_aarch64-make.conf
/etc/resolv.conf -> 
/usr/local/poudriere/data/.m/local_aarch64-default/ref/etc/resolv.conf

[00:00:36] Starting jail local_aarch64-default
/etc/rc.subr: /bin/ps: not found
/etc/rc.subr: /bin/ps: not found
eval: /sbin/ldconfig: not found
eval: sysctl: not found
eval: sysctl: not found
eval: sysctl: not found
/usr/ports/Mk/Scripts/ports_env.sh: grep: not found
sh: /usr/bin/uname: not found
make: "/usr/ports/Mk/bsd.port.mk" line 1128: warning: "/usr/bin/uname 
-s" returned non-zero status

sh: /usr/bin/uname: not found
make: "/usr/ports/Mk/bsd.port.mk" line 1133: warning: "/usr/bin/uname 
-r" returned non-zero status
make: "/usr/ports/Mk/bsd.port.mk" line 1177: UNAME_r () and OSVERSION 
(1100122) do not agree on major version number.

jexec: execvp: ldconfig: No such file or directory

7) Attempting to run any executables created for the jail:
# /usr/local/poudriere/jails/local_aarch64/usr/bin/ldd
/usr/local/poudriere/jails/local_aarch64/usr/bin/ldd: Command not found.
# qemu-aarch64-static 
/usr/local/poudriere/jails/local_aarch64/usr/bin/ldd

Unable to load interpreter
# /usr/local/poudriere/jails/local_aarch64/rescue/ls /var/empty
/usr/local/poudriere/jails/local_aarch64/rescue/ls: Command not found.
# qemu-aarch64-static /usr/local/poudriere/jails/local_aarch64/rescue/ls 
/var/empty

#
(In other words, only running a statically linked executable with 
qemu64-aarch64-static works, all other ways do not work. All the files, 
when checked with the 'file' command, do say they are built for ARM 
aarch64 as opposed to the host's x86-64.)


As verification, this is within the output of 'binmiscctl list':
[...]
name: aarch64
interpreter: /usr/local/bin/qemu-aarch64-static
flags: ENABLED USE_MASK
magic size: 20
magic offset: 0
magic: 0x7f 0x45 0x4c 0x46  0x02 0x01 0x01 0x00  0x00 0x00 0x00 0x00
   0x00 0x00 0x00 0x00  0x02 0x00 0xb7 0x00
mask:  0xff 0xff 0xff 0xff  0xff 0xff 0xff 0x00  0xff 0xff 0xff 0xff
   0xff 0xff 0xff 0xff  0xfe 0xff 0xff 0xff
[...]

There were no errors in the buildworld nor in the jail creation via 
poudriere. Prior to RootWyrm's suggestion of using poudriere-devel and 
the -x flag for jail creation, I had been using poudriere 3.1.19 and 
creating the jail without the -x flag. In that scenario, I was able to 
successfully chroot into the jail's file system (step 5 above) and I was 
able to attempt bulk port building (technically step 6 above although I 
had not done that with the 3.1.19 scenario because it actually was 
building ports for a while), but building ports failed after a while 
with execvp errors (one of which was 'jexec: execvp: /usr/bin/limits: No 
such file or directory') and then finally resulted in all 4 builders 
getting stuck in the clean_pool status before I stopped the jail.


Thanks,
Naram Qashat
___
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"

poudriere 3.1.15 and 3.1.16 builders get stuck in {balancing,clean}_pool status

[Naram Qashat]

I have been transitioning to using poudriere to build ports for my 
system with custom options. Everything has been working well until I 
updated poudriere to 3.1.15 and then later 3.1.16.


My host is running FreeBSD 11.0-RELEASE-p8 amd64, and the poudriere jail 
is running the same version (using the /usr/src / /usr/obj from the 
host). The host has a 6-core Intel i7 (so FreeBSD treats this at 12 CPU 
cores).


When I start a bulk build, I notice that sometimes, after a port has 
finished building, the status of a builder will go to balancing_pool or 
clean_pool instead of idle. Some of the ports that were built will then 
show up as failed AND built, with the error in the failed section 
showing a phase of balancing_pool and the build log showing "Build 
crashed: balancing_pool" near the very end. Eventually it gets to a 
state where poudriere no longer continues building ports, with all the 
builders in either the balancing_pool status or clean_pool status.


I noticed this originally with poudriere 3.1.15 when attempting to just 
bulk build poudriere alone (to get 3.1.16), but at that time I didn't 
notice what state the builder was in before I killed the bulk build. I 
had to update poudriere by building from the port's directory directly. 
Then when I was on poudriere 3.1.16 and started a brand new bulk build, 
that is when I noticed the balancing_pool and clean_pool statuses.


This doesn't happen if I downgrade back to poudriere 3.1.14 (using 
portdowngrade to grab a copy of the port from before 3.1.15).


The relevant changes in my poudriere.conf from the sample version:

* Not using ZFS (NO_ZFS=yes)
* Using portlint (USE_PORTLINT=yes)
* CHECK_CHANGED_OPTIONS set to verbose
* CHECK_CHANGED_DEPS set to yes
* Setting a PKG_REPO_SIGNING_KEY to use the packages built by poudriere 
through pkg

* Only using 4 builders instead of the default 12 (PARALLEL_JOBS=4)
* Save failed WRKDIRs (SAVE_WRKDIR=yes)
* Only allowing MAKE_JOBS on chromium, clang* and llvm* 
(ALLOW_MAKE_JOBS_PACKAGES="chromium clang* llvm*")

* Timestamp my logs (TIMESTAMP_LOGS=yes)

I believe I created the poudriere setup with 3.1.14 or maybe even 
3.1.13. (It was only created within the last couple weeks.)


If more information is needed to diagnose this, please let me know.

Thanks,
Naram Qashat
___
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: Cannot build lang/phantomjs

[Naram Qashat]

On 2016-09-21 15:26, Mark Felder wrote:

On Wed, Sep 21, 2016, at 12:52, Naram Qashat wrote:

I can't seem to get the phantomjs port to build for me under FreeBSD
10.3. I have lang/gcc installed (so I have gcc48 and g++48) and clang 
is
the base compiler. It seems that it is trying to use g++48, but there 
is

no freebsd-g++48 mkspec and it fails to even start building.

I've even tried to set CC and CXX manually but that doesn't help 
because

of the mkspec issue. It seems to always try using gcc48 and g++48
regardless of what CC and CXX are set to.



Do you have more details about how you're trying to build it? It builds
with clang, not gcc. It should not be attempting to use gcc at all.


I'm building using portupgrade, but the problem happens even if I build 
directly with make from /usr/ports/lang/phantomjs too. I use portconf, 
but even with all the options commented out in there, it still doesn't 
build.



Here is the cluster build log for 10.1 amd64 (10.1 is build target for
all packages used for 10.1, 10.2, and 10.3)

http://beefy2.nyi.freebsd.org/data/101amd64-quarterly/422328/logs/phantomjs-2.0.0_4.log


Looking at that build log, I see a difference when it checks for g++ and 
g++48. On my system, since I have g++ and g++48 from lang/gcc, it sets 
PLATFORM to freebsd-g++ when it finds g++ and then to freebsd-g++48 when 
it finds g++48, so XPLATFORM gets set to freebsd-g++48 instead of 
freebsd-clang. I assume that uninstalling lang/gcc would make it build, 
but this seems more like a problem with how phantomjs is checking for 
compilers (and then not having the required mkspec).

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

Cannot build lang/phantomjs

[Naram Qashat]

I can't seem to get the phantomjs port to build for me under FreeBSD 
10.3. I have lang/gcc installed (so I have gcc48 and g++48) and clang is 
the base compiler. It seems that it is trying to use g++48, but there is 
no freebsd-g++48 mkspec and it fails to even start building.


I've even tried to set CC and CXX manually but that doesn't help because 
of the mkspec issue. It seems to always try using gcc48 and g++48 
regardless of what CC and CXX are set to.


Thanks,
Naram Qashat
___
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: i386-wine-stating is failing in poudriere

[Naram Qashat]

On 2016-07-10 03:10, Grzegorz Junka wrote:

wit the following

[00:02:04] >> [03][00:00:08] Finished build of
emulators/i386-wine-staging: Failed: run-depends
[00:02:04] >> [03][00:00:08] Skipping build of
emulators/pipelight: Dependent port emulators/i386-wine-staging failed

===>   i386-wine-staging-1.9.13,1 depends on file:
/usr/local/share/wine/gecko/wine_gecko-2.44-x86.msi - not found
===>   Installing existing package 
/packages/All/wine-gecko-devel-2.47.txz

[10rel3amd64-local-crayon2-job-03] Installing wine-gecko-devel-2.47...
[10rel3amd64-local-crayon2-job-03] Extracting wine-gecko-devel-2.47: . 
done

===>   i386-wine-staging-1.9.13,1 depends on file:
/usr/local/share/wine/gecko/wine_gecko-2.44-x86.msi - not found
*** Error code 1

However, on my main host the package is there:

g@crayon2:~ % l /usr/local/share/wine/gecko/wine_gecko-2.44-x86.msi
-rw-r--r--  1 root  wheel  34,832,896  3 Mar 13:34
/usr/local/share/wine/gecko/wine_gecko-2.44-x86.msi

Why does it fail in poudriere? Can I copy it to poudriere from the main 
host?


System: 10.3-RELEASE FreeBSD 10.3-RELEASE #0 r297264: Fri Mar 25
02:10:02 UTC 2016
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

Grzegorz

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


This is because Makefile.inc in emulators/i386-wine-devel isn't being 
updated when emulators/wine-gecko-devel or emulators/wine-mono-devel are 
updated. Most likely because there isn't a single maintainer for all the 
Wine ports. A quick fix is to edit Makefile.inc so it points to the 
proper file, which is wine-gecko-2.47-x86.msi in this case.


Thanks,
Naram Qashat
___
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: Firefox 47.0 hangs when accessing cnn.com

[Naram Qashat]

I'm of the opinion that the Firefox port was updated to 47 very 
prematurely. Even though the SVN commit note says it was a release 
candidate, I don't usually look at commit notes when I've updated my 
ports tree and ran into some weird issues with 47 that made me downgrade 
back to 46.0.1. 47's official release isn't until tomorrow.


Thanks,
Naram Qashat

On 2016-06-06 14:21, Bob Willcox wrote:
I updated my firefox 46.0.1 to 47.0_1.1 yesterday (Sunday) and now when 
I go
out to cnn.com it hangs, eventually putting up a dialog box telling me 
that a
script has stop working (or something similar). Nothing I've tried so 
far

seems to help and I wind up having to kill firefox.

Anyone else experiencing this? Not that other sites (besides cnn.com) 
have
hung on me as well, but cnn.com seems to be the worst (fails the 
quickest,

within seconds of going there).

--
Bob Willcox| Which is worse: ignorance or apathy?
b...@immure.com | Who knows?  Who cares?
Austin, TX |
___
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@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: print/cups-filters

[Naram Qashat]

> In keeping with current fashion, ports seem to be provided with fewer
> options and more things sucked in by default.
> Please don't force dbus on the rest of us, thanks:
>
> --- Makefile.orig 2016-03-27 13:38:13.277556000 -0400
> +++ Makefile  2016-03-27 13:00:07.083467000 -0400
> @@ -16,7 +16,6 @@
>   libijs.so:${PORTSDIR}/print/libijs \
>   liblcms2.so:${PORTSDIR}/graphics/lcms2 \
>   libqpdf.so:${PORTSDIR}/print/qpdf \
> - libdbus-1.so:${PORTSDIR}/devel/dbus \
>   libcupsimage.so:${PORTSDIR}/print/cups \
>   libfreetype.so:${PORTSDIR}/print/freetype2 \
>   libfontconfig.so:${PORTSDIR}/x11-fonts/fontconfig \
> @@ -43,13 +42,15 @@
>   LIBS+=  -L${LOCALBASE}/lib
>   USE_LDCONFIG=   yes
>
> -OPTIONS_DEFINE=  AVAHI DOCS
> +OPTIONS_DEFINE=  AVAHI DOCS DBUS
>   OPTIONS_DEFAULT=AVAHI
>
>   AVAHI_CONFIGURE_ENABLE= avahi
>   AVAHI_LIB_DEPENDS=  libavahi-client.so:${PORTSDIR}/net/avahi-app
>   AVAHI_SUB_LIST= AVAHI_DAEMON=avahi_daemon
>   AVAHI_SUB_LIST_OFF= AVAHI_DAEMON=
> +DBUS_CONFIGURE_ENABLE=   dbus
> +DBUS_LIB_DEPENDS=libdbus-1.so:${PORTSDIR}/devel/dbus
>
>   post-patch:
>   @${REINPLACE_CMD} 's:-std=c++0x:-std=c++11:' ${WRKSRC}/Makefile.in

If you submit this to bugzilla along with build testing, then I will
approve it. I currently do not have the time to look into doing this
myself as I am in the middle of moving over to a new desktop.

Thanks,
Naram Qashat

___
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: Recent changes to /usr/ports/Mk breaks /usr/ports/ports-mgmt/p5-FreeBSD-Portindex

[Naram Qashat]

> The changes to port Mk files breaks
> /usr/ports/ports-mgmt/p5-FreeBSD-Portindex:
>
> When doing cache-init I get this:
>
> Processing make describe output for path "/usr/ports": Can't locate object
> method "mark_used_by" via package "FreeBSD::Portindex::Category" at
> /usr/local/lib/perl5/site_perl/FreeBSD/Portindex/Tree.pm line 431.
>
> portindex worked fine till the changes

I've actually already sent the information about this to Matthew, he said
he will look into it as soon as he can.

___
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: Pipelight update

[Naram Qashat]

> Hi!
>
>> I would like to know if a new version of pipelight is scheduled.
>
> I do not use pipelight, but I had a try on a patch:
>
> http://people.freebsd.org/~pi/misc/pipelight.diff
>
> Can you test this patch and report back ? Then I can commit it.
>
> --
> p...@opsec.eu+49 171 3101372 5 years to
> go !

I'd just like to point out that CONFIGURE_ARGS needs
--gpg-exec=${LOCALBASE}/bin/gpg2 added to it, otherwise it'll try to use
/usr/local/bin/gpg if it is on the system or erroneously try to use
/usr/bin/gpg (which doesn't exist).

___
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: Adding options framework variables that depend on variables coming after bsd.port.pre.mk

[Naram Qashat]

> On 23 Mar, Naram Qashat wrote:
>> I'm wanting to add an options framework LIB_DEPENDS that depends on
>> variables that normally come after bsd.port.pre.mk.
>>
>> In this case, I am trying to add a UTEMPTER_LIB_DEPENDS on
>> sysutils/libutempter, but I want to check OPSYS and OSVERSION
>> beforehand,
>> since base FreeBSD 9.x contains utempter while any earlier FreeBSDs as
>> well as non-FreeBSD OSes don't contain it and need the port.
>>
>> I cannot place the UTEMPTER_LIB_DEPENDS line after bsd.port.pre.mk
>> because
>> the options framework doesn't see it then, but I also cannot wrap it
>> around an if conditional using OPSYS and OSVERSION before
>> bsd.port.pre.mk
>> because those variables aren't set yet.
>>
>> I've been told that there is a workaround, but I was not told what the
>> workaround was. Does anyone know how this can be acomplished?
>
> Maybe something like:
>
> UTEMPTER_LIB_DEPENDS=${FOO}
>
> .include 
>
> .if ${OPSYS} ... && ${OSVERSION} ...
> FOO=  what you want to add to LIB_DEPENDS
> .endif

That worked perfectly, 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"

Adding options framework variables that depend on variables coming after bsd.port.pre.mk

[Naram Qashat]

I'm wanting to add an options framework LIB_DEPENDS that depends on
variables that normally come after bsd.port.pre.mk.

In this case, I am trying to add a UTEMPTER_LIB_DEPENDS on
sysutils/libutempter, but I want to check OPSYS and OSVERSION beforehand,
since base FreeBSD 9.x contains utempter while any earlier FreeBSDs as
well as non-FreeBSD OSes don't contain it and need the port.

I cannot place the UTEMPTER_LIB_DEPENDS line after bsd.port.pre.mk because
the options framework doesn't see it then, but I also cannot wrap it
around an if conditional using OPSYS and OSVERSION before bsd.port.pre.mk
because those variables aren't set yet.

I've been told that there is a workaround, but I was not told what the
workaround was. Does anyone know how this can be acomplished?

___
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: Is it possibly to detect which OpenSSL is used for a port?

[Naram Qashat]

I've looked at bsd.openssl.mk and from what it says, those WITH_OPENSSL_*
knobs are use-set, not port-set. So that doesn't help me.

> On 2015-03-20 11:02, Naram Qashat wrote:
>> This isn't quite what I'm looking for. I want to be able to tell within
>> a
>> port's Makefile if the user wanted the base or ports OpenSSL to be used.
>> I've been trying to port TDE to FreeBSD, and tdelibs uses pkg-config to
>> check for OpenSSL. This would work if the only form of OpenSSL was in
>> ports, but the base OpenSSL doesn't have a pkg-config file to use, so I
>> need to know which is going to be used so I can determine when this
>> pkg-config check can be removed.
>
> `grep WITH_OPENSSL_ Makefile`
>
> If the port expresses an opinion about which OpenSSL to use, it has to
> use WITH_OPENSSL_PORT or WITH_OPENSSL_BASE.
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>


___
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: Is it possibly to detect which OpenSSL is used for a port?

[Naram Qashat]

This isn't quite what I'm looking for. I want to be able to tell within a
port's Makefile if the user wanted the base or ports OpenSSL to be used.
I've been trying to port TDE to FreeBSD, and tdelibs uses pkg-config to
check for OpenSSL. This would work if the only form of OpenSSL was in
ports, but the base OpenSSL doesn't have a pkg-config file to use, so I
need to know which is going to be used so I can determine when this
pkg-config check can be removed.

> Naram Qashat schrieb:,
>
>> So, I know that WITH_OPENSSL_BASE=yes or WITH_OPENSSL_PORT=yes can be
>> set
>> by a user to say they specifically want either the base or the ports
>> version of OpenSSL. But is there a way to determine within a port which
>> OpenSSL is being used, either base or ports? Should I check if
>> OPENSSLBASE
>> is set to /usr? Is there some other (or better) way to do it?
>
> You can check the shared binaries with "ldd".
>
> $ ldd /usr/local/libexec/dovecot/imap-login
> /usr/local/libexec/dovecot/imap-login:
> libssl.so.6 => /usr/lib/libssl.so.6 (0x33cb7000)
> libcrypto.so.6 => /lib/libcrypto.so.6 (0x33d04000)
> librt.so.1 => /usr/lib/librt.so.1 (0x33e66000)
> libc.so.7 => /lib/libc.so.7 (0x33e6b000)
>
> We look for libssl 
>
> $ ldd /usr/local/libexec/dovecot/imap-login  | grep libssl.so
> libssl.so.6 => /usr/lib/libssl.so.6 (0x33cb7000)
>
> This dovecot was build with the openssl-port.
>
> $ ldd /usr/local/bin/stunnel | grep libssl.so
> libssl.so.6 => /usr/lib/libssl.so.6 (0x33cab000)
>
> This stunnel was build with OpenSSL from base.
>
>
> kind regards Dirk
>
> - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany
> - [dirk.me...@dinoex.sub.org],[dirk.me...@guug.de],[din...@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"
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>



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

Is it possibly to detect which OpenSSL is used for a port?

[Naram Qashat]

So, I know that WITH_OPENSSL_BASE=yes or WITH_OPENSSL_PORT=yes can be set
by a user to say they specifically want either the base or the ports
version of OpenSSL. But is there a way to determine within a port which
OpenSSL is being used, either base or ports? Should I check if OPENSSLBASE
is set to /usr? Is there some other (or better) way to do it?

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

Fwd: [package - 84amd64-default][graphics/libspiro] Failed for libspiro-0.2.20131203, 1 in build

[Naram Qashat]

I'm looking to see if someone who is more knowledgeable about perl or libtool or 
whatever to help me solve the below problem.


Basically, libspiro's internal version number is 0.2.20130930. Under FreeBSD 9.X 
and up, config.log shows LIBSPIRO_VERSION as being 0:2:0 and libtool completes 
as expected. However, under 8.X, LIBSPIRO_VERSION instead becomes $0:2:0, and 
libtool gets :2:0 instead of 0:2:0, and thus fails to build, as shown below.


I'd tried manually having autoreconf and automake run (as libspiro's README.md 
explains), but that didn't help at all.


I'm not familiar enough with the build process of applications that utilize 
libtool to know why this is the case. If anyone has any insights into this, I'd 
really appreciate it.


Thanks,
Naram Qashat

 Forwarded Message 
Subject: [package - 84amd64-default][graphics/libspiro] Failed for 
libspiro-0.2.20131203,1 in build

Date: Sun, 11 Jan 2015 18:45:32 GMT
From: pkg-fall...@freebsd.org
To: cyberb...@cyberbotx.com
CC: pkg-fall...@freebsd.org

You are receiving this mail as a port that you maintain
is failing to build on the FreeBSD package build server.
Please investigate the failure and submit a PR to fix
build.

Maintainer: cyberb...@cyberbotx.com
Last committer: w...@freebsd.org
Ident:  $FreeBSD: head/graphics/libspiro/Makefile 375727 2014-12-28 
14:53:29Z wen $
Log URL: 
http://beefy2.isc.freebsd.org/data/84amd64-default/2015-01-11_18h28m14s/logs/libspiro-0.2.20131203,1.log
Build URL: 
http://beefy2.isc.freebsd.org/build.html?mastername=84amd64-default&build=2015-01-11_18h28m14s

Log:

>> Building graphics/libspiro
build started at Sun Jan 11 18:45:07 UTC 2015
port directory: /usr/ports/graphics/libspiro
building for: FreeBSD 84amd64-default-job-12 8.4-RELEASE-p16 FreeBSD 
8.4-RELEASE-p16 amd64

maintained by: cyberb...@cyberbotx.com
Makefile ident:  $FreeBSD: head/graphics/libspiro/Makefile 375727 2014-12-28 
14:53:29Z wen $

Poudriere version: 3.1.1
Host OSVERSION: 1100050
Jail OSVERSION: 804000

---Begin Environment---
OSVERSION=804000
UNAME_v=FreeBSD 8.4-RELEASE-p16
UNAME_r=8.4-RELEASE-p16
FTP_PASSIVE_MODE=YES
BLOCKSIZE=K
MAIL=/var/mail/root
STATUS=1
SAVED_TERM=
MASTERMNT=/usr/local/poudriere/data/.m/84amd64-default/ref
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin
POUDRIERE_BUILD_TYPE=bulk
PKGNAME=libspiro-0.2.20131203,1
OLDPWD=/
PWD=/usr/local/poudriere/data/.m/84amd64-default/ref/.p/pool
MASTERNAME=84amd64-default
USER=root
HOME=/root
POUDRIERE_VERSION=3.1.1
LOCALBASE=/usr/local
PACKAGE_BUILDING=yes
---End Environment---

---Begin OPTIONS List---
---End OPTIONS List---

--CONFIGURE_ARGS--
--prefix=/usr/local ${_LATE_CONFIGURE_ARGS}
--End CONFIGURE_ARGS--

--CONFIGURE_ENV--
XDG_DATA_HOME=/wrkdirs/usr/ports/graphics/libspiro/work 
XDG_CONFIG_HOME=/wrkdirs/usr/ports/graphics/libspiro/work 
HOME=/wrkdirs/usr/ports/graphics/libspiro/work TMPDIR="/tmp" MAKE=gmake 
SHELL=/bin/sh CONFIG_SHELL=/bin/sh CONFIG_SITE=/usr/ports/Templates/config.site 
lt_cv_sys_max_cmd_len=262144

--End CONFIGURE_ENV--

--MAKE_ENV--
XDG_DATA_HOME=/wrkdirs/usr/ports/graphics/libspiro/work 
XDG_CONFIG_HOME=/wrkdirs/usr/ports/graphics/libspiro/work 
HOME=/wrkdirs/usr/ports/graphics/libspiro/work TMPDIR="/tmp" NO_PIE=yes 
SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local  LOCALBASE=/usr/local 
LIBDIR="/usr/lib"  CC="cc" CFLAGS="-O2 -pipe -fstack-protector 
-fno-strict-aliasing"  CPP="cpp" CPPFLAGS=""  LDFLAGS=" -fstack-protector" 
LIBS=""  CXX="c++" CXXFLAGS="-O2 -pipe -fstack-protector -fno-strict-aliasing" 
MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install  -s -o root -g wheel -m 555" 
 BSD_INSTALL_LIB="install  -s -o root -g wheel -m 444" 
BSD_INSTALL_SCRIPT="install  -o root -g wheel -m 555"  BSD_INSTALL_DATA="install 
 -o root -g wheel -m 0644"  BSD_INSTALL_MAN="install  -o root -g wheel -m 444"

--End MAKE_ENV--

--PLIST_SUB--
OSREL=8.4
PREFIX=%D
LOCALBASE=/usr/local
RESETPREFIX=/usr/local
PORTDOCS=""
PORTEXAMPLES=""
LIB32DIR=lib
DOCSDIR="share/doc/libspiro"
EXAMPLESDIR="share/examples/libspiro"
DATADIR="share/libspiro"
WWWDIR="www/libspiro"
ETCDIR="etc/libspiro"
--End PLIST_SUB--

--SUB_LIST--
PREFIX=/usr/local
LOCALBASE=/usr/local
DATADIR=/usr/local/share/libspiro
DOCSDIR=/usr/local/share/doc/libspiro
EXAMPLESDIR=/usr/local/share/examples/libspiro
WWWDIR=/usr/local/www/libspiro
ETCDIR=/usr/local/etc/libspiro
--End SUB_LIST--

---Begin make.conf---
USE_PACKAGE_DEPENDS=yes
BATCH=yes
WRKDIRPREFIX=/wrkdirs
USE_PACKAGE_DEPENDS=yes
BATC

Using another port Makefile's values without being a slave port?

[Naram Qashat]

Hi everyone,

I've been working on a major update to the print/fontforge port. Fontforge is 
set up in such a way that it has no option to disable usage of freetype, but it 
does have an option of using freetype's source code to build freetype's internal 
debugger into fontforge. Because of this, fontforge needs freetype's distfile 
when that option is enabled.


Currently, to do the above, the version, distfile, and master sites of freetype 
have been copied into fontforge's Makefile. However, I am wondering if it is 
possible to utilize the distfile and master sites from the print/freetype2 port 
directly instead of hardcoding them into fontforge's port.


If this is feasible, I know that one way to accomplish this would be using shell 
commands (to basically do 'make -VDISTFILES' and 'make -VMASTER_SITES' on the 
freetype port), but I'm wondering if those values can be utilized without using 
shell commands.


Because fontforge is only a consumer of freetype and not related to it, it 
wouldn't be appropriate to have fontforge being a slave port of freetype.


If it is better to keep things as they are instead, I'd like to know. I'm just 
looking for a way to make it easier to handle freetype being updated in the 
future without having to worry about it in fontforge. The only reason I can 
think of against changing how it is done is because of freetype's tarball being 
listed in fontforge's distfiles, and that would need updating every time there 
is a freetype update anyways.


Thanks,
Naram Qashat
___
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"

Suspending poudriere build immediately upon non-wrkdir file change

[Naram Qashat]

I would like to know if there is a way to suspend a poudriere build immediately 
in the case of a file being modified outside of the wrkdir. I know that 
poudriere will let you know of changes to files outside of the wrkdir when it is 
done building, but I need to know exactly when it happens, as the 
devel/mingw32-gcc never gets to finish building for 10.x since it clobbers some 
files installed by devel/mingw32-bin-msvcrt during its build.


Thanks,
Naram Qashat
___
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"

Fwd: Re: devel/mingw32-gcc problem

[Naram Qashat]

 Forwarded Message 
Subject: Re: devel/mingw32-gcc problem
From: David Chisnall 
Date: Sun, 12 Oct 2014 21:07:03 +0100
Cc: freebsd-toolch...@freebsd.org, r...@freebsd.org

There have been some changes to how the ports tree handles libtool files 
recently, but I don't know the details.  You'd be better off asking on the ports 
list or in #bsdports on EFNet.


David

On 10 Oct 2014, at 21:36, Naram Qashat  wrote:


Hi everyone,

I've been trying to push out an update to devel/mingw32-gcc, but ran into a 
problem, and Rene suggested asking about it here.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191291

Long story short, some of the .a files installed by devel/mingw32-bin-msvcrt 
get clobbered (their contents becomes nothing but NUL bytes) during the build 
of mingw32-gcc. This only happens under 10.x and not under 9.x or earlier.

I'm not subscribed to this mailing list, so please CC me on any replies.

Thanks,
Naram Qashat


I'm forwarding this message as suggested by David. I'm not sure if the libtool 
changes would account for the problem I'm running in to, as the files being 
clobbered are archives and not libtool files. But if anyone has any insight 
about this, I'd really appreciate it, as I would like to update the port and 
this has been a major stopping point.


Thanks,
Naram Qashat
___
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"

devel/mingw32-gcc build difficulties

[Naram Qashat]

I've been trying to put together an update to devel/mingw32-gcc to bring it to 
gcc 4.8.1 (the current version that the official MinGW gcc is at). I'm not sure 
if poudriere is part of my issues or not, but here goes.


When building under a 9.x jail, the port pollutes PREFIX with 
/usr/local/mingw32/lib/COPIED and /usr/local/mingw32/sys-include/. I've no idea 
why they are left behind with 9.x (and I believe also 8.x as a previous redports 
build by rene@ seen here: 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191291#c2 shows) when they 
aren't left behind on 10.x or 11.x, but at the very least, these can be deleted 
in a post-build target without issues.


When building under a 10.x jail, though, the mingw32-gcc port seems to be 
clobbering some of the .a files that were installed by the 
devel/mingw32-bin-msvcrt port. At first, I thought it might've been because I 
had built a 10.x jail that was slightly newer than the world, but after 
rebuilding my 10.x jail to be 10.0-RELEASE (and thus no longer newer than my 
world), it still happens. I'm unable to get the build to finish under 10.x 
because /usr/local/mingw32/lib/libuser32.a from mingw32-bin-msvcrt contains 
nothing but nulls at the point where it tries to build libgcc_s_dw2-1.dll. 
Searching through the build log shows nothing pertaining to this other than it 
trying to link to the archive with -luser32. The archive isn't broken in 
mingw32-bin-msvcrt itself since I can install that and go into the jail and see 
that it has proper contents.


All in all, I would really like to push out an update to the port, but the 10.x 
difficulty is a stopping point currently.


Thanks in advance,
Naram Qashat
___
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"

print/cups-filters and compile errors with qpdf

[Naram Qashat]

I just wanted to send this out to the list because this has bitten a few 
people already. If you get a compile error in relation to qpdf.h 
missing, this is because print/qpdf needs to be built with the SDK 
option enabled. The option is defaulted, but it wasn't always the case, 
so if you use ports, just rebuild with that option enabled, if you use 
packages, just get the latest package.


Thanks,
Naram Qashat
___
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: Does pkg automatically download INDEX?

[Naram Qashat]

On 08/15/14 13:14, Naram Qashat wrote:

On 08/12/14 14:11, Patrick Powell wrote:

On 08/09/14 18:15, Naram Qashat wrote:

On 08/09/14 19:45, Scot Hetzel wrote:

On Fri, Aug 8, 2014 at 7:00 PM, Naram Qashat  wrote:

On 08/04/14 07:28, David Wolfskill wrote:


On Mon, Aug 04, 2014 at 07:09:33AM -0400, Naram Qashat wrote:


On 08/03/14 22:14, David Wolfskill wrote:


On Sun, Aug 03, 2014 at 10:10:27PM -0400, Naram Qashat wrote:


...
If there is
a way to find out when any process is attempting to modify a file, that
would
probably help me narrow it down, but I'm not aware of anything that can
do that,
...



Well, "chflags schg /usr/ports/INDEX*" would *prevent* the modification


...
This was a really good suggestion.



Glad to help.  :-)

Peace,
david



OK, so while no programs have whined or complained, I get the feeling that
something on my system is running portsnap without my knowledge. When I had
set the schg flag on INDEX-9, an INDEX-9.bz2 file came up. I set the schg
flag on that as well, and now I notice there are a bunch of files called
.fetch.??.INDEX-9.bz2 (where ?? is a random string), as well as a
file called .portsnap.INDEX. As far as I know, I don't have anything
configured to run portsnap, but is there something that defaults to running
portsnap occasionally? I couldn't find anything that would do that.



Do your have a crontab entry that is running portsnap with the -I
(update INDEX) option?

http://www.pl.freebsd.org/doc/handbook/portsnap.html


As far as I can tell, no, none of my crontabs have any references to portsnap
in them. This is making me a bit stumped as to why it would be happening. I
checked the main /etc/crontab, I checked the crontabs in /var/cron/tabs. I
have searched inside of /etc and /usr/local/etc for anything related to
portsnap. Nothing that would be doing this is coming up at all.

Thanks,
Naram Qashat
___
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"


I ran into something similar once,  and found out what was happening this way.

1.  replace the portsnap executable with a shell script.  Rename portsnap to
something
  like /usr/sbin/portsnap.orig
2.  This shell script should dump the current ENV and other stuff to a log file.
Don't forget to put in a timestamp.
And then do:
   exec /usr/sbin/portsnap.orig $*

I did this and found that there was something in one of the .login scripts.
G...


I really liked this suggestion, and did just that. Unfortunately, it seems that
portsnap may not be the culprit here, as I haven't had any log files created
from my modified script nor is there a .portsnap.INDEX file being created after
I deleted the one that was there, but I still have a bunch of
.fetch.??.INDEX-9.bz2 files in /usr/ports. I've been trying to search for
anything on my system that even references INDEX-9, but I can't find anything
else that would cause this to happen.

Thanks,
Naram Qashat


Well, I finally figured out what the culprit was. Webmin was configured to do 
automatic updates and it was running "make fetchindex" on the ports tree. I 
disabled that and now it has stopped trying to download the index. I only 
managed to track that down after noticing that the fetchindex target was the 
only other thing that could have downloaded the index file, and modifying 
/usr/ports/Makefile so it would write the contents of 
/proc/${.MAKE.PPID}/cmdline to a file so I could see what was invoking make. The 
.MAKE.PPID variable was pointed out to me on IRC.


Thanks,
Naram Qashat
___
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: devel/doxygen woes

[Naram Qashat]

On 08/21/14 05:17, Kurt Jaeger wrote:

Hi!


So I've been getting a lot of issues being directed at me due to the
recent devel/doxygen update to 1.8.7. While I'm not sure why these
issues only cropped up after that update and not before, I would like to
try addressing a few things.


Those discussions always pop up if something changes, even if it is not
related 8-}


doxygen has a bit of an issue in that it uses itself to build its own
documentation.


Let me state this a bit more general:

doxygen has the issue that if you use it, it brings in a huge
amount of dependencies. And currently, this process is not
thought-through.


As a result of this, the HTMLDOCS and PDFDOCS options
will only pull in what is needed to allow doxygen to be built in such a
way to be able to build its own documentation. Because of this, if those
options are left out, then doxygen will be left in a state where it can
no longer build HTML docs fully (because of the lack of graphviz) and
cannot build PDF docs (because of the lack of a LaTeX distribution).


What might be a use case for doxygen, if it is not used for html
and pdf docs ? What other formats are supported ?


As far as I can tell from looking at a Doxyfile, it can generate HTML, Docset 
files for Xcode, Microsoft HTML help (.chm files), Qt compressed help (.qch 
files), Eclipse help plugin, LaTeX (which I believe creates a PDF), RTF, man 
pages, XML, AutoGen definitions, and perlmod. A lot of these are disabled by 
default in Doxyfile, though. I think that doxygen's documentation states that 
only the HTML and LaTeX generators require external dependencies, and dot from 
graphviz is only really needed for HTML if the Doxyfile says it wants to use it.



Because of this, consumers of doxygen, whether they be other FreeBSD
ports or just users of doxygen in general, would need to have graphviz
and LaTeX installed to get all of doxygen's features. I recently had
someone that wanted to build doxygen without the LaTeX dependency,
though. So I think ideally, the dependencies for graphviz and LaTeX
should becomes separate options, and the HTMLDOCS and PDFDOCS options
should only be allowed if graphviz and LaTeX, respectively, are enabled.


The problem is: If a port has options to use doxygen, those
options should also include BUILD_DEPENDS for graphviz etc.
The ports that use doxygen normally do not know about those
BUILD_DEPENDS.

One idea was to provide a /usr/ports/Mk/Uses/doxygen.mk which
provides the necessary "glue" by USES += doxygen.


All in all, it basically boils down to needing to find a way to include
graphviz and LaTeX in a way that doesn't cause too many problems but
also allows doxygen to still have the option of building its own
documentation.


It's either in or out 8-}


Well, I'd already put in a bug for this:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192732

It does mean that, yes, by default, it'll pull in a lot of dependencies. I'm not 
sure if having a uses for doxygen really makes much sense, though. The only 
thing that I can think of that would really need work is probably figuring out 
just what parts of TexLive are actually needed by doxygen instead of trying to 
pull in the full distribution.

___
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: Does pkg automatically download INDEX?

[Naram Qashat]

On 08/12/14 14:11, Patrick Powell wrote:

On 08/09/14 18:15, Naram Qashat wrote:

On 08/09/14 19:45, Scot Hetzel wrote:

On Fri, Aug 8, 2014 at 7:00 PM, Naram Qashat  wrote:

On 08/04/14 07:28, David Wolfskill wrote:


On Mon, Aug 04, 2014 at 07:09:33AM -0400, Naram Qashat wrote:


On 08/03/14 22:14, David Wolfskill wrote:


On Sun, Aug 03, 2014 at 10:10:27PM -0400, Naram Qashat wrote:


...
If there is
a way to find out when any process is attempting to modify a file, that
would
probably help me narrow it down, but I'm not aware of anything that can
do that,
...



Well, "chflags schg /usr/ports/INDEX*" would *prevent* the modification


...
This was a really good suggestion.



Glad to help.  :-)

Peace,
david



OK, so while no programs have whined or complained, I get the feeling that
something on my system is running portsnap without my knowledge. When I had
set the schg flag on INDEX-9, an INDEX-9.bz2 file came up. I set the schg
flag on that as well, and now I notice there are a bunch of files called
.fetch.??.INDEX-9.bz2 (where ?? is a random string), as well as a
file called .portsnap.INDEX. As far as I know, I don't have anything
configured to run portsnap, but is there something that defaults to running
portsnap occasionally? I couldn't find anything that would do that.



Do your have a crontab entry that is running portsnap with the -I
(update INDEX) option?

http://www.pl.freebsd.org/doc/handbook/portsnap.html


As far as I can tell, no, none of my crontabs have any references to portsnap
in them. This is making me a bit stumped as to why it would be happening. I
checked the main /etc/crontab, I checked the crontabs in /var/cron/tabs. I
have searched inside of /etc and /usr/local/etc for anything related to
portsnap. Nothing that would be doing this is coming up at all.

Thanks,
Naram Qashat
___
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"


I ran into something similar once,  and found out what was happening this way.

1.  replace the portsnap executable with a shell script.  Rename portsnap to
something
  like /usr/sbin/portsnap.orig
2.  This shell script should dump the current ENV and other stuff to a log file.
Don't forget to put in a timestamp.
And then do:
   exec /usr/sbin/portsnap.orig $*

I did this and found that there was something in one of the .login scripts.
G...


I really liked this suggestion, and did just that. Unfortunately, it seems that 
portsnap may not be the culprit here, as I haven't had any log files created 
from my modified script nor is there a .portsnap.INDEX file being created after 
I deleted the one that was there, but I still have a bunch of 
.fetch.??.INDEX-9.bz2 files in /usr/ports. I've been trying to search for 
anything on my system that even references INDEX-9, but I can't find anything 
else that would cause this to happen.


Thanks,
Naram Qashat
___
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"

devel/doxygen woes

[Naram Qashat]

So I've been getting a lot of issues being directed at me due to the 
recent devel/doxygen update to 1.8.7. While I'm not sure why these 
issues only cropped up after that update and not before, I would like to 
try addressing a few things.


doxygen has a bit of an issue in that it uses itself to build its own 
documentation. As a result of this, the HTMLDOCS and PDFDOCS options 
will only pull in what is needed to allow doxygen to be built in such a 
way to be able to build its own documentation. Because of this, if those 
options are left out, then doxygen will be left in a state where it can 
no longer build HTML docs fully (because of the lack of graphviz) and 
cannot build PDF docs (because of the lack of a LaTeX distribution).


Because of this, consumers of doxygen, whether they be other FreeBSD 
ports or just users of doxygen in general, would need to have graphviz 
and LaTeX installed to get all of doxygen's features. I recently had 
someone that wanted to build doxygen without the LaTeX dependency, 
though. So I think ideally, the dependencies for graphviz and LaTeX 
should becomes separate options, and the HTMLDOCS and PDFDOCS options 
should only be allowed if graphviz and LaTeX, respectively, are enabled.


If I add in those options, then I believe that the options for including 
graphviz and LaTeX should probably be made default. For something like 
this, though, I would need to know how many ports would need either 
option enabled. If the options don't need to be defaulted, then they 
shouldn't need it. graphviz might not be a bad one to have defaulted, 
but LaTeX might. If anyone does have an opinion on this, I'd like to 
hear it.


All in all, it basically boils down to needing to find a way to include 
graphviz and LaTeX in a way that doesn't cause too many problems but 
also allows doxygen to still have the option of building its own 
documentation.


In a semi-related point, part of the patching being done to the port 
involves removing doxygen's included MD5 implementation in order to use 
the system's MD5 implementation instead. I've heard differing opinions 
on this situation. Some people say that I should just let doxygen use 
its own MD5 implementation. But other people say that ports should 
always try to use the system's implementations as opposed to embedded 
ones. Which is better to use in this situation? I believe that doxygen's 
implementation of MD5 is statically linked, but patching it as I am now, 
it will call from the MD5 library of the system instead.


Thanks,
Naram Qashat
___
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: Does pkg automatically download INDEX?

[Naram Qashat]

On 08/09/14 19:45, Scot Hetzel wrote:

On Fri, Aug 8, 2014 at 7:00 PM, Naram Qashat  wrote:

On 08/04/14 07:28, David Wolfskill wrote:


On Mon, Aug 04, 2014 at 07:09:33AM -0400, Naram Qashat wrote:


On 08/03/14 22:14, David Wolfskill wrote:


On Sun, Aug 03, 2014 at 10:10:27PM -0400, Naram Qashat wrote:


...
If there is
a way to find out when any process is attempting to modify a file, that
would
probably help me narrow it down, but I'm not aware of anything that can
do that,
...



Well, "chflags schg /usr/ports/INDEX*" would *prevent* the modification


...
This was a really good suggestion.



Glad to help.  :-)

Peace,
david



OK, so while no programs have whined or complained, I get the feeling that
something on my system is running portsnap without my knowledge. When I had
set the schg flag on INDEX-9, an INDEX-9.bz2 file came up. I set the schg
flag on that as well, and now I notice there are a bunch of files called
.fetch.??.INDEX-9.bz2 (where ?? is a random string), as well as a
file called .portsnap.INDEX. As far as I know, I don't have anything
configured to run portsnap, but is there something that defaults to running
portsnap occasionally? I couldn't find anything that would do that.



Do your have a crontab entry that is running portsnap with the -I
(update INDEX) option?

http://www.pl.freebsd.org/doc/handbook/portsnap.html


As far as I can tell, no, none of my crontabs have any references to portsnap in 
them. This is making me a bit stumped as to why it would be happening. I checked 
the main /etc/crontab, I checked the crontabs in /var/cron/tabs. I have searched 
inside of /etc and /usr/local/etc for anything related to portsnap. Nothing that 
would be doing this is coming up at all.


Thanks,
Naram Qashat
___
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: Does pkg automatically download INDEX?

[Naram Qashat]

On 08/04/14 07:28, David Wolfskill wrote:

On Mon, Aug 04, 2014 at 07:09:33AM -0400, Naram Qashat wrote:

On 08/03/14 22:14, David Wolfskill wrote:

On Sun, Aug 03, 2014 at 10:10:27PM -0400, Naram Qashat wrote:

...
If there is
a way to find out when any process is attempting to modify a file, that would
probably help me narrow it down, but I'm not aware of anything that can do that,
...


Well, "chflags schg /usr/ports/INDEX*" would *prevent* the modification

...
This was a really good suggestion.


Glad to help.  :-)

Peace,
david


OK, so while no programs have whined or complained, I get the feeling that 
something on my system is running portsnap without my knowledge. When I had set 
the schg flag on INDEX-9, an INDEX-9.bz2 file came up. I set the schg flag on 
that as well, and now I notice there are a bunch of files called 
.fetch.??.INDEX-9.bz2 (where ?? is a random string), as well as a file 
called .portsnap.INDEX. As far as I know, I don't have anything configured to 
run portsnap, but is there something that defaults to running portsnap 
occasionally? I couldn't find anything that would do that.


Thanks,
Naram Qashat
___
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: FreeBSD Port: doxygen-1.8.3.1_1,1

[Naram Qashat]

On 08/07/14 15:06, Ewout Boks wrote:

Hi,

I tried building doxygen on FreeBSD 10.0 today, but the build failed :

clang++ -c -pipe -O2 -Wall -W -pthread -D_THREAD_SAFE -DQT_NO_CAST_FROM_ASCII 
-DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_XML_LIB -DQT_GUI_LIB -DQT_CORE_LIB 
-DQT_SHARED -I/usr/local/share/qt4/mkspecs/freebsd-clang -I. 
-I/usr/local/include/qt4/QtCore -I/usr/local/include/qt4/QtGui 
-I/usr/local/include/qt4/QtXml -I/usr/local/include/qt4 -I. -Imoc 
-I/usr/local/include/qt4 -I/usr/local/include -o obj/config_lex.o config_lex.cpp
lex.config.c:1702:16: warning: function 'yyinput' is not needed and will not be 
emitted
   [-Wunneeded-internal-declaration]
 static int yyinput (void)


Perhaps the compiler switch '-Wunneeded-internal-declaration' should be 
removed, or the source code should be modified.


Best regards,

Ewout Boks


It has nothing to do with the compiler flag or the source code, it has to do 
with the fact that doxygen is expecting a newer version of flex than what is in 
the base system. I am attaching a patch that I currently have on my local system 
that allows it to build, in lieu of the 1.8.7 patch that is being looked in to. 
I might have to send this in as a bug report if we can't get the 1.8.7 update 
done, though.


Thanks,
Naram Qashat
Index: /usr/ports/devel/doxygen/Makefile
===
--- /usr/ports/devel/doxygen/Makefile	(revision 363687)
+++ /usr/ports/devel/doxygen/Makefile	(working copy)
@@ -16,7 +16,8 @@
 LICENSE=	GPLv2
 LICENSE_FILE=	${WRKSRC}/LICENSE
 
-BUILD_DEPENDS=	tmake:${PORTSDIR}/devel/tmake
+BUILD_DEPENDS=	tmake:${PORTSDIR}/devel/tmake \
+		flex>0:${PORTSDIR}/textproc/flex
 LIB_DEPENDS=	libpng15.so:${PORTSDIR}/graphics/png
 
 USES=		bison iconv perl5 gmake
@@ -24,7 +25,8 @@
 HAS_CONFIGURE=	yes
 QT_NONSTANDARD=	yes	# non-standard configure arguments
 CONFIGURE_ARGS=	--prefix ${PREFIX} --perl ${PERL} --make ${MAKE_CMD} \
-		--install "${INSTALL}"
+		--install "${INSTALL}" --flex ${LOCALBASE}/bin/flex
+MAKE_JOBS_UNSAFE=	yes
 REINPLACE_ARGS=	-i ''
 
 EXTRACT_AFTER_ARGS=	--exclude '*/libmd5'	\
@@ -52,7 +54,7 @@
 ALL_TARGET+=	pdf
 USE_TEX=	latex:build
 USE_GHOSTSCRIPT_BUILD=	yes
-MAKE_ARGS+=	HAVE_PDFDOCS=yes
+MAKE_ARGS+=	HAVE_LATEX=yes
 .endif # PDFDOCS
 .endif # HTMLDOCS
 
___
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: Does pkg automatically download INDEX?

[Naram Qashat]

On 08/04/14 15:41, Alexander Leidinger wrote:

On Sun, 03 Aug 2014 16:27:36 -0400
Naram Qashat  wrote:


On 08/03/14 15:53, Matthew Seaman wrote:

On 03/08/2014 20:34, Naram Qashat wrote:

Well, I've been using the command line arguments of "-voL '='", and
looking at the man page for pkg-version, as far as I can tell, it
shouldn't be downloading INDEX, since I do have INDEX-9 on my
system.


pkg(8) doesn't download or attempt to build an INDEX at all.  It
can use one if one happens to be already available, but not
otherwise.

Cheers,

Matthew


I'm at a bit of a loss, then. While I can't say for sure if pkg is
doing something unintended, there seems to be something on my system
that is downloading INDEX without my knowledge.

My usual way of updating my INDEX is using p5-FreeBSD-Portindex to
generate the INDEX file, and using that INDEX to update the files
that portupgrade uses. I run that manually, so I have nothing that
would do that for me automatically, to my knowledge.


How do you update the ports tree, with portsnap or with svn? Portnap
also updates the index.

Bye,
Alexander.


I update via svn, so that isn't getting the INDEX updates.

Thanks,
Naram Qashat
___
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: Does pkg automatically download INDEX?

[Naram Qashat]

On 08/03/14 22:14, David Wolfskill wrote:

On Sun, Aug 03, 2014 at 10:10:27PM -0400, Naram Qashat wrote:

...
If there is
a way to find out when any process is attempting to modify a file, that would
probably help me narrow it down, but I'm not aware of anything that can do that,
...


Well, "chflags schg /usr/ports/INDEX*" would *prevent* the modification
-- and with luck, the offending process might whine or squawk (thus
providing you with identification).

"chflags noschg /usr/ports/INDEX*" to undo it.

Peace,
david


This was a really good suggestion. While I wasn't lucky in regards to having a 
process whine about being unable to write to INDEX-9, I did find that now there 
is an INDEX-9.bz2 sitting in /usr/ports, which I assume comes from a download of 
it. I'm going to try setting INDEX-9.bz2 to also have the schg flag on it, maybe 
that'll make a process complain. If not, at least I can modify my manual INDEX 
building to remove the schg flag before updated INDEX and then setting it again 
afterwards.


Thanks,
Naram Qashat
___
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: Does pkg automatically download INDEX?

[Naram Qashat]

On 08/03/14 21:24, Kevin Oberman wrote:

On Sun, Aug 3, 2014 at 1:27 PM, Naram Qashat mailto:cyberb...@cyberbotx.com>> wrote:

On 08/03/14 15:53, Matthew Seaman wrote:

On 03/08/2014 20:34, Naram Qashat wrote:

Well, I've been using the command line arguments of "-voL '='", and
looking at the man page for pkg-version, as far as I can tell, it
shouldn't be downloading INDEX, since I do have INDEX-9 on my 
system.


pkg(8) doesn't download or attempt to build an INDEX at all.  It can use
one if one happens to be already available, but not otherwise.

 Cheers,

 Matthew


I'm at a bit of a loss, then. While I can't say for sure if pkg is doing
something unintended, there seems to be something on my system that is
downloading INDEX without my knowledge.

My usual way of updating my INDEX is using p5-FreeBSD-Portindex to generate
the INDEX file, and using that INDEX to update the files that portupgrade
uses. I run that manually, so I have nothing that would do that for me
automatically, to my knowledge.


Thanks,
Naram Qasha


Are you doing anything between building the index and running "pkg version"? I
can tell you that portmaster will download the "latest" index unless you use the
--no-index-fetch option. I don't know about other tools, but it caught me by
surpize.
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com <mailto:rkober...@gmail.com>


I'm not. In fact, I rebuilt the INDEX and did 'pkg version' and it didn't change 
INDEX, which is correct from what Matthew said. But I left the system alone and 
then, without having run any other commands, checked the timestamp of INDEX-9 
again. It was changed, despite having not done anything in between. If there is 
a way to find out when any process is attempting to modify a file, that would 
probably help me narrow it down, but I'm not aware of anything that can do that, 
so if anyone does know, that would be helpful. I had tried to check my 
/var/log/all.log for anything but the only thing that even happened around the 
time when INDEX-9 got changed was Postfix's anvil being called, which I doubt 
would've caused the INDEX-9 to be downloaded.


Thanks,
Naram Qashat
___
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: Does pkg automatically download INDEX?

[Naram Qashat]

On 08/03/14 15:53, Matthew Seaman wrote:

On 03/08/2014 20:34, Naram Qashat wrote:

Well, I've been using the command line arguments of "-voL '='", and
looking at the man page for pkg-version, as far as I can tell, it
shouldn't be downloading INDEX, since I do have INDEX-9 on my system.


pkg(8) doesn't download or attempt to build an INDEX at all.  It can use
one if one happens to be already available, but not otherwise.

Cheers,

Matthew


I'm at a bit of a loss, then. While I can't say for sure if pkg is doing 
something unintended, there seems to be something on my system that is 
downloading INDEX without my knowledge.


My usual way of updating my INDEX is using p5-FreeBSD-Portindex to generate the 
INDEX file, and using that INDEX to update the files that portupgrade uses. I 
run that manually, so I have nothing that would do that for me automatically, to 
my knowledge.


Thanks,
Naram Qashat
___
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: Does pkg automatically download INDEX?

[Naram Qashat]

On 08/03/14 14:57, Matthew Seaman wrote:

On 03/08/2014 18:33, Naram Qashat wrote:

I've been noticing this whenever I do a 'pkg version -v', it shows some
ports as being different from the INDEX, but when I check the actual
port, it isn't the same version that 'pkg version' shows. I usually
rebuild my INDEX manually after doing an svn update, so I'm wondering if
this is pkg doing something or if I have something else doing it. I am
running FreeBSD 9.2.


What 'pkg version' does depends on the command line options you give it
and to the presence or not of the ports INDEX or the ports tree in
general.  It's all described in pkg-version(8).

Cheers,

Matthew


Well, I've been using the command line arguments of "-voL '='", and looking at 
the man page for pkg-version, as far as I can tell, it shouldn't be downloading 
INDEX, since I do have INDEX-9 on my system.


Thanks,
Naram Qashat
___
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"

Does pkg automatically download INDEX?

[Naram Qashat]

I've been noticing this whenever I do a 'pkg version -v', it shows some ports as 
being different from the INDEX, but when I check the actual port, it isn't the 
same version that 'pkg version' shows. I usually rebuild my INDEX manually after 
doing an svn update, so I'm wondering if this is pkg doing something or if I 
have something else doing it. I am running FreeBSD 9.2.


Thanks,
Naram Qashat
___
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: Help with "port test"

[Naram Qashat]

On 07/15/14 06:36, Stefan Esser wrote:

Am 15.07.2014 11:48, schrieb Andrea Venturoli:

Hello.

I'm trying to create a new port and there are some things I don't
understand.

Referring to chapter 9 of the Porter's Handbook:

_ "make clean; make package PREFIX=/var/tmp/`make -V PORTNAME`" gives no
error;

_ "make stage && make check-orphans && make package" also finds no issue;

_ however "port test" gives:


===> Checking for directories owned by MTREEs
Error: Owned by MTREE: @unexec rmdir "/usr/local" >/dev/null 2>&1 || :


What does this mean?


You are trying to delete the directory /usr/local, which is part of
the base system.

Just remove '@unexec rmdir "/usr/local" ...' from pkg-plist ...

Regards, STefan


I actually think there is an error somewhere in the ports system (but I'm not 
sure where), depending on what the port is trying to do.


I found that if a port has a PLIST_SUB that replaces part of the PREFIX, it'll 
cause both porttools and poudriere to think that PREFIX is being removed 
incorrectly (I ran into this when testing devel/mingw32-gcc).


I also found that if a port has USE_LDCONFIG set, it'll incorrectly think that 
LOCALBASE is being removed because the ldconfig entry isn't being added to 
PREFIX but to LOCALBASE instead (I ran into this when testing 
x11-toolkits/scintilla).


I haven't looked too far into why this is happening, but those entries were 
showing up in work/.staged-files despite that they weren't in my pkg-plist. 
Hopefully this is enough information to allow someone with more knowledge of the 
ports infrastructure to correct it.


Thanks,
Naram Qashat
___
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"

Need GCC cross-compiling help for bug #191291

[Naram Qashat]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191291

The bug report explains my issue, but long story short, I cannot get 
devel/mingw32-gcc to build in order to properly verify that it is being staged 
as well as updated to the GCC that MinGW supports. I have tried all that I can, 
but I do not know enough about cross-compiling GCC to know why it fails. stdio.h 
is included in devel/mingw32-bin-msvcrt, so that is why I am confused about the 
build problems. Any help is appreciated, as I would like the port to not die out 
just because of this.


Thanks,
Naram Qashat
___
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"

devel/mingw32-gcc: Attempting to update the port, can't compile it

[Naram Qashat]

As the maintainer of devel/mingw32-gcc, it currently needs staging, but the port 
refuses to compile at the moment. The first problem I was getting was it saying 
that it couldn't find stdio.h at all.


After a bit of searching on Google, I found the --with-sysroot configure option. 
I had to patch gcc/config.gcc to use /mingw32/include instead of /mingw/include 
(since devel/mingw32-bin-msvcrt installs to ${PREFIX}/mingw32/include).


I have attempted to build the port in poudriere.

If I set --with-sysroot to ${PREFIX}, I get the following:

The directory that should contain system headers does not exist:
  /prefix/mingw32-gcc-4.8.1_1/mingw32/include
gmake[2]: *** [stmp-fixinc] Error 1
gmake[2]: Leaving directory 
`/wrkdirs/usr/ports/devel/mingw32-gcc/work/build/gcc'
gmake[1]: *** [all-gcc] Error 2
gmake[1]: Leaving directory `/wrkdirs/usr/ports/devel/mingw32-gcc/work/build'
gmake: *** [all] Error 2

If I set --with-sysroot to ${LOCALBASE}, I get the following instead:

/wrkdirs/usr/ports/devel/mingw32-gcc/work/build/./gcc/xgcc 
-B/wrkdirs/usr/ports/devel/mingw32-gcc/work/build/./gcc/ 
-L/wrkdirs/usr/ports/devel/mingw32-gcc/work/build/mingw32/winsup/mingw 
-L/wrkdirs/usr/ports/devel/mingw32-gcc/work/build/mingw32/winsup/w32api/lib 
-isystem 
/wrkdirs/usr/ports/devel/mingw32-gcc/work/gcc-4.8.1/winsup/mingw/include 
-isystem 
/wrkdirs/usr/ports/devel/mingw32-gcc/work/gcc-4.8.1/winsup/w32api/include 
-B/prefix/mingw32-gcc-4.8.1_1/mingw32/bin/ 
-B/prefix/mingw32-gcc-4.8.1_1/mingw32/lib/ -isystem 
/prefix/mingw32-gcc-4.8.1_1/mingw32/include -isystem 
/prefix/mingw32-gcc-4.8.1_1/mingw32/sys-include-g -O2 -pipe 
-I/usr/local/include -fno-strict-aliasing -O2 
-I../.././..//gcc-4.8.1/libgcc/../winsup/w32api/include -g -O2 -pipe 
-I/usr/local/include -fno-strict-aliasing -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE 
-W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes 
-Wold-style-definition  -isystem ./include   -g -DIN_LIBGCC2 -fbuilding-libgcc 
-fno-stack-protector   -I. -I. -I../.././gcc -I../.././..//gcc-4.8.1/libgcc 
-I../.././..//gcc-4.8.1/libgcc/. -I../.././..//gcc-4.8.1/libgcc/../gcc 
-I../.././..//gcc-4.8.1/libgcc/../include 
-I../.././..//gcc-4.8.1/libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT 
-DHAVE_CC_TLS -DUSE_EMUTLS -o _muldi3.o -MT _muldi3.o -MD -MP -MF _muldi3.dep 
-DL_muldi3 -c ../.././..//gcc-4.8.1/libgcc/libgcc2.c

In file included from ../.././..//gcc-4.8.1/libgcc/libgcc2.c:27:0:
../.././..//gcc-4.8.1/libgcc/../gcc/tsystem.h:87:19: fatal error: stdio.h: No 
such file or directory

 #include 
   ^
compilation terminated.
gmake[2]: *** [_muldi3.o] Error 1
gmake[2]: Leaving directory 
`/wrkdirs/usr/ports/devel/mingw32-gcc/work/build/mingw32/libgcc'

gmake[1]: *** [all-target-libgcc] Error 2
gmake[1]: Leaving directory `/wrkdirs/usr/ports/devel/mingw32-gcc/work/build'
gmake: *** [all] Error 2

I'm at a complete loss as to how to fix this. I am hoping that someone more 
versed in cross-compiling gcc can help me solve this, so I can get the port 
updated and staged before the end of the month.


Thanks,
Naram Qashat
___
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: devel/doxygen: Need TeX help

[Naram Qashat]

On 06/13/14 18:12, Kurt Jaeger wrote:

Hi!


If I use TeXLive, though, it gets past that point and then ends up with the same
error as I was getting with 1.8.6, with the longtable error shown earlier in
this thread.


I'll investigate this. But it will take time.


See

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190943

for a working patch for this issue.


I really appreciate you looking into the issue for us, Kurt. :D Glad to have a 
working solution, even if it isn't the best, it certainly is better than what we 
had, which was a broken build.


Thanks,
Naram Qashat
___
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: devel/doxygen: Need TeX help

[Naram Qashat]

On 03/18/14 18:32, Naram Qashat wrote:

On 03/18/14 11:56, A.J. 'Fonz' van Werven wrote:

Naram Qashat wrote:


I basically get the following when it comes up to ./langhowto.tex:

! LaTeX Error: Environment longtable undefined.

[snip]

It's probably not as simple as this, but I'll ask anyway: have you
tried the following?
# texconfig-sys rehash


I hadn't tried that, but I did that just now and I still get the same
error.
Would've been nice if it had been that simple. :P


Bummer, sorry it didn't help. However, as you may have noticed I quoted
your entire message in my first reply and CC'ed it to the freebsd-tex@
mailing list. So hopefully someone on either list (the other being
freebsd-ports@) knows what else to try.

Furthermore: are you getting this error during building or during use? I
tried building devel/doxygen with PDF support and it built perfectly fine
here.

AvW


It was during building. The port is currently at 1.8.3.1, and I actually ran
into the problem in the email when I initially was trying to update to 1.8.4.
That was the main reason I haven't pushed out an update to the port yet.

Oddly enough, when I try to build 1.8.3.1 on my machine currently, I also get a
TeX error, but an entirely different one. I can't recall what the error was, but
it had nothing to do with longtable.

Thanks,
Naram Qashat


I'm going to try bringing this back up, since it has been a bit over a month 
now. Doxygen updated to 1.8.7, so I went back to trying to update the port. Now, 
I am getting two different stopping points with TeX depending on if I use teTeX 
or TeXLive.


If I use teTeX, then I get the following error:

! Package keyval Error: pdfencoding undefined.

I'm not exactly sure what part of the manual is causing this, but it seems to 
happen pretty quickly upon starting the PDF creation process.


If I use TeXLive, though, it gets past that point and then ends up with the same 
error as I was getting with 1.8.6, with the longtable error shown earlier in 
this thread.


Because I wasn't sure if something in my own system's environment was the issue, 
I built the ports using Tinderbox and Poudriere in a virtual machine. So 
apparently it isn't an issue with my system, as a pristine and jailed system has 
the same issue. Both my system as well as the one in the VM are 9-STABLE, since 
I think I did forget to mention that earlier in the thread (oops).


One thing, though, about the keyval error, someone reported it on a mailing 
list, but there was no reply. It appears to have come about since 1.8.7 got 
released.


I really would appreciate some insight on this, though. I know nothing about TeX 
and these errors just keep making the doxygen port get more and more outdated.


Thanks,
Naram Qashat
___
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: print/hpijs + new cups + foomatic not working with hpijs-pcl3e printer.

[Naram Qashat]

On 04/08/14 07:08, Boris Samorodov wrote:

08.04.2014 13:55, Patrick Lamaiziere пишет:

Le Tue, 8 Apr 2014 14:05:00 +1000,
Robert Backhaus  a écrit :


  I've got a printing problem with the new cups.


I've got a similar problem with cups 1.7 and a Lexmark T640
using the foomatic filters. I've to use Generic Postcript printer to
make it works again.

That worked fine with cups 1.5. With 1.7 the printer prints nothing.
I guess something is broken.


Anything suspicious at /var/log/messages, /var/log/cups/*?
OS version and which cups / foomatic ports are installed?


Something that I think needs to be brought up. It appears that since CUPS 1.6.x, 
cups-filters is required for it to work with most printers. Since we are now on 
1.7.1, that means that print/cups-filters should also be installed. I ran into 
the same problem with my printer after the upgrade and installing cups-filters 
fixed it. I even put in an update for print/cups-filters just yesterday (trying 
to take over maintainership of it). I don't know if this means that 
print/cups-filters should be made into a libdepends on cups-base or not. My gut 
feeling is that it probably should, though, if CUPS is now "useless" without it.


Thanks,
Naram Qashat
___
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: devel/doxygen: Need TeX help

[Naram Qashat]

On 03/18/14 11:56, A.J. 'Fonz' van Werven wrote:

Naram Qashat wrote:


I basically get the following when it comes up to ./langhowto.tex:

! LaTeX Error: Environment longtable undefined.

[snip]

It's probably not as simple as this, but I'll ask anyway: have you
tried the following?
# texconfig-sys rehash


I hadn't tried that, but I did that just now and I still get the same
error.
Would've been nice if it had been that simple. :P


Bummer, sorry it didn't help. However, as you may have noticed I quoted
your entire message in my first reply and CC'ed it to the freebsd-tex@
mailing list. So hopefully someone on either list (the other being
freebsd-ports@) knows what else to try.

Furthermore: are you getting this error during building or during use? I
tried building devel/doxygen with PDF support and it built perfectly fine
here.

AvW


It was during building. The port is currently at 1.8.3.1, and I actually ran 
into the problem in the email when I initially was trying to update to 1.8.4. 
That was the main reason I haven't pushed out an update to the port yet.


Oddly enough, when I try to build 1.8.3.1 on my machine currently, I also get a 
TeX error, but an entirely different one. I can't recall what the error was, but 
it had nothing to do with longtable.


Thanks,
Naram Qashat
___
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: devel/doxygen: Need TeX help

[Naram Qashat]

On 03/17/14 21:56, A.J. 'Fonz' van Werven wrote:

[Added CC to freebsd-tex@]

Naram Qashat wrote:


Hello everyone,

I am attempting to update the devel/doxygen port to 1.8.6 (something that I
should've done some time back). The port is successful in every way EXCEPT
if support for PDF docs is enabled. I basically get the following when it
comes up to ./langhowto.tex:

! LaTeX Error: Environment longtable undefined.

I currently have the teTeX ports installed, but I do believe I tried this
with the TeXLive ports as well and had the same problem. I have
/usr/local/share/texmf-dist/tex/latex/tools/longtable.sty from
teTeX-texmf-3.0_9, so I'm at a loss as to why this is happening. Upstream
hasn't been able to help either. So if there are any TeX gurus out there who
would know how to fix this, I'd love to know so I can get the port updated.

Thanks,
Naram Qashat


The texmf-dists of teTeX and Tex Live are supposed to be compatible, so
that *should* not be the problem.

It's probably not as simple as this, but I'll ask anyway: have you tried
the following?
# texconfig-sys rehash

AvW


I hadn't tried that, but I did that just now and I still get the same error. 
Would've been nice if it had been that simple. :P


Thanks,
Naram Qashat
___
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"

devel/doxygen: Need TeX help

[Naram Qashat]

Hello everyone,

I am attempting to update the devel/doxygen port to 1.8.6 (something that I 
should've done some time back). The port is successful in every way EXCEPT if 
support for PDF docs is enabled. I basically get the following when it comes up 
to ./langhowto.tex:


! LaTeX Error: Environment longtable undefined.

I currently have the teTeX ports installed, but I do believe I tried this with 
the TeXLive ports as well and had the same problem. I have 
/usr/local/share/texmf-dist/tex/latex/tools/longtable.sty from 
teTeX-texmf-3.0_9, so I'm at a loss as to why this is happening. Upstream hasn't 
been able to help either. So if there are any TeX gurus out there who would know 
how to fix this, I'd love to know so I can get the port updated.


Thanks,
Naram Qashat
___
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: kde3 ports expired today

[Naram Qashat]

On 07/01/13 16:40, Matthias Apitz wrote:

El día Monday, July 01, 2013 a las 10:26:13PM +0200, Per olof Ljungmark 
escribió:


While I have full respect for this decision I am another example of one
that looses his desktop...

Actually, I'm not really using KDE3, but rather xfce but with the apps
from KDE3 like konsole, kwrite, ksnapshot and a few others that I failed
to see any good replacements for.

And security, well, not sure if this is that important for a desktop? At
least we're warned.

And KDE4 is not an alternative, tried several times but gave up.


Are there any numbers how many FreeBSD(!) users are using KDE3 or KDE4?
If not, what about a well organized(!) straw poll? Just to see, if we are all
hunting in the right direction.

matthias


I currently use KDE3, I never liked the direction KDE4 took. I did contemplate 
porting Trinity over to FreeBSD, but I never really had the time to do it, 
mainly because of how they are so scattered on how to build it (plus their build 
instructions are haphazard at best).


Even though the ports have expired, I'll probably continue to use KDE3 on my 
desktop.


Thanks,
Naram Qashat
___
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: devel/doxygen: Does anyone need the PDF docs built?

[Naram Qashat]

On 06/21/13 03:43, Matthias Andree wrote:

Am 21.06.2013 07:11, schrieb Naram Qashat:

Hello all,

I have been sitting on an update for devel/doxygen, but have not
submitted it because I am unable to build the PDF docs for it. I have
yet to get a reply from doxygen's developer about this.

The error I get seems to be related to the teTeX distribution that
FreeBSD currently defaults to. I have not tested with TeXLive, but if it
doesn't build with teTeX, then it wouldn't help to test TeXLive.

What I would like to know is if there is anyone who actually needs these
PDF docs to be built. I'm starting to lean towards just removing these
docs from building, making it so the only docs available are HTML docs.
These docs existed whether or not you wanted the PDF docs, as long as
the HTMLDOCS option was selected.

I would like to get the update to doxygen out as soon as possible, so
the sooner I see replies about this, the sooner I can push out an update.


Dear Naram,

my reasoning is:

-  doxygen uses itself to extract its own documentation

-> if it cannot build PDF documentation for itself, it cannot build
PDF documentation for any user projects using PDF output either.

This would break working PDF build systems for end users.


Hi Matthias,

From a small test I just did, doxygen itself does not need to be built with PDF 
docs built in order for it to generate the tex files needed to make a PDF doc 
for a doxygen project. I believe all it requires is latex and pdflatex installed 
on the system beforehand.


However, even with doxygen version 1.8.4 installed, I do have problems with one 
of my own projects that has doxygen comments.



So my conclusion is that you should *wait with the upgrade* until the
situation is understood.


You can, in the meantime (while you are waiting for Dimitri's help):

- post your upgraded port for testing on some website, to see if the PDF
problem affects other users, too;


Here is the current patch for the port: 
http://kirby.cyberbotx.com/doxygen-1.8.4.patch


A few things to point out, I only put OPTIONS_DEFAULT in there for me to test 
with because the port command from porttools does not seem to handle quoted 
strings correctly, so I can't use WITH="HTMLDOCS QT4", for example, on the 
command-line and have port send the proper command to the call to make.


Also, assuming that I keep doxygen building it's own docs in PDF format, I am 
not 100% sure if I need the extra build depend on latex-ltablex, I had only 
added that in there after a previous reply from Dimitri on the bug report I 
submitted for this upgrade.


I also removed the need for the patch to examples/Makefile.in because I modified 
Makefile.in in the doxygen root to just not build the examples.



- show the PDF build failures, and post them here, to see if anyone else
has a clue.


One thing I noticed when I told doxygen to not build it's own PDF docs but tried 
to build PDF docs for my own C++ project is that the same problem was coming up. 
One thing that comes up is that it says it's nested too deeply, hitting Enter 
allows it to continue and it does create a PDF, but no page numbers in the table 
of contents sections are filled in, they are all ??.


Here is the output when I try to build the PDF docs with teTeX:

pdflatex refman
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
entering extended mode
(./refman.tex
LaTeX2e <2003/12/01>
Babel  and hyphenation patterns for american, french, german, ngerman, b
ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e
stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis
h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur
kish, ukrainian, nohyphenation, loaded.
(/usr/local/share/texmf-dist/tex/latex/base/book.cls
Document Class: book 2004/02/16 v1.4f Standard LaTeX document class
(/usr/local/share/texmf-dist/tex/latex/base/bk10.clo))
(/usr/local/share/texmf-dist/tex/latex/tools/calc.sty) (./doxygen.sty
(/usr/local/share/texmf-dist/tex/latex/base/alltt.sty)
(/usr/local/share/texmf-dist/tex/latex/tools/array.sty)
(/usr/local/share/texmf-dist/tex/latex/float/float.sty)
(/usr/local/share/texmf-dist/tex/latex/base/ifthen.sty)
(/usr/local/share/texmf-dist/tex/latex/tools/verbatim.sty)
(/usr/local/share/texmf-dist/tex/latex/xcolor/xcolor.sty
(/usr/local/share/texmf-dist/tex/latex/graphics/color.cfg)
(/usr/local/share/texmf-dist/tex/latex/graphics/pdftex.def)
(/usr/local/share/texmf-dist/tex/latex/carlisle/colortbl.sty))
(/usr/local/share/texmf-dist/tex/latex/xtab/xtab.sty))
(/usr/local/share/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/local/share/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/local/share/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/local/share/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/local/share/texmf-dist/tex/latex/graphics/graphics.cfg)))
(/usr/local/share/texmf-dist/tex/lat

devel/doxygen: Does anyone need the PDF docs built?

[Naram Qashat]

Hello all,

I have been sitting on an update for devel/doxygen, but have not submitted it 
because I am unable to build the PDF docs for it. I have yet to get a reply from 
doxygen's developer about this.


The error I get seems to be related to the teTeX distribution that FreeBSD 
currently defaults to. I have not tested with TeXLive, but if it doesn't build 
with teTeX, then it wouldn't help to test TeXLive.


What I would like to know is if there is anyone who actually needs these PDF 
docs to be built. I'm starting to lean towards just removing these docs from 
building, making it so the only docs available are HTML docs. These docs existed 
whether or not you wanted the PDF docs, as long as the HTMLDOCS option was selected.


I would like to get the update to doxygen out as soon as possible, so the sooner 
I see replies about this, the sooner I can push out an update.


Thanks,
Naram Qashat
___
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 commit ports/172355?

[Naram Qashat]

This PR was submitted to allow portconf to handle dash symbols (as well as plus 
symbols), which is highly important because of the new OPTIONS framework. It was 
submitted in Oct 2012 but has been untouched since then. I have been using the 
patch myself and it works fine, without it, I would be unable to use something 
like "xorg-servers_SET=WHATEVER" in port.conf at all.


Thanks,
Naram Qashat
___
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: Firefox 21.0 bus error and segfault

[Naram Qashat]

On 05/20/13 02:23, Koichiro IWAO wrote:

I have met the same problem.
With gcc47 fails, gcc48 or clang works.


Regards,


I can confirm that it works with clang from ports. I am not sure why it gives 
the bus error when compiled with gcc46 though.


Thanks,
Naram Qashat
___
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"

Firefox 21.0 bus error and segfault

[Naram Qashat]

Hi all,

I had just recently built Firefox 21.0 (my port version is 21.0_1,1) and I have 
been running into both bus errors and segfaults, depending on how I build 
Firefox. I usually build my ports via portupgrade and use portconf for options. 
With Firefox, I have GIO, LOGGING, and WEBRTC unset, and I have OPTIMIZED_CFLAGS 
set. I am running 8.3-RELEASE-p4 on amd64.


When I build Firefox with just the above, I get a bus error with the following 
backtrace in gdb:


Program received signal SIGBUS, Bus error.
[Switching to Thread 8013021c0 (LWP 100207 initial thread)]
0x00419d55 in realloc ()
(gdb) bt
#0  0x00419d55 in realloc ()
#1  0x000800fca61e in ?? () from /lib/libc.so.7
#2  0x000800fca9b1 in ?? () from /lib/libc.so.7
#3  0x000800fcb23c in setenv () from /lib/libc.so.7
#4  0x00402510 in ?? ()
#5  0x00402a9e in _start ()

I have also tried to build Firefox with DEBUG set and OPTIMIZED_CFLAGS unset. 
When I do this, Firefox runs, but I then run into a segfault if I do enough back 
and forth browsing in a single tab. Unfortunately I cannot reproduce this 
reliably. I get the following inside of gdb:


Assertion failure: mDocument->IsXUL() || mDocument->GetReadyStateEnum() == 
nsIDocument::READYSTATE_INTERACTIVE || (mDocument->GetReadyStateEnum() == 
nsIDocument::READYSTATE_UNINITIALIZED && 
NS_IsAboutBlank(mDocument->GetDocumentURI())) (Bad readystate), at 
/usr/ports/www/firefox/work/mozilla-release/layout/base/nsDocumentViewer.cpp:1029


Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 8013021c0 (LWP 101982 initial thread)]
0x0008023dd14e in ?? () from /usr/local/lib/firefox/libxul.so
(gdb) bt
#0  0x0008023dd14e in ?? () from /usr/local/lib/firefox/libxul.so
#1  0x000803643f88 in ?? () from /usr/local/lib/firefox/libxul.so
#2  0x0008036435b0 in ?? () from /usr/local/lib/firefox/libxul.so
#3  0x0008036774dd in ?? () from /usr/local/lib/firefox/libxul.so
#4  0x0008036763a9 in ?? () from /usr/local/lib/firefox/libxul.so
#5  0x000803675f98 in ?? () from /usr/local/lib/firefox/libxul.so
#6  0x000803675a3f in ?? () from /usr/local/lib/firefox/libxul.so
#7  0x00080205022d in ?? () from /usr/local/lib/firefox/libxul.so
#8  0x000802197668 in ?? () from /usr/local/lib/firefox/libxul.so
#9  0x000802041b54 in ?? () from /usr/local/lib/firefox/libxul.so
#10 0x0008020412d8 in ?? () from /usr/local/lib/firefox/libxul.so
#11 0x0008045cb4f7 in ?? () from /usr/local/lib/firefox/libxul.so
#12 0x0008045f1321 in ?? () from /usr/local/lib/firefox/libxul.so
#13 0x0008045763d2 in ?? () from /usr/local/lib/firefox/libxul.so
#14 0x000803bf18e0 in ?? () from /usr/local/lib/firefox/libxul.so
#15 0x00080464da85 in ?? () from /usr/local/lib/firefox/libxul.so
#16 0x00080464da16 in ?? () from /usr/local/lib/firefox/libxul.so
#17 0x00080464d9a7 in ?? () from /usr/local/lib/firefox/libxul.so
#18 0x000803a76452 in ?? () from /usr/local/lib/firefox/libxul.so
#19 0x000803746d4c in ?? () from /usr/local/lib/firefox/libxul.so
#20 0x000801ff88d6 in ?? () from /usr/local/lib/firefox/libxul.so
#21 0x000801ff8b97 in ?? () from /usr/local/lib/firefox/libxul.so
#22 0x000801ff8db2 in XRE_main () from /usr/local/lib/firefox/libxul.so
#23 0x0040322b in ?? ()
#24 0x0040360c in ?? ()
#25 0x004025de in _start ()

I'm not sure why the backtrace with DEBUG set still shows no debugging symbols. 
In any case, regarding the bus error, I have no idea why this is happening. I 
have not updated FreeBSD itself, and I had Firefox 20 running fine prior to the 
update to Firefox 21, but after Firefox 21, even Firefox 20 gives me a bus error 
(it's pretty much the same backtrace as above).


The only other thing I can point out is that I have libstdc++.so.6 and 
libgcc_s.so.1 libmapped to the gcc47 versions of those.


Thanks,
Naram Qashat
___
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"

Stumbling block on updating devel/doxygen

[Naram Qashat]

Hello all,

As the maintainer of devel/doxygen, I am trying to update the port to 1.8.3. 
But I am running into an error upon it trying to create it's docs.  This appears 
to be due to the version of latex we use from teTeX being too old.


The problem is that it is failing on creating a .dvi version of the manual in 
order to create a .ps version of it.  The creation of the .pdf version of the 
manual appears to be fine, but the creation of the other two appears to be 
specific to the FreeBSD port, and was being done prior to my taking over the port.


What I need to know is if there is actually a demand for the .dvi/.ps versions 
of the doxygen manual.  I have been receiving some help from doxygen's 
developer, but considering that this problem isn't in an unmodified version of 
doxygen, I would prefer to stop supplying the .dvi/.ps files.


Thanks,
Naram Qashat
___
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"

One-line error in graphics/autotrace

[Naram Qashat]

graphics/autotrace has been updated to OptionsNG, but there is a check of .if 
${PORT_OPTIONS:MSETUIDMING} while the Option for it is just MING, not 
SETUIDMING.  Really minor, but if anyone is using this port with that option, 
they would be in a bit of a pickle.


Thanks,
Naram Qashat
___
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"

Dropping maintainership of devel/allegro and devel/allegro-devel

[Naram Qashat]

I've realized that ever since I took over maintaining these two ports, I haven't 
kept them maintained.  I am wanting to drop these two ports, if anyone else 
wishes to become their maintainers, I am perfectly fine with it.


Thanks,
Naram Qashat
___
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: [HEADSUP] Please convert your ports to new options framework

[Naram Qashat]

On 06/03/12 14:44, Baptiste Daroussin wrote:

Hi,

The new options framework is now in the port for a week, most of the problems
directly concerning the framework seems to have been addressed.

Some issue seems still to be there regarding backward compatibility but I
haven't been able to reproduced any of the one that are supposed to be left.

The porters handbook has been updated and the new option framework is well
documented (thank you crees)

Please convert as soon as possible your ports to the new framework. As you may
already have notice bsd.options.desc.mk provide shared descriptions of the usual
options, try to be consistent and reuse the same options name so that it is
simpler for users, please override the description for your ports each time it
make sense, remember that most of the time a functional description is more
accurate than a technical one, users might not know the technical details but
they know what functionnality they do want.

All the complaints I found in the past concerning the old framework have been
addressed in the new one, you can have mutually exclusive options, checked by
the framework, you can have group options, you can have 0 or only 1 option among
N or 0 or N options among M. be creative, most of the use case should be doable.

for 3 special options: DOCS, EXAMPLES and NLS, you do not need to activate them
in OPTIONS_DEFAULT as the framework already activate them. you also do not need
to add them to OPTIONS_DEFINE if you only use one of them, do avoid having the
dialog UI to show up.

DOCS in long term maybe used to replace NOPORTDOCS (NOPORTDOCS is defined has a
backward compatibility if as a user you remove it).

Same goes for EXAMPLES ->  NOPORTEXAMPLES
and NLS ->  WITHOUT_NLS

In my concern the priority is:

1/ convert all the old OPTIONS:
Here is a list of them
http://wiki.freebsd.org/Ports/Options/ConvertingToOptionsNG

2/ replace all the knobs by optionsNg options (replacing the KNOBS file by
bsd.options.desc

regards,
Bapt


So I have a question from a consumer standpoint as opposed to a maintainer 
standpoint.  If we use portconf to store all of our WITH_* options for ports, 
will that continue to work with ports that have switched to optionsng or is 
there something I need to change in my ports.conf file for the options to 
continue to be recognized?


Thanks,
Naram Qashat
___
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: multimedia/transcode

[Naram Qashat]

On 12/06/11 16:03, C. P. Ghost wrote:

Hi,

transcode is already it 1.1.7 and allegedly features a better
video stabilizing plugin. Our version in ports is still at 1.1.5.

Could you please update the port? The distfile is here:
   https://bitbucket.org/france/transcode-tcforge/downloads

Thanks,
-cpghost.



I'll look into this during the weekend.

Thanks,
Naram
___
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: subversion 1.7.0 is coming. Many ports are not ready -- what should I do?

[Naram Qashat]

On 10/14/11 09:51, Lev Serebryakov wrote:

Hello, Freebsd-ports.

   I want update subversion to latest version 1.7.0 before 9.0-RELEASE.

   But here are some ports, which uses svn_client library. And every
port I checked could not be built with new subversion 1.7.0, as it
has some not-backward-compatible changes in API.

   What should I do with these ports? Here are list of them

devel/kdevelop  (could not be built)
devel/pecl-svn  (could not be built)
devel/subcommander  (could not be built)
devel/pysvn (could not be built)



For devel/subcommander, it might be best to mark it deprecated/broken or 
something along those lines.  The author hasn't updated that version of it in 3 
years.


Thanks,
Naram Qashat
___
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: Circular dependency in devel/doxygen?

[Naram Qashat]

On 09/19/11 11:17, Scot Hetzel wrote:

On Mon, Sep 19, 2011 at 4:56 AM, Thomas Mueller
  wrote:

> From Scot Hetzel:


The circular dependancy is being caused by audio/jack,
graphics/graphviz and devel/sdl12:



audio/pulseaudio
  - audio/jack
  -- devel/doxygen
  --- graphics/graphviz
   graphics/devil
  - devel/sdl12
  -- audio/pulseaudio



There are several ways to break the circular dependancy:



1. Turn the DOC option OFF for audio/jack.
2. define NOPORTDOCS when installing devel/doxygen (breaks dependancy
on graphics/graphviz)
3. Turn the DEVIL option OFF for graphics/graphviz
4. Turn the PULSEAUDIO option OFF for devel/sdl12


I already had DEVIL off for graphics/graphviz.


Sounds like you have the other circular dependancy ;-).  There are at
least 2 ways to create this circular dependancy, and at one point I
had documented both cases.  Unfortunately, I am unable to locate it
today.

You would need to capture a log of the build process to identify the
cause of your circular dependancy.

Scot


Hey everyone, I maintain devel/doxygen (sorry I didn't add my 2 cents earlier, 
I've been a bit busy) and was looking at this particular thread.  I know someone 
filed a PR regarding the circular dependency, stating that it might be best to 
split apart doxygen so one port builds just the program and another port build 
just the documentation.  I am not sure if that is the best thing to do or not. 
I've been wanting to push out an update to doxygen but this has been a stopping 
block for me.


Naram Qashat
___
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: doxygen font error

[Naram Qashat]

On 11/09/10 17:30, Andrea Venturoli wrote:

Hello.

Sorry for the confusion...

Doxygen is giving me a lot of these:
Error: Error: Could not find/open font



Digging a bit, I found that it calls dot:

%dot -v foo.dot -Tps -o foo.eps
dot - graphviz version 2.26.3 (20100126.1600)
Activated plugin library: libgvplugin_gd.so.6
Using textlayout: textlayout:gd
Activated plugin library: libgvplugin_dot_layout.so.6
Using layout: dot:dot_layout
Activated plugin library: libgvplugin_core.so.6
Using render: ps:core
Using device: ps:ps:core
The plugin configuration file:
/usr/local/lib/graphviz/config6
was successfully loaded.
render : dot fig gd map ps svg tk vml vrml xdot
layout : circo dot fdp neato nop nop1 nop2 osage patchwork sfdp twopi
textlayout : textlayout
device : canon cmap cmapx cmapx_np dot eps fig gd gd2 gif gv imap
imap_np ismap jpe j
loadimage : (lib) eps gd gd2 gif jpe jpeg jpg png ps svg
Error: Could not find/open font
fontname: "FreeSans.ttf" resolved to: [internal times]
Error: Could not find/open font
Error: Could not find/open font
Error: Could not find/open font
Error: Could not find/open font
Error: Could not find/open font
Error: Could not find/open font
Error: Could not find/open font
Error: Could not find/open font
Error: Could not find/open font
network simplex: 10 nodes 9 edges maxiter=2147483647 balance=1
network simplex: 10 nodes 9 edges 0 iter 0.00 sec
mincross: pass 0 iter 0 trying 0 cur_cross 0 best_cross 0
mincross G: 0 crossings, 0.00 secs.
network simplex: 19 nodes 26 edges maxiter=2147483647 balance=2
network simplex: 19 nodes 26 edges 4 iter 0.00 sec
routesplines: 9 edges, 27 boxes 0.00 sec
Using render: ps:core
Using device: ps:ps:core



First strangeness is that dot belongs to graphics/graphviz, but doxygen
doesn't depend on that (seen with pkg_info and make
pretty-print-run-depends-list).
Is this my fault in any way? Is it a bug in the port?


As the maintainer of the port, I can tell you that doxygen depends on 
graphics/graphviz only if NOPORTDOCS is not defined.  Did you have NOPORTDOCS 
defined?  If so, I might have to make it so graphviz is required regardless.



Second: in fact I have:
# locate FreeSans.ttf
/usr/local/share/vlc/skins2/fonts/FreeSans.ttf
# pkg_which /usr/local/share/vlc/skins2/fonts/FreeSans.ttf
vlc-1.1.4_2,3

Of course neither doxygen, nor graphviz depend on vlc...
Should they?
Am I missing some other port?


From a scan of the ports tree, there are many ports which have a FreeSans.ttf 
as part of their pkg-plist.  However, looking at the docs that come with 
Doxygen, it appears that Doxygen itself should be generating that file for use 
with dot.  As I have only taken up maintainership of the port and do not develop 
Doxygen, this may be something to bring up with the Doxygen developers.  A quick 
glance at the code shows that it should be creating that, however.


Thanks,
Naram Qashat


I do I instruct dot to use that font?
Should I?
Is it that one the missing font or is it the only one it finds?
In that case, how can I get the name of the others?



bye & Thanks
av.
___
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: pkg_version notification and perl

[Naram Qashat]

On 07/15/10 06:41, Jerry wrote:

I just ran 'portsnap' to update my port tree, followed
by "/usr/sbin/pkg_version -vIL=" which produced this output:

These ports need updating:
perl-5.10.1_1>succeeds index (index has 5.10.1)
startup-notification-0.10<needs updating (index has 0.10_1)

You will notice the discrepancy with perl. This never occurred before.
Is there something wrong on my system or does the problem exist
elsewhere?


There is a typo in the Makefile for perl5.10, PORTREVISION is missing an I, it 
says PORTREVISON instead.


Naram Qashat
___
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: ports/146920: Allegro runtime and Allegro-devel libraries incompatible

[Naram Qashat]

As the current maintainer of the Allegro ports, I can tell you a few things 
here.  For one, the devel/allegro port will be updated to 4.4.1.1 as soon as I 
can get some more time to finish patching it for FreeBSD and making sure those 
patches work.  For two, devel/allegro-devel is meant to be Allegro's 
developmental version and does not necessarily need to be compatible with 
devel/allegro in any way, and as such, once I get devel/allegro updated, I will 
be updating devel/allegro-devel to 4.9.19.  So basically, I would say is it up 
to the maintainers of ports relying on any Allegro ports to side with one of the 
ports and not rely on the other port.  I can't force them into doing so, however.


Thanks,
Naram Qashat
___
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: devel/gdb6* broken with new readline?

[Naram Qashat]

On 05/19/10 10:35, Frank Mayhar wrote:

I'm trying to do a full upgrade of everything for the first time in a
while.  After many gyrations, I've run into something that appears to
not be my fault :-):

cc -O2 -fno-strict-aliasing -pipe -DRL_NO_COMPAT   \
 -o gdb gdb.o libgdb.a \
-lreadline ../opcodes/libopcodes.a ../bfd/libbfd.a  
../libiberty/libiberty.a -lncurses -lm -L/usr/local/lib -liconv 
/usr/local/lib/libexpat.so -Wl,-rpath -Wl,/usr/local/lib 
../libiberty/libiberty.a  -lkvm
libgdb.a(tui-io.o)(.text+0x2aa): In function `tui_setup_io':
: undefined reference to `readline_echoing_p'
libgdb.a(tui-io.o)(.text+0x2b0): In function `tui_setup_io':
: undefined reference to `readline_echoing_p'
libgdb.a(tui-io.o)(.text+0x3c0): In function `tui_setup_io':
: undefined reference to `readline_echoing_p'
gmake[2]: *** [gdb] Error 1
gmake[2]: Leaving directory `/usr/ports/devel/gdb66/work/gdb-6.6/gdb'
gmake[1]: *** [all-gdb] Error 2
gmake[1]: Leaving directory `/usr/ports/devel/gdb66/work/gdb-6.6'
gmake: *** [all] Error 2
*** Error code 1

Stop in /usr/ports/devel/gdb66.
*** Error code 1

It fails the same way with devel/gdb6.  I did a bit of searching and
apparently this is a known problem with the latest readline that was
fixed in gdb 6.8.


I had submitted a patch to update devel/gdb6 to GDB 6.8, and GDB 6.6 was 
repocopied to devel/gdb66, but I haven't seen any updates recently on the 
situation.  Maybe we could look into this again, as well as the possibility of 
adding a devel/gdb7 port to accommodate the GDB 7.x branch?


Thanks,
Naram Qashat
___
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"

emulators/zsnes segfaults in 32-bit jail on FreeBSD/amd64 8.0

[Naram Qashat]

I just built a FreeBSD/amd64 8.0 system, and I built emulators/zsnes within a 
32-bit jail in /compat/i386.  But when I try to run it by setting 
LD_32_LIBRARY_PATH to /compat/i386/usr/local/lib and PATH to 
/compat/i386/usr/local/bin:$PATH, it segfaults.  I also tried to build the port 
with WITH_DEBUG=yes to get it to add -g to the CFLAGS and remove the STRIP 
variable, but it still segfaulted.  However, if I did a make extract and then 
manually went into the work directory and built it with the environment set with 
CLFAGS and CXXFLAGS set to -g, ZSNES doesn't crash at all.  With the first 2 
segfaults, even running a 32-bit gdb66 on zsnes didn't give me anything, saying 
there were no debugging symbols.  I'm at a loss, as the port compiles and runs 
just fine on my FreeBSD/i386 7.2 system.  Any help would be appreciated.


Thanks,
Naram Qashat
___
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"

K3B on FreeBSD/amd64 8.0 doesn't recognize SATA DVD writer

[Naram Qashat]

When I try to launch K3B on my FreeBSD/amd64 8.0 machine, it says it can not 
find a DVD writer.  I get the following in a console:


[04/25/2010 11:36:12 kirby ~]> kdecore (KAction): WARNING: 
KActionCollection::KActionCollection( QObject *parent, const char *name, 
KInstance *instance )

k3b: (K3bCdrecordProgram) could not start /opt/schily/bin
k3b: (K3bMkisofsProgram) could not start /opt/schily/bin
k3b: (K3bExternalBinManager) Cdrecord 2.1 features: gracetime, overburn, cdtext, 
clone, tao, cuefile, xamix, plain-atapi, hacked-atapi, audio-stdin, burnfree
k3b: (K3bExternalBinManager) 2 1 -1  seems to be cdrecord version >= 1.11a02, 
using burnfree instead of burnproof
k3b: (K3bExternalBinManager) seems to be cdrecord version >= 1.11a31, support 
for Just Link via burnfree driveroption

(BSDDeviceScan) number of matches 27
(BSDDeviceScan) periph: pass0
(BSDDeviceScan) periph: ada0
(BSDDeviceScan) periph: pass1
(BSDDeviceScan) periph: ada1
(BSDDeviceScan) periph: cd0
(BSDDeviceScan) periph: sg0
(BSDDeviceScan) periph: pass2
(BSDDeviceScan) add device /dev/cd0:6:0:0 (/dev/pass2)
(K3bDevice::Device) /dev/cd0: init()
(K3bDevice::openDevice) open device /dev/pass2 succeeded.
(K3bDevice::openDevice) open device /dev/pass2 succeeded.
(K3bDevice::ScsiCommand) transport command 12, length: 6
(K3bDevice::ScsiCommand) transport failed (4): 0
(K3bDevice::ScsiCommand) failed:
   command:INQUIRY (12)
   errorcode:  0
   sense key:  NO SENSE (2)
   asc:0
   ascq:   0
k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.
Could not initialize device /dev/cd0
k3b: [void K3bMediaCache::clearDeviceList()]
k3b: (K3bCdrecordProgram) could not start /opt/schily/bin
k3b: (K3bMkisofsProgram) could not start /opt/schily/bin
k3b: (K3bExternalBinManager) Cdrecord 2.1 features: gracetime, overburn, cdtext, 
clone, tao, cuefile, xamix, plain-atapi, hacked-atapi, audio-stdin, burnfree
k3b: (K3bExternalBinManager) 2 1 -1  seems to be cdrecord version >= 1.11a02, 
using burnfree instead of burnproof
k3b: (K3bExternalBinManager) seems to be cdrecord version >= 1.11a31, support 
for Just Link via burnfree driveroption

Devices:
--
kdecore (KAction): WARNING: KActionCollection::operator+=(): function is 
severely deprecated.

k3b: (K3bFileTreeView::addCdDeviceBranches)
k3b: (K3bFileTreeView::addCdDeviceBranches) done
k3b: (K3bFileTreeView::addCdDeviceBranches)
k3b: (K3bFileTreeView::addCdDeviceBranches) done
k3b: (K3bCore) System problems:
k3b:  NON_CRITICAL
k3b:  PROBLEM:  No CD/DVD writer found.
k3b:  DETAILS:  K3b did not find an optical writing device in your system. Thus, 
you will not be able to burn CDs or DVDs. However, you can still use other K3b 
features like audio track extraction or audio transcoding or ISO9660 image creation.

k3b:  SOLUTION:
k3b:

I also start getting the following in my root console, looking like a kernel 
message:


ahcich5: Timeout on slot 

Where the  started was at 15 but then also jumped up to 16.  This only 
started to come up after I tried to start K3B, and hasn't stopped until I 
reboot.  I also noticed that the first time I tried to load K3B, it seemed like 
it locked up and I had to kill it and try starting it again.


I am also attaching my kernel config.  I hope this is just a misconfigured 
kernel, but I am at a loss here.


Thanks,
Naram Qashat
machine amd64
cpu HAMMER

ident CBXKERN

options SCHED_ULE
options SMP
options PREEMPTION
options COMPAT_43
options COMPAT_43TTY
options COMPAT_FREEBSD4
options COMPAT_FREEBSD5
options COMPAT_FREEBSD6
options COMPAT_FREEBSD7
options SYSVSHM
options SYSVSEM
options SYSVMSG
options KTRACE
options STACK
options HWPMC_HOOKS
options INET
options INET6
options NETSMB
options LIBMCHAIN
options LIBALIAS
options SCTP
options NETGRAPH
options XBONEHACK
options IPFIREWALL
options IPFIREWALL_FORWARD
options IPFIREWALL_NAT
options FFS
options NFSCLIENT
options CD9660
options MSDOSFS
options NFSSERVER
options NULLFS
options PROCFS
options PSEUDOFS
options SMBFS
options UDF
options SOFTUPDATES
options SUIDDIR
options VFS_AIO
options _KPOSIX_PRIORITY_SCHEDULING
options P1003_1B_SEMAPHORES
options P1003_1B_MQUEUE
options HZ=1000
options SCSI_DELAY=1000
options LIBICONV
options KBD_INSTALL_CDEV
options MAXCONS=12
options SC_HISTORY_SIZE=1000
options ATA_STATIC_ID

options COMPAT_IA32
options COMPAT_LINUX32
options LINPROCFS
options LINSYSFS

device hwpmc
device loop
device ether
device vlan
device bpf
device disc
device edsc
device tap
device tun
device gif
device gre
device faith
device stf
device if_bridge
device random
device mem
device scbus
device ch
device da
device cd
device pt
device pass
device sg
device pty
device md
device ccd
device firmware
device sc
device ahci
device ata
device atadisk
device ataraid
device atapicd
device atapifd
device atapicam
device fdc
device puc
dev

Re: drop devel/allegro and devel/allegro-devel

[Naram Qashat]

On 04/19/10 04:16, Eitan Adler wrote:

Since I no longer use allegro and don't have time to update them I'd
like to drop maintainership of allegro.

If anyone would like to take them feel free...

Note to the next maintainer: devel/allegro needs to be updated to
4.4.1.1 and devel/allegro-devel needs to be updated to 4.9.19.


I'll take up maintaining both these ports.

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

Assistance needed to update sysutils/di

[Naram Qashat]

I am attempting to update the sysutils/di port from 4.19 to 4.20.  Prior to 
4.19, there was a Build script in place that did configuring and building, 
including if the .po files for NLS were to be utilized or not.  With 4.20, they 
have done away with this Build script and now only have a Makefile to handle 
configuring and building in one step.  Installing was done manually instead of 
using Build, although I could use the install step of the Makefile now.


It seems as though the option to enable or disable if NLS is used has been 
removed from the latest version as well.  With 4.19 and earlier, I could call 
the build-po target of the Build script when I needed to, since I was telling 
Build earlier if I wanted NLS or not.  Trying to do the same with calling the 
Makefile doesn't seem to work, as it doesn't seem to properly invoke certain 
commands in the Makefile.  The command they created to help determine if NLS 
should be enabled or disabled does not seem to have a flag to allow the user to 
choose so.


What I did with the port, so far, is removed the do-configure step, changed the 
do-build step to call ${MAKE} instead of ./Build, also trying to call ${MAKE} 
build-po if WITHOUT_NLS is not set (but this fails because the Makefile doesn't 
properly include certain variables), and changed the do-install step to call 
${MAKE} install instead of manually copying files, also trying to use ${MAKE} 
install-po if WITHOUT_NLS is not set, same problem as build-po.


If I am doing something incorrectly, please let me know.  I am attaching my 
current diff of the port, which includes the old parts commented out as I was 
still testing the port.  Any help is appreciated.  If I need to clarify 
anything, let me know.


Thanks,
Naram Qashat
diff -ruN --exclude=CVS /usr/ports/sysutils/di/Makefile 
/kirby/shared/ports/di/Makefile
--- /usr/ports/sysutils/di/Makefile 2010-02-03 08:55:41.0 -0500
+++ /kirby/shared/ports/di/Makefile 2010-04-02 23:49:12.0 -0400
@@ -6,7 +6,7 @@
 #
 
 PORTNAME=  di
-PORTVERSION=   4.19
+PORTVERSION=   4.20
 CATEGORIES=sysutils
 MASTER_SITES=  http://www.gentoo.com/di/ \
http://fresh.t-systems-sfr.com/unix/src/privat2/
@@ -19,60 +19,89 @@
 .if !defined(WITHOUT_NLS)
 USE_GETTEXT=   yes
 PLIST_SUB= NLS=""
-DI_BUILD_NO_NLS=   0
+#DI_BUILD_NO_NLS=  0
 .else
-DI_BUILD_NO_NLS=   1
+#DI_BUILD_NO_NLS=  1
 PLIST_SUB= NLS="@comment "
 .endif
 
-USE_PERL5_BUILD=   yes
+#USE_PERL5_BUILD=  yes
 
 .include 
 
 post-patch:
@${REINPLACE_CMD} -e "s|zoneid_t|zoneId_t|g" ${WRKSRC}/di.c
 
-pre-configure:
-   @${CHMOD} +x ${WRKSRC}/Build
-   @${CHMOD} +x ${WRKSRC}/features/turnoffnls.sh
+#pre-configure:
+#  @${CHMOD} +x ${WRKSRC}/Build
+#  @${CHMOD} +x ${WRKSRC}/features/turnoffnls.sh
+
+#do-configure:
+#  (cd ${WRKSRC}; \
+#  ${SETENV} ${MAKE_ENV} DI_BUILD_MKCONFIG_PL=1 \
+#  CC="${CC}" LDFLAGS="${LDFLAGS}" \
+#  prefix="${PREFIX}" LOCALEDIR="${PREFIX}/share/locale" \
+#  DI_BUILD_NO_NLS=${DI_BUILD_NO_NLS} \
+#  ./Build config.h)
+
+#do-build:
+#  (cd ${WRKSRC}; \
+#  ${SETENV} ${MAKE_ENV} \
+#  CC="${CC}" LDFLAGS="${LDFLAGS}" \
+#  prefix="${PREFIX}" LOCALEDIR="${PREFIX}/share/locale" \
+#  DI_BUILD_NO_NLS=${DI_BUILD_NO_NLS} \
+#  ./Build)
 
-do-configure:
+do-build:
(cd ${WRKSRC}; \
-   ${SETENV} ${MAKE_ENV} DI_BUILD_MKCONFIG_PL=1 \
+   ${SETENV} ${MAKE_ENV} \
CC="${CC}" LDFLAGS="${LDFLAGS}" \
prefix="${PREFIX}" LOCALEDIR="${PREFIX}/share/locale" \
-   DI_BUILD_NO_NLS=${DI_BUILD_NO_NLS} \
-   ./Build config.h)
-
-do-build:
+   ${MAKE})
+.if !defined(WITHOUT_NLS)
(cd ${WRKSRC}; \
${SETENV} ${MAKE_ENV} \
CC="${CC}" LDFLAGS="${LDFLAGS}" \
prefix="${PREFIX}" LOCALEDIR="${PREFIX}/share/locale" \
-   DI_BUILD_NO_NLS=${DI_BUILD_NO_NLS} \
-   ./Build)
+   ${MAKE} build-po)
+.endif
 
 do-install:
-   ${INSTALL_PROGRAM} ${WRKSRC}/di ${PREFIX}/bin
-   ${LN} -sf ${PREFIX}/bin/di ${PREFIX}/bin/mi
-   ${INSTALL_MAN} ${WRKSRC}/di.1 ${PREFIX}/man/man1
+#  ${INSTALL_PROGRAM} ${WRKSRC}/di ${PREFIX}/bin
+#  ${LN} -sf ${PREFIX}/bin/di ${PREFIX}/bin/mi
+#  ${INSTALL_MAN} ${WRKSRC}/di.1 ${PREFIX}/man/man1
+   (cd ${WRKSRC}; \
+   ${SETENV} ${MAKE_ENV} \
+   CC="${CC}" LDFLAGS="${LDFLAGS}" \
+   prefix="${PREFIX}" LOCALEDIR="${PREFIX}/share/locale" \
+   ${MAKE} install)
 .if !defined(WITHO

Re: fontforge: bug in configure?

[Naram Qashat]

Andriy Gapon wrote:

It seems that there is a subtle bug in fontforge's configure:

CFLAGS_NOOPT=`echo $CFLAGS | sed -e s/-O2// | sed -e s/-O//`

This is supposed to produce CFLAGS with all optimization options stripped.
Let's leave alone the fact that there could be -O1 flag or -O3 or even
-funroll-all-loops.
Still, 'g' option is missing from the sed commands.
Say, CFLAGS contain "-O2 ... -O2", then the first sed command would strip only 
the
first occurrence of -O2 and the second command would leave a dangling '2'.
This is what I am hitting here.

Proposal:
CFLAGS_NOOPT=`echo $CFLAGS | sed -e s/-O[0-9]*//g`

What do you think?


I'd be fine with that.  I'll submit a PR for it later today.

Thanks,
Naram Qashat
___
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: devel/dbus-qt4 won't build

[Naram Qashat]

Doug Barton wrote:

Lars Eighner wrote:

Okay after it didn't work a few times I did

portupgrade -fr qt4\*

and still the make of devel/dbus-qt4 fails thus:


What happens if you do this:

cd /usr/ports/devel/dbus-qt4
make clean
make config
make


Doug


Actually, I had this problem as well, I found the solution (after a bit of 
Googling), is to deinstall devel/dbus-qt4 and then install it again.  Apparently 
the update conflicts with the older version already installed.


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

portupgrade: undefining a variable in MAKE_ARGS set previously

[Naram Qashat]

When using portupgrade, I use the MAKE_ARGS variable inside of pkgtools.conf.  I 
have variables set for '*' as well as many ports.  However, I want to be able to 
undefine a variable I set previously in the '*' entry.  I found a mailing list 
thread from 2007 for rt36 that mentions using -U with make, but make 
complains saying that U is an illegal option, and the man page says nothing 
about -U being an option.  Even if it were an option, I'm not sure how BSD make 
would handle the situation of defining a variable with = or 
-D and then later undefining it with -U.  So is there a way 
to do this either via pkgtools.conf or via make itself?


Thanks,
Naram Qashat
___
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: reintroduction of php5_pcre broken

[Naram Qashat]

Michael Butler wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Naram Qashat wrote:

Michael Butler wrote:
It seems that the reintroduction of php5_pcre has broken something :-(

PHP Warning:  PHP Startup: Unable to load dynamic library
'/usr/local/lib/php/20060613/pcre.so' -
/usr/local/lib/php/20060613/pcre.so: Undefined symbol
"php_pcre_free" in Unknown on line 0


I found that running 'make config' in /usr/ports/devel/php5_pcre and
selecting 'bundled pcre' solves the problem. The option is noted only as
being applicable to apache 2.0.x but I run 2.2 - it works anyway - 


This works for my 7.1 system, although oddly enough, I never enabled that knob 
on my 6.3 system and it still works...


Thanks,
Naram Qashat


Michael
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAkmynmIACgkQQv9rrgRC1JKRsgCfUMfyg8iVLCbTmxToEZLNxbGs
QvQAn0X1OxepghTl1MLrI44Lo/puVK1o
=5E3B
-END PGP SIGNATURE-


___
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: reintroduction of php5_pcre broken

[Naram Qashat]

Michael Butler wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

It seems that the reintroduction of php5_pcre has broken something :-(

PHP Warning:  PHP Startup: Unable to load dynamic library
'/usr/local/lib/php/20060613/pcre.so' -
/usr/local/lib/php/20060613/pcre.so: Undefined symbol
"php_pcre_free" in Unknown on line 0


I have an odd situation in regards to this.  My FreeBSD 7.1 system shows this 
same error, but my FreeBSD 6.3 system does not show this error and is loading 
the module just fine.  I compared the order of the modules in 
/usr/local/etc/php/extensions.ini on both machines, and made them match 
(although the 6.3 machine also have the apc, ming, and readline modules loaded, 
which I don't believe are going to affect it), still to no avail on the 7.1 
machine.  Both systems have the same configure command line (although the 6.3 
machine also has --disable-ipv6, which I don't think would affect the pcre 
module).  I've asked around and found that the module also works fine from a 
Fedora package.  So I'm wondering if this issue is FreeBSD specific or not.  If 
need be, I can provide more information that can hopefully trace down here the 
problem is.  Another thing I notice is that doing strings on pcre.so shows 
pcre_free in the 6.3 version but php_pcre_free on the 7.1 version.


Thanks,
Naram Qashat


Michael

(sorry, I'm not subscribed to ports@)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAkmxQCsACgkQQv9rrgRC1JJ5MQCffhco6Pka76+yVD/Kq8qryBUl
ULsAoL7YJ89NpvWzI5uFYOfzOd0dquCR
=5dc3
-END PGP SIGNATURE-
___
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: Dead projects in ports tree

[Naram Qashat]

Robert Huff wrote:

Garrett Cooper writes:


 >Just trying to amass cruft in the ports tree that could be marked
 > deprecated and removed. Some assistance in amassing the list would be
 > helpful...

 xmms looks completely dead now. Can someone confirm or deny this
 fact?


huff@>> dir /var/dv/pkg | grep xmms-1
drwxr-xr-x2 root  wheel   512 Feb 27 15:47 xmms-1.2.11_6
huff@>> ps -ax | grep xmms
99029  ??  S102:16.39 /usr/local/bin/xmms

It's currently playing Fleetwood Mac's "The chain" 


Robert Huff


I too still use xmms and can confirm it works still.

Naram Qashat
___
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: gecko & firefox marked forbidden

[Naram Qashat]

t-u-t wrote:

just a note,
firefox2 has been marked forbidden, and it stopped me twice while 
building gnome2-lite today when pulled for gecko depends by www/epiphany 
and x11/yelp.


on my own system i fixed the Makefiles of these two to use xulrunner, 
(which was there anyway - just removed firefox), but i don't know what 
other effects there are on other ports etc.


n.b. i don't need ff2, just noting


I'll point out that the same issue occured for me with multimedia/vlc.  It was 
updated to have xulrunner after firefox in USE_GECKO, but even defining 
WITH_GECKO=xulrunner it still tried to install firefox2.  I don't know what the 
bug is, but there is one.


Naram Qashat
___
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: firefox3 support in bsd.gecko.mk

[Naram Qashat]

Dominic Fandrey wrote:

There is no firefox3 support in bsd.gecko.mk. This seems to keep
plugins and add-ons that would work in Firefox 3 as well from being
ported.


As far as I understand, plugins for any Mozilla products are made using 
xulrunner now.


Naram Qashat


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"

Re: USE_GECKO=firefox and firefox3

[Naram Qashat]

Norberto Meijome wrote:

Hi all,
I have firefox3 installed. my make.conf shows USE_GECKO=firefox.

When I try to install any port (in particular today, the latest eclipse 3.3.2 )
which uses USE_GECKO, www/firefox is pulled into the dependencies, rather tha
firefox3.

I use portupgrade to launch the eclipse upgrade ( portupgrade -p eclipse ) ,
and my /usr/local/etc/pkgtools.conf contains the following relevant entries:


 ALT_PKGDEP = {
'www/mozilla' => 'www/firefox3',
'www/firefox' => 'www/firefox3',
'firefox-2*' => 'firefox-3*',
'firefox' => 'firefox3',
[...]
}



As far as I can tell, from having this problem with the VLC Firefox plugin after 
the FF3 release, you need to use WITH_GECKO=xulrunner instead of firefox or 
firefox3.  Of course, that will only work if the eclipse port has xulrunner in 
the list for USE_GECKO and isn't pulling in the old bsd.gecko.mk from the 
mozilla folder.


The reason for that is that after Firefox 2, the Mozilla team moved all the 
stuff for building into xulrunner, as Firefox 3 doesn't have a firefox3-config 
like Firefox 2 had firefox-config.  I don't use eclipse, so I can't comment if 
changing it so it uses xulrunner will work, but it's worth a shot.


Naram Qashat


still, no luck, ffox 2 gets pulled in.

should Mk/bsd.gecko.mk have support for firefox3 ? Is there any solution,other
than deinstalling ffox3, install ffox2, install eclipse, and then replace ffox2
with 3 ? 


 ( I *suspect* that portupgrade -o {ffox something} {ffox other} eclipse would
do , but not entirely sure how it works

Thanks for any help!!
B, now gmail powered.
_
{Beto|Norberto|Numard} Meijome

"I respect faith, but doubt is what gives you an education."
   Wilson Mizner

I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


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

Re: portupgrade fails with quoted options

[Naram Qashat]

Sergey Matveychuk wrote:

Naram Qashat wrote:

Sergey Matveychuk wrote:

Naram Qashat wrote:
Notice how WITH_MODULES has quotes around it and then escaped 
quotes inside it?  It shouldn't be doing things like that.  I 
don't know ruby (I only made that above script from looking at 
some parts of portupgrade, but I have almost no understanding of 
ruby), so I can't give a fix for this.


Try the patch please. (cd /usr/local/lib/ruby/site_ruby/1.8; patch < 
~/pkgmisc.rb.diff)

Does it fix the problem for you?



It seems like it got a little farther, but it still bombed.  I'm not 
sure if the  new problems is a problems in portupgrade's ruby scripts 
or if it's something in the Makefiles themselves:


--->  Reinstalling 'apache-2.2.9_3' (www/apache22)
--->  Building '/usr/ports/www/apache22' with make flags: BATCH=yes 
WITH_OPENSSL_PORT=yes WITH_OPENSSL=yes WITHOUT_GNOME=esound 
WITHOUT_CUPS=yes WITH_BDB_VER=46 WITH_MYSQL_VER=50 
WITH_OPTIMIZED_CFLAGS=yes WITHOUT_APACHE_OPTIONS=yes 
WITH_PCRE_FROM_PORTS=yes WITH_MYSQL=yes WITH_BDB=yes WITH_SUEXEC=yes 
SUEXEC_LOGFILE=/var/log/www/httpd-suexec.log WITH_MODULES="actions 
alias auth_basic auth_digest authn_dbd authn_default authz_default 
authz_host authz_user autoindex cgi dav dav_fs dav_lock dbd deflate 
dir echo env expires filter headers ident imagemap include info 
log_config log_forensic logio mime mime_magic negotiation rewrite 
setenvif status suexec unique_id userdir version vhost_alias"

"/usr/ports/Mk/bsd.apache.mk", line 261: Need an operator
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! www/apache22 (apache-2.2.9_3) (clean error)

But that does seem to be a step in a right direction.

Naram Qashat


Quotas still there!
Can you open file /usr/local/lib/ruby/site_ruby/1.8/pkgmisc.rb and add 
after line 96: arg.gsub(/([$\\\`])/, "\\1") the line:

arg.gsub(/\"/, "")
?

It should fix the error.
Looks like it's a long standing bug from a knu@ era :)
If it's OK for you, I'll add the patch to a portupgrade port.


That doesn't fix it.  I would suspect it would make it worse because it would 
treat all the options after the first one in WITH_MODULES as if they were passed 
to make directly instead of via a knob.  It still gives the same error from 
bsd.apache.mk though.


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

Re: portupgrade fails with quoted options

[Naram Qashat]

Sergey Matveychuk wrote:

Naram Qashat wrote:
Notice how WITH_MODULES has quotes around it and then escaped quotes 
inside it?  It shouldn't be doing things like that.  I don't know 
ruby (I only made that above script from looking at some parts of 
portupgrade, but I have almost no understanding of ruby), so I can't 
give a fix for this.


Try the patch please. (cd /usr/local/lib/ruby/site_ruby/1.8; patch < 
~/pkgmisc.rb.diff)

Does it fix the problem for you?



It seems like it got a little farther, but it still bombed.  I'm not sure if the 
 new problems is a problems in portupgrade's ruby scripts or if it's something 
in the Makefiles themselves:


--->  Reinstalling 'apache-2.2.9_3' (www/apache22)
--->  Building '/usr/ports/www/apache22' with make flags: BATCH=yes 
WITH_OPENSSL_PORT=yes WITH_OPENSSL=yes WITHOUT_GNOME=esound WITHOUT_CUPS=yes 
WITH_BDB_VER=46 WITH_MYSQL_VER=50 WITH_OPTIMIZED_CFLAGS=yes 
WITHOUT_APACHE_OPTIONS=yes WITH_PCRE_FROM_PORTS=yes WITH_MYSQL=yes WITH_BDB=yes 
WITH_SUEXEC=yes SUEXEC_LOGFILE=/var/log/www/httpd-suexec.log 
WITH_MODULES="actions alias auth_basic auth_digest authn_dbd authn_default 
authz_default authz_host authz_user autoindex cgi dav dav_fs dav_lock dbd 
deflate dir echo env expires filter headers ident imagemap include info 
log_config log_forensic logio mime mime_magic negotiation rewrite setenvif 
status suexec unique_id userdir version vhost_alias"

"/usr/ports/Mk/bsd.apache.mk", line 261: Need an operator
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! www/apache22 (apache-2.2.9_3) (clean error)

But that does seem to be a step in a right direction.

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

Re: portupgrade fails with quoted options

[Naram Qashat]

Sergey Matveychuk wrote:

Naram Qashat wrote:
When I try to upgrade a port that has quoted options (an example is 
www/apache22, where I opted to retain the old WITH_MODULES line I had 
before) in pkgtools.conf, portupgrade fails to quote the option and 
causes the port to fail to build or even causes portupgrade itself to 
bomb.  Strangely enough, if I use the following script that uses the 
same tools as portupgrade:


require "pkgtools"
require "optparse"
load_config
opts = OptionParser.new
opts.order(ARGV) do |arg|
  make_args = config_make_args(arg)
  puts "#{arg}:#{make_args}"
end

It shows the correct options if I run it for www/apache22.  I get the 
following with the above script:


www/apache22:WITHOUT_APACHE_OPTIONS=yes WITHOUT_IPV6=yes 
WITH_MYSQL=yes WITH_BDB=yes WITH_SUEXEC=yes 
SUEXEC_LOGFILE=/var/log/www/httpd-suexec.log WITH_MODULES="actions 
alias auth_basic auth_digest authn_dbd authn_dbd authn_default 
authz_default authz_host authz_user autoindex cgi dav dav_fs dbd 
deflate dir echo env expires filter headers ident imagemap include 
info log_config log_forensic logio mime mime_magic negotiation rewrite 
setenvif ssl status suexec unique_id userdir version vhost_alias" 
BATCH=yes WITH_OPENSSL=yes WITH_OPENSSL_PORT=yes WITHOUT_X11=yes 
WITH_BDB_VER=43 WITH_MYSQL_VER=50


But when I use portupgrade itself, I get the following as the make 
arguments instead:


--->  Building '/usr/ports/www/apache22' with make flags: 
WITHOUT_APACHE_OPTIONS=yes WITHOUT_IPV6=yes WITH_MYSQL=yes 
WITH_BDB=yes WITH_SUEXEC=yes 
SUEXEC_LOGFILE=/var/log/www/httpd-suexec.log "WITH_MODULES=\"actions 
alias auth_basic auth_digest authn_dbd authn_dbd authn_default 
authz_default authz_host authz_user autoindex cgi dav dav_fs dbd 
deflate dir echo env expires filter headers ident imagemap include 
info log_config log_forensic logio mime mime_magic negotiation rewrite 
setenvif ssl status suexec unique_id userdir version vhost_alias\"" 
BATCH=yes WITH_OPENSSL=yes WITH_OPENSSL_PORT=yes WITHOUT_X11=yes 
WITH_BDB_VER=43 WITH_MYSQL_VER=50


Notice how WITH_MODULES has quotes around it and then escaped quotes 
inside it?  It shouldn't be doing things like that.  I don't know ruby 
(I only made that above script from looking at some parts of 
portupgrade, but I have almost no understanding of ruby), so I can't 
give a fix for this.




You missed lines from pkgtools.conf you use. Please, show them.



Here's the www/apache22 and '*' section I have in my pkgtools.conf:

'*' => [
  'BATCH=yes',
  'WITH_OPENSSL_PORT=yes',
  'WITH_OPENSSL=yes',
  'WITHOUT_GNOME=esound',
  'WITHOUT_CUPS=yes',
  'WITH_BDB_VER=46',
  'WITH_MYSQL_VER=50',
  'WITH_OPTIMIZED_CFLAGS=yes'
],
'www/apache22' => [
  'WITHOUT_APACHE_OPTIONS=yes',
  'WITH_PCRE_FROM_PORTS=yes',
  'WITH_MYSQL=yes',
  'WITH_BDB=yes',
  'WITH_SUEXEC=yes',
  'SUEXEC_LOGFILE=/var/log/www/httpd-suexec.log',
  'WITH_MODULES="actions alias auth_basic auth_digest authn_dbd 
authn_default authz_default authz_host authz_user autoindex cgi dav dav_fs 
dav_lock dbd deflate dir echo env expires filter headers ident imagemap include 
info log_config log_forensic logio mime mime_magic negotiation rewrite setenvif 
status suexec unique_id userdir version vhost_alias"'

],

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

portupgrade fails with quoted options

[Naram Qashat]

When I try to upgrade a port that has quoted options (an example is 
www/apache22, where I opted to retain the old WITH_MODULES line I had before) in 
pkgtools.conf, portupgrade fails to quote the option and causes the port to fail 
to build or even causes portupgrade itself to bomb.  Strangely enough, if I use 
the following script that uses the same tools as portupgrade:


require "pkgtools"
require "optparse"
load_config
opts = OptionParser.new
opts.order(ARGV) do |arg|
  make_args = config_make_args(arg)
  puts "#{arg}:#{make_args}"
end

It shows the correct options if I run it for www/apache22.  I get the following 
with the above script:


www/apache22:WITHOUT_APACHE_OPTIONS=yes WITHOUT_IPV6=yes WITH_MYSQL=yes 
WITH_BDB=yes WITH_SUEXEC=yes SUEXEC_LOGFILE=/var/log/www/httpd-suexec.log 
WITH_MODULES="actions alias auth_basic auth_digest authn_dbd authn_dbd 
authn_default authz_default authz_host authz_user autoindex cgi dav dav_fs dbd 
deflate dir echo env expires filter headers ident imagemap include info 
log_config log_forensic logio mime mime_magic negotiation rewrite setenvif ssl 
status suexec unique_id userdir version vhost_alias" BATCH=yes WITH_OPENSSL=yes 
WITH_OPENSSL_PORT=yes WITHOUT_X11=yes WITH_BDB_VER=43 WITH_MYSQL_VER=50


But when I use portupgrade itself, I get the following as the make arguments 
instead:


--->  Building '/usr/ports/www/apache22' with make flags: 
WITHOUT_APACHE_OPTIONS=yes WITHOUT_IPV6=yes WITH_MYSQL=yes WITH_BDB=yes 
WITH_SUEXEC=yes SUEXEC_LOGFILE=/var/log/www/httpd-suexec.log 
"WITH_MODULES=\"actions alias auth_basic auth_digest authn_dbd authn_dbd 
authn_default authz_default authz_host authz_user autoindex cgi dav dav_fs dbd 
deflate dir echo env expires filter headers ident imagemap include info 
log_config log_forensic logio mime mime_magic negotiation rewrite setenvif ssl 
status suexec unique_id userdir version vhost_alias\"" BATCH=yes 
WITH_OPENSSL=yes WITH_OPENSSL_PORT=yes WITHOUT_X11=yes WITH_BDB_VER=43 
WITH_MYSQL_VER=50


Notice how WITH_MODULES has quotes around it and then escaped quotes inside it? 
 It shouldn't be doing things like that.  I don't know ruby (I only made that 
above script from looking at some parts of portupgrade, but I have almost no 
understanding of ruby), so I can't give a fix for this.


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

Re: Can't build kdelibs4 due to dependencies failing

[Naram Qashat]

Naram Qashat wrote:
I attempted to install kdelibs4 in order to get KDE4 installed.  Using 
portupgrade, it started to build the dependencies for it, but it failed 
on both textproc/soprano and deskutils/strigi.  Here are the parts where 
each failed at:


Actually, this is a somewhat false alarm.  But for anyone else wondering, don't 
build textproc/clucene with the WITH_ASCII_SUPPORT flag enabled.


Thanks,
Naram Qashat


Scanning dependencies of target tstringtest
[ 99%] Building CXX object test/CMakeFiles/tstringtest.dir/tstringtest.o
In file included from /usr/local/include/CLucene/StdHeader.h:444,
 from /usr/local/include/CLucene.h:11,
 from 
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/../index/tstring.h:28,
 from 
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/tstringtest.cpp:16:
/usr/local/include/CLucene/util/Equators.h:203: warning: unused 
parameter 'nothing'
/usr/local/include/CLucene/util/Equators.h:210: warning: unused 
parameter 'nothing'
/usr/local/include/CLucene/util/Equators.h:215: warning: unused 
parameter 'nothing'

In file included from /usr/local/include/CLucene/index/IndexReader.h:14,
 from /usr/local/include/CLucene.h:14,
 from 
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/../index/tstring.h:28,
 from 
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/tstringtest.cpp:16:
/usr/local/include/CLucene/store/Directory.h:72: warning: unused 
parameter 'bufferSize'

In file included from /usr/local/include/CLucene.h:14,
 from 
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/../index/tstring.h:28,
 from 
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/tstringtest.cpp:16:
/usr/local/include/CLucene/index/IndexReader.h:52: warning: unused 
parameter 'dummy'

In file included from /usr/local/include/CLucene/index/SegmentHeader.h:22,
 from /usr/local/include/CLucene/index/IndexWriter.h:20,
 from /usr/local/include/CLucene.h:15,
 from 
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/../index/tstring.h:28,
 from 
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/tstringtest.cpp:16:
/usr/local/include/CLucene/index/CompoundFile.h:50: warning: unused 
parameter 'pos'

In file included from /usr/local/include/CLucene/index/IndexWriter.h:20,
 from /usr/local/include/CLucene.h:15,
 from 
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/../index/tstring.h:28,
 from 
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/tstringtest.cpp:16:
/usr/local/include/CLucene/index/SegmentHeader.h:72: warning: unused 
parameter 'proxPointer'

In file included from /usr/local/include/CLucene/search/SearchHeader.h:16,
 from /usr/local/include/CLucene/search/IndexSearcher.h:14,
 from /usr/local/include/CLucene.h:18,
 from 
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/../index/tstring.h:28,
 from 
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/tstringtest.cpp:16:
/usr/local/include/CLucene/search/Filter.h:40: warning: unused parameter 
'bs'

In file included from /usr/local/include/CLucene/search/BooleanQuery.h:14,
 from 
/usr/local/include/CLucene/search/MultiTermQuery.h:20,

 from /usr/local/include/CLucene/search/WildcardQuery.h:15,
 from /usr/local/include/CLucene.h:21,
 from 
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/../index/tstring.h:28,
 from 
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/tstringtest.cpp:16:
/usr/local/include/CLucene/search/ConjunctionScorer.h:42: warning: 
unused parameter 'doc'
/usr/local/include/CLucene/search/ConjunctionScorer.h:42: warning: 
unused parameter 'ret'
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/tstringtest.cpp: In 
member function 'void TStringTest::testConversion()':
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/tstringtest.cpp:72: 
warning: format '%ls' expects type 'wchar_t*', but argument 2 has type 
'const char*'
/usr/ports/textproc/soprano/work/soprano-2.1.1/test/tstringtest.cpp:74: 
error: cannot convert 'const char*' to 'const wchar_t*' for argument '1' 
to 'void printWChars(const wchar_t*, int)'

*** Error code 1

Stop in /usr/ports/textproc/soprano/work/soprano-2.1.1.
*** Error code 1

Stop in /usr/ports/textproc/soprano/work/soprano-2.1.1.
*** Error code 1

Stop in /usr/ports/textproc/soprano/work/soprano-2.1.1.
*** Error code 1

Stop in /usr/ports/textproc/soprano.
** Command failed [exit code 1]: /usr/bin/script -qa 
/tmp/portinstall.58784.2 env make BATCH=yes WITH_OPENSSL_PORT=yes 
WITH_OPENSSL=yes WITHOUT_GNOME=esound 

Can't build kdelibs4 due to dependencies failing

[Naram Qashat]

locator > > >&, uint32_t, uint32_t)':
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/cluceneindexreader.cpp:799: 
error: no matching function for call to 'lucene::index::Term::Term(const 
wchar_t*, const wchar_t*)'
/usr/local/include/CLucene/index/Term.h:68: note: candidates are: 
lucene::index::Term::Term(const char*, const char*)
/usr/local/include/CLucene/index/Term.h:62: note: 
lucene::index::Term::Term(const char*, const char*, bool)
/usr/local/include/CLucene/index/Term.h:59: note: 
lucene::index::Term::Term()
/usr/local/include/CLucene/index/Term.h:56: note: 
lucene::index::Term::Term(const lucene::index::Term*, const char*)
/usr/local/include/CLucene/index/Term.h:39: note: 
lucene::index::Term::Term(const lucene::index::Term&)
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/cluceneindexreader.cpp:805: 
error: cannot convert 'const wchar_t*' to 'const char*' for argument '2' to 'int 
strncmp(const char*, const char*, size_t)'
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/cluceneindexreader.cpp:809: 
error: no matching function for call to 'std::setstd::char_traits, std::allocator >, 
std::less, 
std::allocator > >, std::allocatorstd::char_traits, std::allocator > > >::insert(const char*)'
/usr/include/c++/4.2/bits/stl_set.h:304: note: candidates are: 
std::pair, _Compare, 
typename _Alloc::rebind<_Key>::other>::const_iterator, bool> std::set<_Key, 
_Compare, _Alloc>::insert(const _Key&) [with _Key = std::basic_stringstd::char_traits, std::allocator >, _Compare = 
std::less, 
std::allocator > >, _Alloc = std::allocatorstd::char_traits, std::allocator > >]
/usr/include/c++/4.2/bits/stl_set.h:331: note: typename 
std::_Rb_tree<_Key, _Key, std::_Identity<_Key>, _Compare, typename 
_Alloc::rebind<_Key>::other>::const_iterator std::set<_Key, _Compare, 
_Alloc>::insert(typename std::_Rb_tree<_Key, _Key, std::_Identity<_Key>, 
_Compare, typename _Alloc::rebind<_Key>::other>::const_iterator, const _Key&) 
[with _Key = std::basic_string, 
std::allocator >, _Compare = std::lessstd::char_traits, std::allocator > >, _Alloc = 
std::allocator, 
std::allocator > >]
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/cluceneindexreader.cpp: 
In member function 'virtual void CLuceneIndexReader::getChildren(const 
std::string&, std::map, 
std::allocator >, int, std::lessstd::char_traits, std::allocator > >, std::allocatorstd::basic_string, std::allocator >, int> > >&)':
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/cluceneindexreader.cpp:852: 
error: no matching function for call to 'wchartoutf8(const char*&)'
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/tcharutils.h:28: 
note: candidates are: std::string wchartoutf8(const wchar_t*)
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/tcharutils.h:30: 
note: std::string wchartoutf8(const std::wstring&)
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/cluceneindexreader.cpp:853: 
error: no matching function for call to 'lucene::document::Document::get(const 
wchar_t*)'
/usr/local/include/CLucene/document/Document.h:85: note: candidates are: const 
char* lucene::document::Document::get(const char*) const
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/cluceneindexreader.cpp:855: 
error: no matching function for call to 'wchartoutf8(const char*&)'
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/tcharutils.h:28: 
note: candidates are: std::string wchartoutf8(const wchar_t*)
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/tcharutils.h:30: 
note: std::string wchartoutf8(const std::wstring&)
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/cluceneindexreader.cpp: 
In member function 'std::vectorstd::allocator > 
CLuceneIndexReader::Private::strigiSpecial(const std::string&)':
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/cluceneindexreader.cpp:883: 
error: no matching function for call to 'wchartoutf8(const char* const&)'
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/tcharutils.h:28: 
note: candidates are: std::string wchartoutf8(const wchar_t*)
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/tcharutils.h:30: 
note: std::string wchartoutf8(const std::wstring&)
/usr/ports/deskutils/strigi/work/strigi-0.5.11/src/luceneindexer/cluceneindexreader.cpp:896: 
error: cannot convert 'char*' to 'const wchar_t*' for argument '1' to 'size_t 
wcslen(const wchar_t*)'

*** Error code 1

Stop in /usr/ports/deskutils/strigi/work/strigi-0.5.11.
*** Error code 1

Stop in /usr/ports/deskutils/strigi/work/strigi-0.5.11.
*** Error code 1

Stop in /usr/ports/deskutils/strigi/work/strigi-0.5.11.
*** Error code 1

Stop in /usr/ports/deskutils/strigi.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall.58784.3 
env make BATCH=yes WITH_OPENSSL_PORT=yes WITH_OPENSSL=yes WITHOUT_GNOME=esound 
WITHOUT_CUPS=yes WITH_BDB_VER=46 WITH_MYSQL_VER=50 WITH_OPTIMIZED_CFLAGS=yes

** Fix the problem and try again.

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

Odd issue with 'make extract' in a directory outside /usr/ports

[Naram Qashat]

I have a folder outside /usr/ports that is not owned by root that I store ports 
I am making edits on, and whenever I use 'make extract' on any port within that 
folder while I am root, none of the permissions from the tarball it extracted 
from are kept.  For example, a configure script that is set to mode 0755 will be 
extracted as mode 0644, removing the execute flag.  I don't recall when this 
started happening, as it used to work.  I saw nothing in the flags used to 
extract that could be changed.  Manually extracting by running the commands 
myself fails as well.  When I ran it manually, I tried to add -p to tar's flags, 
but that still resulted in the execute flag being removed.  I'm not sure what's 
going on with this, but I do know it works fine within /usr/ports.  Any help on 
the matter is appreciated.


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

Question regrading recent KDE4 ports

[Naram Qashat]

I was wondering if the ports that were committed were the final versions of the 
KDE4 ports.  I was going to install it, and then I started to look through the 
Makefiles and noticed a lot of the KDE4 ports are still referencing KDE3.  I'm 
not sure how much of a problem this will make when it comes to installing KDE4, 
but I want to know if that would cause problems before I make an attempt to 
install it.


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

Porttools and running 'port test'

[Naram Qashat]

I'm not sure if it's porttools at fault here or my own system (or even where I 
have my files), but it seems like every other time I run a 'port test' on a 
port, the permissions on the files being extracted are coming out wrong.  For 
instance, configure scripts are lacking their +x, even though they have it in 
the tarball they are being extracted from.  I don't have this problem with real 
ports in the ports tree, just when I run 'port test' from my separate 
repository.  I do wonder if it's because my repository is owned by my user 
(cyberbotx) but I run 'port test' as root.  Any help on the matter would be 
appreciated.


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

Re: firefox3 port missing firefox-config or firefox3-config

[Naram Qashat]

Jeremy Messenger wrote:
On Fri, 18 Jul 2008 12:06:02 -0500, Naram Qashat 
<[EMAIL PROTECTED]> wrote:


I was trying to modify the VLC port to enable the Firefox plugin, but 
when I added firefox3 to the list of USE_GECKO and tried to build the 
port, it complained saying it couldn't find firefox3-config.  I 
checked my system, and there is no firefox3-config, but back when I 
had firefox2 installed, there was a firefox-config on my system.  I 
couldn't find where in bsd.gecko.mk to add firefox3-config to the 
plist or where in firefox3's Makefile it would need to be added.  Any 
advice on the matter would be helpful.


Because Firefox 3 does not install this file and *.pc (pkg-config files) 
anymore. Everytime when I have tried to search for answer and reason why 
they changed it. I end up hit the wall. Perhaps, they asked in the wrong 
place. Also it's hard to find a good keyword to search in google 
(Mozilla is using google search for their website/newsgroups). If you 
can find it, I would love to know about it. Everything what jong357 
(forum user) knows are same what I know in our search, but he has 
pointed that there is answer in mailing list that I can't find.


http://forums-test.mozillazine.org/viewtopic.php?p=3559635

I have told my team about that somehow I think that Mozilla developers 
want us to start to use xulrunner for SDK/build stuff rather than on 
Firefox, Seamonkey and etc. I think that xulrunner 1.9 does install *.pc 
files and probably xulrunner-config too.


I did a little digging on my own, and found two more threads talking about this:

http://forums.gentoo.org/viewtopic-t-626153-highlight-.html
http://www.linuxquestions.org/questions/slackware-14/firefox-3.0-email-links-no-thunderbird-650845/page2.html

Both mention the same thing, that xulrunner should be used to get the correct 
Mozilla configuration files.  I also just tried to build vlc after manually 
editing it's Makefile to have xulrunner at the beginning of the WANT_GECKO line 
and removing the .include to bsd.gecko.mk, and it found xulrunner-config after 
installing xulrunner, so I assume that's how it should be done from now on.  I 
think this means that using anything but xulrunner for WANT_GECKO or USE_GECKO 
won't work as planned anymore.


Naram Qashat


--

While I am here, our firefox3 port still need some improvements such as 
don't use lib/browser_plugins anymore, because firefox3 can't use 
firefox2 plugins or it crashes. I am thinking about maybe use 
www/linux-mplayer-plugin/Makefile.npapi. Then create new directories 
like lib/npapi/symlinks/gecko18 and lib/npapi/symlinks/lib/gecko19. 
Other more improvements like clean up in bsd.gecko.mk and gecko ports.


I am slowing and lacking motivative, because I dislike any Mozilla 
products and my box is slow for build/install test. I am being patient 
to work with these, so I would love someone (that actually like Mozilla 
product and have motivative) to jump in and take over. ;-)


Cheers,
Mezz


Thanks,
Naram Qashat




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

firefox3 port missing firefox-config or firefox3-config

[Naram Qashat]

I was trying to modify the VLC port to enable the Firefox plugin, but when I 
added firefox3 to the list of USE_GECKO and tried to build the port, it 
complained saying it couldn't find firefox3-config.  I checked my system, and 
there is no firefox3-config, but back when I had firefox2 installed, there was a 
firefox-config on my system.  I couldn't find where in bsd.gecko.mk to add 
firefox3-config to the plist or where in firefox3's Makefile it would need to be 
added.  Any advice on the matter would be helpful.


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

Using bsd.gecko.mk in a port

[Naram Qashat]

With the recent commit of Firefox 3 to the ports, bsd.gecko.mk is now in Mk. 
However, there are no ports using it yet.  I made an attempt to convert vlc to 
use it in order to get it to work with Firefox 3, but I get the following error:


"Makefile", line 371: Could not find bsd.gecko.mk

I had changed the line from

.include "${.CURDIR}/../../www/mozilla/bsd.gecko.mk"

to

.include 

Is there something else that needs to be done in order for bsd.gecko.mk to be 
used, or did I do that wrong?


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

Re: CALL FOR TEST: Updates to pixmap, cairo, poppler, and firefox 3.0!

[Naram Qashat]

Rene Ladan wrote:

2008/6/18 Jeremy Messenger <[EMAIL PROTECTED]>:

Hello folks,


[...]

x11/pixman: Update to 0.10.0

[...]

graphics/cairo: Update to 1.6.4

[...]

graphics/poppler: Update to 0.8.3

[...]

www/firefox3: Update to 3.0 final


[...]

I saw this in the daily security check:


Affected package: firefox-3.0_1,1
Type of problem: mozilla -- multiple vulnerabilities.
Reference: 
<http://www.FreeBSD.org/ports/portaudit/e190ca65-3636-11dc-a697-000c6ec775d9.html>


Is this a false positive?  It seems to affect firefox >3.*,1 but the
CVE entries say it is fixed in firefox 2.0.0.5

Rene


I got past that by adding DISABLE_VULNERABILITIES=yes to my build line.  I'm 
sure it probably is a false positive, though.  But at least it wasn't something 
that broke the build entirely.


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

Re: CALL FOR TEST: Updates to pixmap, cairo, poppler, and firefox 3.0!

[Naram Qashat]

Tom Evans wrote:

On Wed, 2008-06-18 at 16:39 -0400, Naram Qashat wrote:
Well, I tried to build Firefox 3 after updating all the other ports, it gets to 
this point and fails:


c++ -o nsBlockFrame.o -c -I../../dist/include/system_wrappers -include 
../../config/gcc_hidden.h -DMOZILLA_INTERNAL_API -D_IMPL_NS_COM -DEXPORT_XPT_API 
-DEXPORT_XPTC_API -D_IMPL_NS_COM_OBSOLETE -D_IMPL_NS_GFX -D_IMPL_NS_WIDGET 
-DIMPL_XREAPI -DIMPL_NS_NET -DIMPL_THEBES  -DOSTYPE=\"FreeBSD7\" 
-DOSARCH=FreeBSD -D_IMPL_NS_LAYOUT -I. -I./../base -I./../forms -I./../tables 
-I./../xul/base/src -I./../../content/xul/content/src -I./../../content/base/src 
-I./../../content/html/content/src -I./../../dom/src/base -D_THREAD_SAFE 
-I/usr/local/include/cairo -I/usr/local/include/freetype2 -I/usr/local/include 
-I/usr/local/include/pixman-1   -D_THREAD_SAFE -I/usr/local/include/cairo 
-I/usr/local/include -I/usr/local/include/freetype2 
-I/usr/local/include/pixman-1-I. -I. -I../../dist/include/xpcom 
-I../../dist/include/string -I../../dist/include/dom 
-I../../dist/include/content -I../../dist/include/thebes 
-I../../dist/include/gfx -I../../dist/include/widget -I../../dist/include/locale 
-I../../dist/include/view -I../../dist/include/necko -I../../dist/include/js 
-I../../dist/include/caps -I../../dist/include/pref 
-I../../dist/include/htmlparser -I../../dist/include/webshell 
-I../../dist/include/plugin -I../../dist/include/docshell 
-I../../dist/include/webbrwsr -I../../dist/include/oji 
-I../../dist/include/unicharutil -I../../dist/include/lwbrk 
-I../../dist/include/imglib2 -I../../dist/include/xpconnect 
-I../../dist/include/java -I../../dist/include/intl -I../../dist/include/thebes 
-I../../dist/include/cairo -I../../dist/include/accessibility 
-I../../dist/include   -I../../dist/include/layout -I/usr/local/include/nspr 
-I/usr/local/include  -I/usr/include  -I../../dist/sdk/include 
-I/usr/local/include   -fPIC  -I/usr/local/include  -I/usr/local/include 
-fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith 
-Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor 
-Wcast-align -Wno-long-long -O -pipe -O2 -fno-strict-aliasing -O2 
-fno-strict-aliasing -fshort-wchar -pipe  -DNDEBUG -DTRIMMED -O2 -D_THREAD_SAFE 
-I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include 
-I/usr/local/include/atk-1.0 -I/usr/local/include/cairo 
-I/usr/local/include/pango-1.0 -I/usr/local/include 
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include 
-I/usr/local/include/freetype2 -I/usr/local/include/pixman-1 
-I/usr/local/include/gtk-unix-print-2.0-I/usr/local/include 
-I/usr/local/include -DMOZILLA_CLIENT -include ../../mozilla-config.h 
nsBlockFrame.cpp

In file included from ../../dist/include/content/nsContentUtils.h:46,
  from ./../../content/base/src/nsGenericElement.h:59,
  from ./../../content/base/src/nsStyledElement.h:50,
  from ./../../content/base/src/nsMappedAttributeElement.h:48,
  from 
./../../content/html/content/src/nsGenericHTMLElement.h:41,
  from nsBlockFrame.cpp:69:
../../dist/include/js/jsnum.h:150: warning: 'js_TraceRuntimeNumberState' 
initialized and declared 'extern'
../../dist/include/js/jsnum.h:150: error: variable or field 
'js_TraceRuntimeNumberState' declared void

../../dist/include/js/jsnum.h:150: error: 'JSTracer' was not declared in this 
scope
../../dist/include/js/jsnum.h:150: error: 'trc' was not declared in this scope
nsBlockFrame.cpp: In member function 'PRBool 
nsBlockFrame::HandleOverflowPlaceholdersOnPulledLine(nsBlockReflowState&, 
nsLineBox*)':

nsBlockFrame.cpp:4268: warning: unused variable 'taken'
nsBlockFrame.cpp: In member function 'void 
nsBlockFrame::SetOverflowOutOfFlows(const nsFrameList&)':

nsBlockFrame.cpp:4620: warning: unused variable 'result'
nsBlockFrame.cpp: In member function 'virtual void 
nsBlockFrame::DeleteNextInFlowChild(nsPresContext*, nsIFrame*)':

nsBlockFrame.cpp:5601: warning: unused variable 'prevInFlow'
gmake[4]: *** [nsBlockFrame.o] Error 1
gmake[4]: Leaving directory 
`/usr/ports/www/firefox3/work/mozilla/layout/generic'
gmake[3]: *** [libs] Error 2
gmake[3]: Leaving directory `/usr/ports/www/firefox3/work/mozilla/layout'
gmake[2]: *** [libs_tier_gecko] Error 2
gmake[2]: Leaving directory `/usr/ports/www/firefox3/work/mozilla'
gmake[1]: *** [tier_gecko] Error 2
gmake[1]: Leaving directory `/usr/ports/www/firefox3/work/mozilla'
gmake: *** [default] Error 2
*** Error code 2

Stop in /usr/ports/www/firefox3.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.39797.0 
env UPGRADE_TOOL=portupgrade UPGRADE_PORT=firefox-2.0.0.14_1,1 
UPGRADE_PORT_VER=2.0.0.14_1,1 make BATCH=yes WITH_OPENSSL_PORT=yes 
WITH_OPENSSL=yes WITHOUT_GNOME=esound WITHOUT_CUPS=yes WITH_BDB_VER=46 
WITH_MYSQL_VE

Re: CALL FOR TEST: Updates to pixmap, cairo, poppler, and firefox 3.0!

[Naram Qashat]

/include 
-I/usr/local/include/atk-1.0 -I/usr/local/include/cairo 
-I/usr/local/include/pango-1.0 -I/usr/local/include 
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include 
-I/usr/local/include/freetype2 -I/usr/local/include/pixman-1 
-I/usr/local/include/gtk-unix-print-2.0-I/usr/local/include 
-I/usr/local/include -DMOZILLA_CLIENT -include ../../mozilla-config.h 
nsBlockFrame.cpp

In file included from ../../dist/include/content/nsContentUtils.h:46,
 from ./../../content/base/src/nsGenericElement.h:59,
 from ./../../content/base/src/nsStyledElement.h:50,
 from ./../../content/base/src/nsMappedAttributeElement.h:48,
 from 
./../../content/html/content/src/nsGenericHTMLElement.h:41,
 from nsBlockFrame.cpp:69:
../../dist/include/js/jsnum.h:150: warning: 'js_TraceRuntimeNumberState' 
initialized and declared 'extern'
../../dist/include/js/jsnum.h:150: error: variable or field 
'js_TraceRuntimeNumberState' declared void

../../dist/include/js/jsnum.h:150: error: 'JSTracer' was not declared in this 
scope
../../dist/include/js/jsnum.h:150: error: 'trc' was not declared in this scope
nsBlockFrame.cpp: In member function 'PRBool 
nsBlockFrame::HandleOverflowPlaceholdersOnPulledLine(nsBlockReflowState&, 
nsLineBox*)':

nsBlockFrame.cpp:4268: warning: unused variable 'taken'
nsBlockFrame.cpp: In member function 'void 
nsBlockFrame::SetOverflowOutOfFlows(const nsFrameList&)':

nsBlockFrame.cpp:4620: warning: unused variable 'result'
nsBlockFrame.cpp: In member function 'virtual void 
nsBlockFrame::DeleteNextInFlowChild(nsPresContext*, nsIFrame*)':

nsBlockFrame.cpp:5601: warning: unused variable 'prevInFlow'
gmake[4]: *** [nsBlockFrame.o] Error 1
gmake[4]: Leaving directory 
`/usr/ports/www/firefox3/work/mozilla/layout/generic'
gmake[3]: *** [libs] Error 2
gmake[3]: Leaving directory `/usr/ports/www/firefox3/work/mozilla/layout'
gmake[2]: *** [libs_tier_gecko] Error 2
gmake[2]: Leaving directory `/usr/ports/www/firefox3/work/mozilla'
gmake[1]: *** [tier_gecko] Error 2
gmake[1]: Leaving directory `/usr/ports/www/firefox3/work/mozilla'
gmake: *** [default] Error 2
*** Error code 2

Stop in /usr/ports/www/firefox3.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.39797.0 
env UPGRADE_TOOL=portupgrade UPGRADE_PORT=firefox-2.0.0.14_1,1 
UPGRADE_PORT_VER=2.0.0.14_1,1 make BATCH=yes WITH_OPENSSL_PORT=yes 
WITH_OPENSSL=yes WITHOUT_GNOME=esound WITHOUT_CUPS=yes WITH_BDB_VER=46 
WITH_MYSQL_VER=50 WITH_OPTIMIZED_CFLAGS=yes WITH_SMB=yes DISABLE_VULNERABILITIES=yes

** Fix the problem and try again.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! www/firefox3 (firefox-2.0.0.14_1,1)   (new compiler error)

Thanks,
Naram Qashat


TODO tasks:
---
- Bring more ports that depend on poppler in ports-stable.
- Need to update the document for bsd.gecko.mk (USE_GECKO).
- Fix plist in firefox-devel, I hope to get it fix by
  tomorrow or so in this week.
- Add firefox3 in some ports' USE_GECKO if these support,
  but it's safe to wait either. (no hurry)
- Test and test.
- Maybe more if there is any
---

How to use MC ports-stable and upgrade?
---
You can grab marcusmerge[1] and run 'marcusmerge -m ports-stable'. If 
you want to update your ports tree, you have to run cvsup, csup, 
portsnap or different method first then marcusmerge second at the 
everytime. If you want to unmerge your ports tree, you can run 
'marcusmerge -U' and be sure to update your ports tree to bring ports 
back. Be sure to read in marcusmerge manpage[2] for more info.


To upgrade your installed ports, you can just simple 'portmaster -a' or 
'portupgrade -a'. While we don't have most ports that depend on poppler 
get bump yet, so be expect to get a bit problem in runtime at the 
moment. But it is easy to fix by rebuild/reinstall port. To downgrade, 
well you have to do it by manual.


As for the MC ports (GNOME development) users, I have moved these ports 
from ports module to ports-stable module. You will need to run 
'marcusmerge -U' first then update ports tree then MC ports-stable then 
at last MC ports.


[1] http://www.marcuscom.com/downloads/marcusmerge
[2] http://www.marcuscom.com/marcusmerge.8.html
---

With all of these changes, I want this to be tested in the pointyhat-exp 
first before merges into FreeBSD ports tree. The more help we get will 
get faster pointyhat-exp test and merge into FreeBSD ports tree. ;-)


Cheers,
Mezz

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

Re: vlc 0.8.6h failed build on FreeBSD 7.0

[Naram Qashat]

Rafaël Carré wrote:

On Mon, Jun 16, 2008, Naram Qashat wrote:
I was trying to build vlc 0.8.6h on my FreeBSD 7.0 system, trying to upgrade 
from 0.8.6f.  It gets through most of it but stops around here:


somehow I failed to reproduce that bug on my setup

by pure curiosity do you have restrictive CFLAGS in make.conf ?


My CFLAGS are set to -O -pipe


Making all in galaktos
gmake[5]: Entering directory 
`/usr/ports/multimedia/vlc/work/vlc-0.8.6h/modules/visualization/galaktos'


..


PCM.c:82: error: expected ')' before 'PCMdata'


this file fails to #include 

I removed the previous patch which used short instead of int16_t because I 
failed to understand what was its purpose.



I will open a PR with a patch shortly.

In the meantime you can:

cd /usr/ports/multimedia/vlc
make patch
vi work/vlc-0.8.6h/modules/visualization/galaktos/PCM.c
:32
i#include 
:wq
make all deinstall reinstall clean


Thanks for the report



That did indeed fix the build process, thanks for the quick fix.

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

vlc 0.8.6h failed build on FreeBSD 7.0

[Naram Qashat]

/usr/ports/multimedia/vlc/work/fake//usr/local/include 
-I/usr/ports/multimedia/vlc/work/vlc-0.8.6h/include -I/usr/local/include/speex 
-I/usr/local/include -I/usr/local/ffmpeg  -DHAVE_POSTPROC_POSTPROCESS_H 
-I/usr/local/include -DSYS_FREEBSD7_0 -I../../../include 
`top_builddir="../../.." ../../../vlc-config --cflags plugin galaktos` 
-Wsign-compare -Wall -O -pipe  -O2 -ffast-math -fomit-frame-pointer 
-fno-strict-aliasing -pthread -pipe -MT libgalaktos_plugin_a-init_cond.o -MD -MP 
-MF ".deps/libgalaktos_plugin_a-init_cond.Tpo" -c -o 
libgalaktos_plugin_a-init_cond.o `test -f 'init_cond.c' || echo './'`init_cond.c; \
then mv -f ".deps/libgalaktos_plugin_a-init_cond.Tpo" 
".deps/libgalaktos_plugin_a-init_cond.Po"; else rm -f 
".deps/libgalaktos_plugin_a-init_cond.Tpo"; exit 1; fi
if cc -DHAVE_CONFIG_H -I. -I. -I../../.. 
-I/usr/ports/multimedia/vlc/work/fake//usr/local/include 
-I/usr/ports/multimedia/vlc/work/vlc-0.8.6h/include -I/usr/local/include/speex 
-I/usr/local/include -I/usr/local/ffmpeg  -DHAVE_POSTPROC_POSTPROCESS_H 
-I/usr/local/include -DSYS_FREEBSD7_0 -I../../../include 
`top_builddir="../../.." ../../../vlc-config --cflags plugin galaktos` 
-Wsign-compare -Wall -O -pipe  -O2 -ffast-math -fomit-frame-pointer 
-fno-strict-aliasing -pthread -pipe -MT libgalaktos_plugin_a-PCM.o -MD -MP -MF 
".deps/libgalaktos_plugin_a-PCM.Tpo" -c -o libgalaktos_plugin_a-PCM.o `test -f 
'PCM.c' || echo './'`PCM.c; \
then mv -f ".deps/libgalaktos_plugin_a-PCM.Tpo" 
".deps/libgalaktos_plugin_a-PCM.Po"; else rm -f 
".deps/libgalaktos_plugin_a-PCM.Tpo"; exit 1; fi

PCM.c:82: error: expected ')' before 'PCMdata'
PCM.c: In function 'getPCM':
PCM.c:143: warning: implicit declaration of function 'rdft'
gmake[6]: *** [libgalaktos_plugin_a-PCM.o] Error 1
gmake[6]: Leaving directory 
`/usr/ports/multimedia/vlc/work/vlc-0.8.6h/modules/visualization/galaktos'

gmake[5]: *** [all-modules] Error 1
gmake[5]: Leaving directory 
`/usr/ports/multimedia/vlc/work/vlc-0.8.6h/modules/visualization/galaktos'

gmake[4]: *** [all-recursive] Error 1
gmake[4]: Leaving directory 
`/usr/ports/multimedia/vlc/work/vlc-0.8.6h/modules/visualization'

gmake[3]: *** [all] Error 2
gmake[3]: Leaving directory 
`/usr/ports/multimedia/vlc/work/vlc-0.8.6h/modules/visualization'

gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/usr/ports/multimedia/vlc/work/vlc-0.8.6h/modules'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/multimedia/vlc/work/vlc-0.8.6h'
gmake: *** [all] Error 2
*** Error code 2

Stop in /usr/ports/multimedia/vlc.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.28789.0 
env UPGRADE_TOOL=portupgrade UPGRADE_PORT=vlc-0.8.6.f_4,2 
UPGRADE_PORT_VER=0.8.6.f_4,2 make BATCH=yes WITH_OPENSSL_PORT=yes 
WITH_OPENSSL=yes WITHOUT_GNOME=esound WITHOUT_CUPS=yes WITH_BDB_VER=46 
WITH_MYSQL_VER=50 WITH_OPTIMIZED_CFLAGS=yes WITH_AALIB=yes WITHOUT_AVAHI=yes 
WITHOUT_DAAP=yes WITH_FAAC=yes WITH_FAAD=yes WITH_FLAC=yes WITHOUT_HTTPD=yes 
WITH_NCURSES=yes WITH_SVG=yes WITH_SKINS=yes WITH_THEORA=yes WITH_TWOLAME=yes 
WITH_WIN32_CODECS=yes WITHOUT_DVBPSI=yes WITH_DVDREAD=yes WITHOUT_ESOUND=yes 
WITH_FRIBIDI=yes WITHOUT_DIRAC=yes WITHOUT_GGI=yes WITH_VLC_MOZILLA_PLUGIN=yes 
WITH_GEKCO=firefox WITHOUT_MPCDEMUX=yes WITH_OPENGL=yes WITH_TRANSCODE=yes 
WITHOUT_SLP=yes WITHOUT_XOSD=yes

** Fix the problem and try again.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! multimedia/vlc (vlc-0.8.6.f_4,2)  (new compiler error)

[13:25:14 kirby /kirby/shared/ports]# uname -a
FreeBSD kirby.cyberbotx.com 7.0-STABLE FreeBSD 7.0-STABLE #1: Wed Jun  4 
19:02:24 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CBXKERN  i386


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

Re: linux-flashplugin9 Restricted?

[Naram Qashat]

Derek Graham wrote:

from freshports.org:

2006-04-08
Affects: users of www/linux-flashplugin*
Author: [EMAIL PROTECTED]
Reason: 
These ports have been removed because the End User License Agreement

explicitly forbids to run the Flash Player on FreeBSD.
For more details, see
http://www.macromedia.com/shockwave/download/license/desktop/.
I found this odd, I remember seeing an email from adobe someone posted that 
said that they do not support freebsd but they do not forbid users to use 
flash if they can get it working.  I personally think this is insane we need 
a good alternative to flash9, more sites are using flash9 and flash7 is 
becoming useless. Is there a alternative in ports that supports flash ver 9?


It's not a perfect solution, but I've been using Wine to run the Windows version 
of Firefox along with the Windows version of the Flash 9 plugin.  I 
unfortunately had no luck getting the Linux Flash 9 plugin to run with a native 
Firefox and nspluginwrapper, it would freeze nspluginwrapper.


Naram Qashat


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


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

Wine 1.0-rc3 failed build

[Naram Qashat]

I just updated my ports tree which included the update of Wine to 1.0-rc3.  I 
attempted to build it and it failed at this point:


gmake[2]: Entering directory 
`/usr/ports/emulators/wine/work/wine-1.0-rc3/dlls/wininet'
cc -c -I. -I. -I../../include -I../../include  -D__WINESRC__ -D_WINX32_ 
-D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing 
-Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith 
-I/usr/local/include -O -pipe   -o cookie.o cookie.c
cc -c -I. -I. -I../../include -I../../include  -D__WINESRC__ -D_WINX32_ 
-D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing 
-Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith 
-I/usr/local/include -O -pipe   -o dialogs.o dialogs.c
cc -c -I. -I. -I../../include -I../../include  -D__WINESRC__ -D_WINX32_ 
-D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing 
-Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith 
-I/usr/local/include -O -pipe   -o ftp.o ftp.c
cc -c -I. -I. -I../../include -I../../include  -D__WINESRC__ -D_WINX32_ 
-D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing 
-Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith 
-I/usr/local/include -O -pipe   -o gopher.o gopher.c
cc -c -I. -I. -I../../include -I../../include  -D__WINESRC__ -D_WINX32_ 
-D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing 
-Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith 
-I/usr/local/include -O -pipe   -o http.o http.c

In file included from /usr/local/include/openssl/ssl.h:183,
 from internet.h:48,
 from http.c:60:
/usr/local/include/openssl/x509.h:207: error: expected ')' before numeric 
constant
In file included from /usr/local/include/openssl/ssl.h:183,
 from internet.h:48,
 from http.c:60:
/usr/local/include/openssl/x509.h:929: error: expected identifier or '(' before 
'LPCSTR'

/usr/local/include/openssl/x509.h:929: error: expected ')' before numeric 
constant
/usr/local/include/openssl/x509.h:929: error: expected declaration specifiers or 
'...' before '(' token

/usr/local/include/openssl/x509.h:929: error: expected ')' before numeric 
constant
In file included from /usr/local/include/openssl/ssl.h:183,
 from internet.h:48,
 from http.c:60:
/usr/local/include/openssl/x509.h:929:1: error: pasting ")" and "_it" does not 
give a valid preprocessing token

gmake[2]: *** [http.o] Error 1
gmake[2]: Leaving directory 
`/usr/ports/emulators/wine/work/wine-1.0-rc3/dlls/wininet'

gmake[1]: *** [wininet] Error 2
gmake[1]: Leaving directory `/usr/ports/emulators/wine/work/wine-1.0-rc3/dlls'
gmake: *** [dlls] Error 2
*** Error code 2

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

portupgrade with -o doesn't apply any make flags

[Naram Qashat]

I've noticed that with the current (non-devel) version of portupgrade, when I 
was doing a replacement with -o specified, none of the make flags from 
pkgtools.conf were being applied like they normally are when I do a normal 
upgrade or an install.  I haven't had a chance to test portupgrade-devel or not, 
but has it been fixed in that?


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

Re: updating wine to 0.9.57,1 fails?

[Naram Qashat]

Rene Ladan wrote:

Hi,

I don't succeed in updating wine from version 0.9.56,1 to 0.9.57,1 on
my box.  fontforge coredumps during the build.

I'm running FreeBSD 7.0-RELEASE i386

I have CPUTYPE=prescott in /etc/make.conf

Various files are available at ftp://rene-ladan.nl/pub/freebsd/wine :
* alias.txt : alias definitions (build-clean)
* fontforge.ldd : output of 'ldd /usr/local/bin/fontforge' (ok?)
* pkg.lst : overview of installed packages
* wine.portmaster : script(1) of 'portmaster wine'
* wine-0.9.57.log : output of 'make' after a failed build

The core file is available (3.6 MB), but probably doesn't contain
much useful information, since it is built without -g

Any ideas?

Regards,
Rene


The latest update (pending commit) for fontforge fixes the issue.  It was a 
problem on the developers end.  It's been fixed in the source, so when you see 
fontforge get updated in the ports tree, wine should be able to rebuild.


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