Re: Any plan to fix ports git main history compatibility with old GitHub master?

[Eric Turgeon]

Thanks! I was able to fix that this morning and I just merged back from
main and everything is working fine.

*Eric Turgeon*


On Tue, Apr 6, 2021 at 2:08 PM Ulrich Spörlein  wrote:

> On Mon, 2021-04-05 at 21:45:57 +, Brooks Davis wrote:
> >On Mon, Apr 05, 2021 at 05:33:08PM -0300, Eric Turgeon wrote:
> >> Today when trying to sync the GhostBSD ports tree with the FreeBSD ports
> >> tree, I found out the main branch history is not compatible with the old
> >> GitHub master.
> >>
> >> Any plan to migrate to main with hold git history as we had with
> >> freebsd-src?
> >
> >The main branch will contain a commit which is identical to the last
> >commit of the old master branch (except for the hash).  If the GhostBSD
> >repo is merged up to that point, you can then merge the matching commit
> >from main and proceed with using main as the source for future merges.
> >
> >If you have outstanding WIPs the process of updating them to the new
> history
> >should be about the same as the one for source:
> >
> https://github.com/freebsd/freebsd-doc/blob/main/documentation/content/en/articles/committers-guide/_index.adoc#562-migrating-from-github-fork
>
> This special commit was only provided for the `src` repo and will not be
> provided for the ports repo. It is fairly trivial to do this yourself
> and there's documentation around this here:
>
> https://github.com/freebsd/git_conv/wiki/Migrating-merge-based-project-from-legacy-git-tree
>
>
> It should roughly go like this:
> 1. add both remotes and fetch from them
> 2. merge into old master as usual (this is
> e010feae47ac7fda1354fb3b12290a5ee42ef590)
> 3. merge into main at the same instant in time, using your own tree:
> git merge -s ours --allow-unrelated-histories
> 3cc0c0d66a065554459bd2f9b4f80cc07426464a
> 4. now merge into the new origin/main from now on and forevermore
>
> hth, please let me know if you need further help!
> Uli
>
___
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"

Any plan to fix ports git main history compatibility with old GitHub master?

[Eric Turgeon]

Today when trying to sync the GhostBSD ports tree with the FreeBSD ports
tree, I found out the main branch history is not compatible with the old
GitHub master.

Any plan to migrate to main with hold git history as we had with
freebsd-src?




*Eric TurgeonFreeBSD ports committer*
www.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"

Logitech media server recurrent plist issues

[Eric Masson]

Hi,

I'm trying to upgrade logitechmediaserver port to version 7.9.3 released
on last August (would fix plugin repo access issues, permit a new port
for DSDPlayer plugin and bring some other improvements)

So far, I've modified Makefile & files/vendorpatch-CPAN_buildme.sh and
generated distinfo & pkg-plist via makesum & makeplist targets
The port builds but on package stage, it fails the same way older
revisions failed.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240397

>From what I've understood, removing entries in pkg-plist could lead to
an incomplete package on a fresh installation, as some files not
installed by port building would miss (directly installed in ports
prefix and not in stage prefix)

What's the canonical way to fix this kind of issues, please ?

Regards

Éric Masson

-- 
 AB> J'ai demandé à Rémi de le faire.
 Pourquoi moi ? Mais qu'avez-vous donc contre moi ? Je ne vous ai rien
 fait à la fin!
 -+-RL in GNU - Tu connais la différence entre Neuneu et un Pitbull ?-+-
___
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: [Bug 227256] audio/logitechmediaserver doesn't build anymore since perl5 defaults to 5.26

[Eric Masson]

Hi,

bugzilla-nore...@freebsd.org writes:

> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227256
>
> Rodrigo Osorio  changed:
>
>What|Removed |Added
> 
>  Status|New |Closed
>  Resolution|--- |FIXED
>
> --- Comment #11 from Rodrigo Osorio  ---
> Committed, thanks

Thanks a lot.

Éric Masson
___
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: [Bug 227256] audio/logitechmediaserver doesn't build anymore since perl5 defaults to 5.26

[Eric Masson]

Rodrigo Osorio  writes:

Hi Rodrigo,

> Take it !

Thanks a lot.

Éric Masson
___
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: [Bug 227256] audio/logitechmediaserver doesn't build anymore since perl5 defaults to 5.26

[Eric Masson]

bugzilla-nore...@freebsd.org writes:

Hi,

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

Could any port committer commit the patch in ticket 227256, please ?

Regards

Éric Masson
___
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: Logitechmediaserver fails to build

[Eric Masson]

Walter Schwarzenfeld  writes:

Hi Walter,

Thanks for your detailed explanations.

> So I think it is better, you make a PR.

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

Regards

Éric Masson

-- 
 > C'est malheureux de constater k'apres kelkes millers d'années d'evolution,
 > les hommes sont encore au stade *primitive* : peur de ce k'on ne connait
 > pas, juger ses sembles a tout prix, coller une etiquette et j'en passe.
 -+- Gl in :  - fufe, c'est du Darwin -+-
___
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"

database/bbdb issue

[Eric Masson]

Hi,

It seems to me that since emacs has been flavoured, database\bbdb builds
fine but can't be used as stated in 3.x series documentation.

Using the following initialization code :
~/.emacs.d/init.el
;; BBDB setup
(require 'bbdb)
(bbdb-initialize 'gnus 'message)
(bbdb-mua-auto-update-init 'gnus 'message)

emacs barfs on startup, as bbdb-mua-auto-update-init symbol is void.

A few google searches later, the issue seems to be known :
https://bugs.archlinux.org/task/48634

The workaround is the following :
~/.emacs.d/init.el 
;; BBDB setup
(require 'bbdb-loaddefs) ;; symbol definition void workaround
(require 'bbdb)
(bbdb-initialize 'gnus 'message)
(bbdb-mua-auto-update-init 'gnus 'message)

Can this issue be fixed ?
If not, could a pkg-message be added to warn about the issue ?

Regards

Éric Masson

-- 
 ED: Ben il me semble que depuis peu tu doit declarer un site que tu
 crée...
 NP: Depuis longtemps, mais il y a un certain laxisme au niveau du suivi.
 + NP in Guide du Macounet Pervers : Y'a du mou dans la corde à noeuds. +
___
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: Logitechmediaserver fails to build

[Eric Masson]

Walter Schwarzenfeld  writes:

Hi,

> work/slimserver-vendor-1463b00/CPAN/buildme.sh misses perl5.26 entry.

I've changed this file by adding perl5.26 entry (see attached diff), LMS
still doesn't build correctly :
(errors on work/slimserver-vendor-1463b00/CPAN/Class-XSAccessor-1.05)
make typescript attached.

Regards

Éric Masson

-- 
 Il y en a qui ne savent pas déballer leur ordinateur de la boîte
 d'emballage. Faudrait aussi prévoir une doc là-dessus (parce que celle
 fournie avec la boîte, il y a plein de mots et pas beaucoup d'images)
 -+- Jaco in Guide du Linuxien pervers - "[OUI] à fcol.deballage" -+-
--- buildme.sh	2018-04-03 09:50:06.635491000 +0200
+++ /home/emss/buildme.sh	2018-04-03 09:46:48.470468000 +0200
@@ -322,6 +322,19 @@
 PERL_ARCH=$BUILD/arch/5.24
 fi
 
+# Path to Perl 5.26
+if [ -x "/usr/bin/perl5.26.1" ]; then
+PERL_526=/usr/bin/perl5.26.1
+fi
+   
+if [ $PERL_526 ]; then
+echo "Building with Perl 5.26 at $PERL_526"
+PERL_BIN=$PERL_526
+# Install dir for 5.26
+PERL_BASE=$BUILD/5.26
+PERL_ARCH=$BUILD/arch/5.26
+fi
+
 # try to use default perl version
 if [ "$PERL_BIN" = "" ]; then
 PERL_BIN=`which perl`
@@ -355,6 +368,9 @@
 "5.24")
 	PERL_524=$PERL_BIN
 ;;
+"5.26")
+	PERL_526=$PERL_BIN
+;;
 *)
 echo "Failed to find supported Perl version for '$PERL_BIN'"
 exit


LMS_make.gz
Description: Binary data
___
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"

Logitechmediaserver fails to build

[Eric Masson]

Hi,

Seems Logitech Media Server doesn't build on 11-STABLE (I had to rebuild
it after perl5 defaults from 5.24 to 5.26).

root@newsrv:/usr/ports/audio/logitechmediaserver # make
===>  License SDL needs confirmation, will ask later
===>   logitechmediaserver-7.9.1.g2017.07.11 depends on file: 
/usr/local/sbin/pkg - found
===> Fetching all distfiles required by logitechmediaserver-7.9.1.g2017.07.11 
for building
===>  Extracting for logitechmediaserver-7.9.1.g2017.07.11
=> SHA256 Checksum OK for 
Logitech-slimserver-7.9.1.g2017.07.11-762b5cb_GH0.tar.gz.
=> SHA256 Checksum OK for Logitech-slimserver-vendor-1463b00_GH0.tar.gz.
===>  Patching for logitechmediaserver-7.9.1.g2017.07.11
===>  Applying extra patch 
/usr/ports/audio/logitechmediaserver/files/vendorpatch-CPAN_buildme.sh
===>  Applying FreeBSD patches for logitechmediaserver-7.9.1.g2017.07.11
===>   logitechmediaserver-7.9.1.g2017.07.11 depends on executable: nasm - found
===>   logitechmediaserver-7.9.1.g2017.07.11 depends on executable: bash - found
===>   logitechmediaserver-7.9.1.g2017.07.11 depends on executable: rsync - 
found
===>   logitechmediaserver-7.9.1.g2017.07.11 depends on executable: gmake - 
found
===>   logitechmediaserver-7.9.1.g2017.07.11 depends on package: 
perl5>=5.26<5.27 - found
===>   logitechmediaserver-7.9.1.g2017.07.11 depends on shared library: 
libgd.so - found (/usr/local/lib/libgd.so)
===>   logitechmediaserver-7.9.1.g2017.07.11 depends on shared library: 
libintl.so - found (/usr/local/lib/libintl.so)
===>  Configuring for logitechmediaserver-7.9.1.g2017.07.11
===>  Building for logitechmediaserver-7.9.1.g2017.07.11
cd 
/storage/work/ports/build/usr/ports/audio/logitechmediaserver/work/slimserver-vendor-1463b00/CPAN
 && ./buildme.sh
RUN_TESTS:1 CLEAN:1 USE_HINTS:1 target all
Building for FreeBSD / amd64-freebsd-thread-multi
Failed to find supported Perl version for '/usr/local/bin/perl'
===>  Staging for logitechmediaserver-7.9.1.g2017.07.11
===>   logitechmediaserver-7.9.1.g2017.07.11 depends on executable: flac - found
===>   logitechmediaserver-7.9.1.g2017.07.11 depends on executable: shorten - 
found
===>   logitechmediaserver-7.9.1.g2017.07.11 depends on executable: sox - found
===>   logitechmediaserver-7.9.1.g2017.07.11 depends on package: 
perl5>=5.26<5.27 - found
===>   Generating temporary packing list
===> Creating groups.
===> Creating users
(cd 
/storage/work/ports/build/usr/ports/audio/logitechmediaserver/work/slimserver-762b5cb
 && /bin/sh -c '(/usr/bin/find -Ed $1 $3 | /usr/bin/cpio -dumpl $2 >/dev/null 
2>&1) &&  /usr/bin/find -Ed $1 $3 \(   -type d -exec /bin/sh -c '\''cd 
'\''$2'\'' && chmod 755 "$@"'\'' . {} +  -o -type f -exec /bin/sh -c '\''cd 
'\''$2'\'' && chmod 0644 "$@"'\'' . {} + \)' COPYTREE_SHARE . 
/storage/work/ports/build/usr/ports/audio/logitechmediaserver/work/stage/usr/local/share/logitechmediaserver)
(cd 
/storage/work/ports/build/usr/ports/audio/logitechmediaserver/work/slimserver-vendor-1463b00/CPAN/build
 &&  /bin/sh -c '(/usr/bin/find -Ed $1 $3 | /usr/bin/cpio -dumpl $2 >/dev/null 
2>&1) &&  /usr/bin/find -Ed $1 $3 \(   -type d -exec /bin/sh -c '\''cd 
'\''$2'\'' && chmod 755 "$@"'\'' . {} +  -o -type f -exec /bin/sh -c '\''cd 
'\''$2'\'' && chmod 0644 "$@"'\'' . {} + \)' COPYTREE_SHARE arch 
/storage/work/ports/build/usr/ports/audio/logitechmediaserver/work/stage/usr/local/share/logitechmediaserver/CPAN)
cd: 
/storage/work/ports/build/usr/ports/audio/logitechmediaserver/work/slimserver-vendor-1463b00/CPAN/build:
 No such file or directory
*** Error code 2

Stop.
make[1]: stopped in /usr/ports/audio/logitechmediaserver
*** Error code 1

Stop.
make: stopped in /usr/ports/audio/logitechmediaserver
root@newsrv:/usr/ports/audio/logitechmediaserver #

Regards

Éric Masson

-- 
 > Mais bon, c'est pas moi qui lancerais l'AAD là-dessus (mais s'il passe
 > je voterai certainement pour si ça peut éviter aux dinosaures de bloquer
 > systèmatiquement toutes les initiatives des linuxiens).
 -+- EF in Guide du linuxien pervers : "Les dinos ont changé de camps !" -+-
___
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: Working on FLAVOR support in portmaster

[Eric Masson]

Stefan Esser  writes:

Hi Stefan

> Is it acceptable, to have portmaster stop supporting the old package system?

I think so.

Thanks for your work on this.

Éric Masson

-- 
 Discuter tranquillement avec Michel Guillou???
 Je n'ai JAMAIS vu quelqu'un de plus *facho* que ce type. C'est
 écoeurant.
 -+- Rocou In GNU - T'as l'adresse des FFL, c'est pour écrire -+-
___
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: poudriere, python ports, and flavors oh my?

[Eric Masson]

Adam Weinberger  writes:

Hi Adam,

> Given that most people don't participate and test patches while they're
> in review, you have to expect that some bugs will only surface when it
> lands in HEAD. This is precisely why we have quarterly branches, and why
> we recommend that most people stay on quarterly.

For starters, the following is not intended to troll anyone.

FLAVORS mechanism seems to be a quite nice tool to improve ports, but
the landing in ports/head raises few questions.

Is ports/head becoming the alter ego of src/head (possible breakages or
disruptive new features from time to time) ?

If yes, this should be written down in the handbook (chapter on ports
still states ports/head for svn retrieval) and quarterly ports branches
should be publicized.

I've just switched to 2017Q4 on my main 11-STABLE box by digging in
various ports docs after I've read this very post I'm answering to.

I thus got rid of ports/head FLAVORS related issues (portmaster is my
tool of choice as poudriere seems a bit overkill for my needs).

Thanks to all involved.

Éric Masson

-- 
 Cela m'a même déjà valu quelques discussions animés avec mes paires
 -+- FC in  : Tête à tête ou tête à queue ? -+-
___
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: manpath change for ports ?

[Eric van Gyzen]

On 03/06/2017 17:56, Baptiste Daroussin wrote:

Hi all,

I would like to propose a change in the localbase hier for ports


[...]


Which will also remove tons of hacks from the ports tree.

What do you think?


This sounds good to me.

I seem to recall that most(?) Linux distros used /usr/man many years 
ago, but they switched to /usr/share/man, I think in the early 2000s. 
If that's correct, then I consider our /usr/local/man path a historical 
curiosity that should finally be changed to /usr/local/share/man.


Eric
___
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: opensmtpd 5.4.4 in freebsd 9 jail

[Eric Faurot]

On Tue, Feb 24, 2015 at 11:42:32AM +0100, Cedric Berger wrote:
 Hello,
 
 Since I upgraded my freebsd 9 jail with the latest opensmtpd 5.4.4_1,1 port,
 smtp-out refuse to send any email to the outside world.
 
 I've seen a similar issue reported by Meutel here, but with no apparent
 solution:
 
 http://blog.gmane.org/gmane.mail.opensmtpd.general/day=20150211, 2nd post.
 
 Based on ktrace analysis, I believe the faulty code starts at line 210 of
 getaddrinfo_async.c in libasr:
 
 https://github.com/OpenSMTPD/libasr/blob/libasr-1.0.1/src/getaddrinfo_async.c
 
 This code returns EAI_NONAME if there is no non-loopback interface
 configured
 in the jail. This is my case, as a jail by default has only loopback
 interfaces configured (this doesn't prevent connecting to the outside
 world).
 
 If my analysis is correct, I believe that if no non-loopback interface is
 found, the code should also (in a second step) consider loopback interfaces
 when selecting IPv4 versus IPv6, instead of just bailing out.
 
 That would make the code more robust.

Hello.

I'll think how asr can be improved in the way you suggest.  In the
meantime, the regression you see is actually due to the following
change in smtpd.  Try without it.  Note that it will also retreive
inet6 addresses, so you might want to add limit mta inet4 in
smtpd.conf if inet6 is not routable on your system.

Eric.

diff --git a/smtpd/dns.c b/smtpd/dns.c
index fc8bce6..ea5d430 100644
--- a/smtpd/dns.c
+++ b/smtpd/dns.c
@@ -448,6 +448,7 @@ dns_lookup_host(struct dns_session *s, const char *host, 
int preference)
s-refcount++;
 
memset(hints, 0, sizeof(hints));
+   hints.ai_flags = AI_ADDRCONFIG;
hints.ai_family = PF_UNSPEC;
hints.ai_socktype = SOCK_STREAM;
as = getaddrinfo_async(host, NULL, hints, NULL);
___
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

xfe-1.37_1 does not start...

[Eric Douzet]

Hello,


xfe-1.37_1 does not start after update of the fox16-1.6.50 library.

portupgrade -fr x11-toolkits/fox16 has no effect.

Best regards,


-- 
Amicalement et librement,

Éric Douzet


Consultant Informatique

Administrateur Réseaux, Système et Base de Données
Consultant Sage (Logiciels de Gestion) - Comptable Diplômé
Sécurité Réseaux - Hébergeur FreeBSD - Audit de Site Web

Systèmes : FreeBSD, Mac OSX, Unix et Windows

Site Web professionnel : www.c-extra.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Asterisk ports

[Eric Teeter]

Are there going to be ports for the different languages sounds for Asterisk 
(i.e. g772 or wav for en)? 

-- 

Eric Teeter 
349 N Rutland Ave Apt 3 
Brooklyn, WI 53521 
(608) 455-4172 




-
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4794 / Virus Database: 4253/8872 - Release Date: 01/05/15
___
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

Request : jkmeter-0.6.1 (a vu-meter for Jack)

[Eric F]

Hi all,

I'm a newbie at FreeBSD, and FreeBSD porting, so I would be cool if someone
could port jkmeter.

Thanks in advance,

Eric
___
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 ports that you maintain require staging updates

[Eric Masson]

portmgr-feedb...@freebsd.org writes:

Hello,

 Ports that you maintain that are currently unstaged (NO_STAGE=yes):
   print/lpr-wrapper
   print/psdim

I don't use lpr-wrapper anymore, it seems to me that lpr-wrapper  psdim
have been superseded by P. Selinger's upprint :
http://www.mathstat.dal.ca/~selinger/upprint/

Thanks for resetting maintainer, please.

Regards

Éric Masson
___
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 Port: banshee-2.6.0_1,1 failed to build.

[Eric Turgeon]

Making all in audio-profiles
Generating and caching the translation database
Merging translations into aac.xml.
CREATED aac.xml
Found cached translation database
Merging translations into aac-novell.xml.
CREATED aac-novell.xml
Found cached translation database
Merging translations into base.xml.
CREATED base.xml
Found cached translation database
Merging translations into flac.xml.
CREATED flac.xml
Found cached translation database
Merging translations into mp3-lame.xml.
CREATED mp3-lame.xml
Found cached translation database
Merging translations into mp3-xing.xml.
CREATED mp3-xing.xml
Found cached translation database
Merging translations into vorbis.xml.
CREATED vorbis.xml
Found cached translation database
Merging translations into wavpack.xml.
CREATED wavpack.xml
Found cached translation database
Merging translations into wav.xml.
CREATED wav.xml
Found cached translation database
Merging translations into wma.xml.
CREATED wma.xml
Making all in desktop-files
Found cached translation database
Merging translations into banshee-audiocd.desktop.
Found cached translation database
Merging translations into banshee-media-player.desktop.
Found cached translation database
Merging translations into banshee.desktop.
Making all in icon-theme-hicolor
  GEN   addin-xml-strings.cs
Making all in help
Making all in libbanshee
  CCbanshee-bpmdetector.o
  CCbanshee-gst.o
  CCbanshee-player.o
banshee-player.c: In function 'bp_destroy':
banshee-player.c:104: warning: 'g_mutex_free' is deprecated (declared at
/usr/local/include/glib-2.0/glib/deprecated/gthread.h:274)
banshee-player.c:108: warning: 'g_mutex_free' is deprecated (declared at
/usr/local/include/glib-2.0/glib/deprecated/gthread.h:274)
banshee-player.c: In function 'bp_new':
banshee-player.c:135: warning: 'g_mutex_new' is deprecated (declared at
/usr/local/include/glib-2.0/glib/deprecated/gthread.h:272)
banshee-player.c:136: warning: 'g_mutex_new' is deprecated (declared at
/usr/local/include/glib-2.0/glib/deprecated/gthread.h:272)
  CCbanshee-player-cdda.o
  CCbanshee-player-dvd.o
  CCbanshee-player-equalizer.o
  CCbanshee-player-missing-elements.o
  CCbanshee-player-pipeline.o
  CCbanshee-player-replaygain.o
  CCbanshee-player-video.o
  CCbanshee-player-vis.o
  CCbanshee-ripper.o
  CCbanshee-tagger.o
  CCbanshee-transcoder.o
  LINK  libbanshee.la
Making all in src
Making all in Hyena
Making all in build
Making all in m4
Making all in pkg-config
  MCS   gconf-schema-extractor.exe
  MCS   dll-map-verifier.exe
  MCS   addin-xml-string-extractor.exe
  MCS   gobject-intptr-ctor-verifier.exe
Making all in Hyena
  MCS   ../../../bin/Hyena.dll
Making all in Hyena.Data.Sqlite
  MCS   ../../../bin/Hyena.Data.Sqlite.dll
Making all in Hyena.Gui
  MCS   ../../../bin/Hyena.Gui.dll
error CS1705: Assembly `gdk-sharp, Version=2.12.0.0, Culture=neutral,
PublicKeyToken=35e10195dab3c99f' references `Mono.Cairo, Version=4.0.0.0,
Culture=neutral, PublicKeyToken=0738eb9f132ed756' which has a higher
version number than imported assembly `Mono.Cairo, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=0738eb9f132ed756'
./Hyena.Data.Gui/ListView/ListView_Rendering.cs(53,53): error CS0012: The
type `Cairo.Context' is defined in an assembly that is not referenced.
Consider adding a reference to assembly `Mono.Cairo, Version=4.0.0.0,
Culture=neutral, PublicKeyToken=0738eb9f132ed756'
Compilation failed: 2 error(s), 0 warnings
gmake[4]: *** [../../../bin/Hyena.Gui.dll] Error 1
gmake[3]: *** [all-recursive] Error 1
gmake[2]: *** [all-recursive] Error 1
gmake[1]: *** [all-recursive] Error 1
gmake: *** [all] Error 2
*** [do-build] Error code 1

Stop in /usr/ports/multimedia/banshee.
*** [install] Error code 1

Stop in /usr/ports/multimedia/banshee.
root@ericbsd:/usr/ports/multimedia/banshee #


-- 
*Eric Turgeon
**GhostBSD project*
Office location:
1-11 connaught
Moncton NB Canada
www.ghostbsd.org http://www.ghostbsd.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: GNOME 3

[Eric Turgeon]

I think gnome2 will be replace by Mate which is far more better and less
buggy. I am running mate 1.6 right now on FreeBSD it work well and fast.
https://github.com/jlmess77/mate-ports#mate-ports-for-freebsd


On Sun, Jun 9, 2013 at 10:20 PM, Stephen Montgomery-Smith 
step...@missouri.edu wrote:

 On 06/09/2013 06:33 PM, Kenta Suzumoto wrote:
  Is there any ETA on getting GNOME 3 into FreeBSD ports?

 Also, if gnome3 goes into ports, is there any chance we could keep a
 legacy gnome2 going for a while?  I discovered that I really hate gnome3
 based upon my usage with ubuntu, and I have switched instead to mate.
 It would be good to keep gnome2 going on FreeBSD at least until FreeBSD
 has a well working mate.

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




-- 
*Eric Turgeon
**GhostBSD project*
Office location:
1-11 connaught
Moncton NB Canada
www.ghostbsd.org http://www.ghostbsd.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: GNOME 3

[Eric Turgeon]

Yes I am The GhostBSD project Founder my project depend on FreeBSD project
and the Gnome team I have to try to help as mush I can with the time I
don't have lol.

Yes it is possible to ports it but it take time and man power.



On Sun, Jun 9, 2013 at 10:31 PM, Kenta Suzumoto ken...@hush.com wrote:

 Back on the list..

 On 06/09/2013 at 9:20 PM, Eric Turgeon ericturgeon@gmail.com
 wrote:
 
 I can't say anything sure on that, but for now more it go more it
 look like lost cause. The first time I have install it all was working
 fine, but now every time I compile it failed or if get it compile it buggy
 
 

 I'm not familiar with Ghost BSD but are you in cooperation with the
 FreeBSD GNOME/Ports team(s)? Hopefully there aren't multiple teams trying
 to reinvent each other's work. If a group like OpenBSD with such limited
 manpower can port it, surely the FreeBSD guys can do so, too.




-- 
*Eric Turgeon
**GhostBSD project*
Office location:
1-11 connaught
Moncton NB Canada
www.ghostbsd.org http://www.ghostbsd.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

Last database update: 2012-11-11 10:45:48 UTC

[Eric Douzet]

Hello,


The last database update Ports is : 2012-11-11 10:45:48 UTC

The database should be updated it, thank you !

Best regards,


Éric Douzet


Consultant Informatique
Site Web professionnel : www.c-extra.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: emulators/virtualbox-ose-kmod refuses to build

[Eric Masson]

Aryeh Friedman aryeh.fried...@gmail.com writes:

Hi,

 === All  virtualbox-ose-kmod-4.1.22 (5/44)

Check /usr/ports/UPDATING on 20130103 entries...

-- 
 Je vous ferez remarquer chers câblés et très très chères câblées qu'un
 simple message INNOCENT (j'insiste) a engendré près de 10 réponses !!!
 -+- PC in http://www.le-gnu.net : Tous coupables, tous. -+-
___
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: CFT: new BSD-licensed sort available

[Eric van Gyzen]

On 03/16/2012 08:25 PM, Doug Barton wrote:

On 03/14/2012 15:14, Jonathan Anderson wrote:

In fact, the runtime behaviour of the Debian alternatives system is simpler 
than that:
http://segfault.in/2010/04/using-the-debian-alternatives-system/

[...]

This sounds like a good solution to more than one problem. Does anyone
know why they indirect through 2 sets of symlinks? That article doesn't
touch on the why? only the what.


Do you mean, why do they do
/usr/bin/vim - /etc/alternatives/vim - /usr/bin/vim.gtk
instead of
/usr/bin/vim - /usr/bin/vim.gtk
?

Someone's choice of a vi-like editor would be considered configuration, 
so it belongs in /etc.


I agree, it does sound like a good solution.  As simple as possible, but 
no less.  ;)


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

CUDA porting effort?

[Eric McCorkle]

Given that NVidia is releasing the CUDA platform source on a limited
basis, is anyone actively working to port it to FreeBSD?  The reason I
ask is that to get access to the source, you have to submit a request
explaining what you intend to use it for.  It might be a good idea to
get ahold of the source on behalf of FreeBSD, so that interested people
could work on porting it.  I could devote a small amount of time to such
an effort; I'm wondering if there's interest from anyone else.



signature.asc
Description: OpenPGP digital signature

Re: FreeBSD Port: samba36-3.6.1

[Eric Masson]

Jean-Yves Avenard jean-yves.aven...@hydrix.com writes:

Hello,

 samba36 from ports fail to compile properly on my system (FreeBSD 8.2)

No problem here (compilation tested 5 mn ago)
8.2-RELEASE-p4

# New ports collection makefile for:samba36
# Date created: 1 May 2011
# Whom: ti...@freebsd.org
#
# $FreeBSD: ports/net/samba36/Makefile,v 1.3 2011/10/21 02:12:22 timur Exp $

WITH_LDAP=true
WITHOUT_ADS=true
WITHOUT_CUPS=true
WITH_WINBIND=true
WITHOUT_SWAT=true
WITH_ACL_SUPPORT=true
WITHOUT_AIO_SUPPORT=true
WITHOUT_FAM_SUPPORT=true
WITH_SYSLOG=true
WITHOUT_QUOTAS=true
WITH_UTMP=true
WITHOUT_PAM_SMBPASS=true
WITHOUT_DNSUPDATE=true
WITHOUT_AVAHI=true
WITHOUT_EXP_MODULES=true
WITH_POPT=true
WITH_IPV6=true
WITHOUT_MAX_DEBUG=true
WITHOUT_SMBTORTURE=true

Éric Masson

-- 
 Crétin anonyme vous etes un abruti !
 Je ne pretends pas le contraire, la preuve je vous parle.
 -+- SM in http://www.le-gnu.net : Léon est un con -+-
___
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: ImageMagick fails to build when upgrading.

[Eric McCorkle]

On 10/13/11 10:46, Andriy Gapon wrote:
 on 12/10/2011 14:55 Zhihao Yuan said the following:
 I checked out the latest version in ports, but this test still fails for
 gcc46. I'll try clang latter.
 I am also running into the same problem with gcc45 and optimization level = 
 2.
 With base gcc or optimization level = 1 all tests pass OK.
 I don't know how to explain this, I won't even try, because I think that this 
 is
 irrelevant.

 I've tracked down origins of this issue to the following:
 https://bugzilla.novell.com/show_bug.cgi?id=673303
 http://www.imagemagick.org/discourse-server/viewtopic.php?f=3t=19436
 Apparently they fixed something strerror_r-ish for glib environment, but 
 broken it
 for posix environment.


I've seen the same behavior with a clang build.



signature.asc
Description: OpenPGP digital signature

Re: ImageMagick fails to build when upgrading.

[Eric McCorkle]

On 10/14/11 17:25, Eric McCorkle wrote:
 I've seen the same behavior with a clang build. 

Actually, no.  I looked into it more, and what I found is suspicious.

I had the tests failing in Magick++/attributes.sh.  What's suspicious is
it would claim to have a random, and often nonsensible number of
failures (-21563, or something).  I opened up attributes.cpp, expecting
to find an uninitialized variable, however, there is an int failures =
0 at the top of the main function.  After a while, I moved the
declaration outside of the main function, and the test worked.  This
tells me it's getting corrupted somehow, perhaps by a buffer overflow of
some kind.

Has anyone else seen this?



signature.asc
Description: OpenPGP digital signature

Re: Re-starting daemons across upgrades? (was: Thank you (for making the ports less boring).)

[Eric]

 We do not currently have a standard procedure for that, nor do we record
 the necessary state -- perhaps we should just discuss, vote, and add a
 paragraph to the porter's handbook.
 
 We also need to bring the authors (or volunteers) for the de-facto
 standard upgrade tools into the loop.
 
 My thoughts:
 
 - give the user a choice to configure whether to restart services
 
 - optional: give the users a chance to configure this per-service
 
 - discuss whether we want/need to support this (a) in the framework that
 we currently use, (b) only in pkgng, (c) in portmaster and portupgrade
 where necessary.

Just for ref regarding (c) on the portupgrade wiki page[1] it mentions using
AFTERINSTALL in pkgtools.conf for doing automatic stop/start/restart.

[1] http://wiki.freebsd.org/portupgrade


___
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: SQLite 3 PHP extensions issues after upgrading to PHP5 5.3.6_1

[Eric]

 From: Attos attos.ja...@gmail.com
 Hello,
 Just upgraded to php5-5.3.6_1 and the SQLITE 3 extensions
 (php5-pdo_sqlite-5.3.6_1 and php5-sqlite3-5.3.6_1) are causing PHP to core
 dump.
 I commented them from /usr/local/etc/php/extensions.ini and the segmentation
 faults disappear.

I've always fount that re-ordering the entries in /usr/local/etc/php/
extensions.ini through trial and error tends to make the problem go away and
allows one to use the extension without the faults.

Jim Pingle posted a script ages ago on his blog[1] to do some rough and
ready re-ordering, if you fancy giving that a try.

Regards

Eric

[1] http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround


___
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: -Qunused-parameter and clang (was Re: GHC Port on 9-CURRENT)

[Eric McCorkle]

On 6/28/11 4:06 PM, Niclas Zeising wrote:

On 2011-06-28 21:19, Pan Tsu wrote:

Niclas Zeisingzeis...@daemonic.se  writes:


Sorry for hijacking this thread, and cross posting.

On 2011-06-26 03:07, Gabor PALI wrote:




With Clang, an error occurs in one of the configure scripts, because
Clang warns about unused command-line arguments, and the configure
script assumes that to be a compiler error.  You can deal with this by
adding -Qunused-parameter to CFLAGS.


Thanks for investigating this.



This should probably be made the default, at least for ports when clang
is compiled, since the output generated when not using
-Qunused-parameter confuses configure scripts, and stops at least
FireFox 5 from compiling, that I know of.


Do you use ccache? Try without.

For example, the combo confuses libtool



It has nothing to do with cccache. The issue is that clang by default
warns when passed flags (-std= -f -W etc.) that's not used during the
compilation/linking. This can be silenced with -Qunused-arguments, and
if not, it confuses configure scripts that believe this is an error in
the code it uses to test for features.

Regards!


Example: In the GHC port, the configure script tries to figure out 
whether the ISA supports PC-relative indexing.  It does this by 
generating a simple program, which contains some asm containing 
PC-relative indexing, compiling it, and seeing if the compiler generates 
a warning.  If clang warns about unused arguments, then the configure 
script assumes (falsely) that the ISA does not support PC-relative 
indexing, and generates bad assembly code, which causes trouble downstream.

___
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

GHC Port on 9-CURRENT

[Eric McCorkle]

The GHC (Glasgow Haskell Compiler) was marked broken by pointyhat 
sometime back in May, following its update to GHC 7.0.3_1.  I'm not sure 
if anyone has looked at this, but it doesn't appear anyone has.  Sorry 
if any of this is repeated.


I tried building the port yesterday, with both GCC and Clang.  The GCC 
build succeeds, and the compiler seems to work just fine (it has no 
trouble compiling and installing the haskell-platform port, as well as 
many of my own haskell programs).


With Clang, an error occurs in one of the configure scripts, because 
Clang warns about unused command-line arguments, and the configure 
script assumes that to be a compiler error.  You can deal with this by 
adding -Qunused-parameter to CFLAGS.  With this, it builds the bootstrap 
and stage 1 compilers.  However, the stage 1 compiler's parser appears 
to be broken, as it reports erroneous parse errors on the GHC compiler's 
source code (and probably for any haskell program, but it never gets a 
chance to).  I'm not sure why this happens, but I will investigate more 
closely once I deal with some more important issues I'm investigating.


In any case, the port builds fine with GCC.  Perhaps it would be prudent 
to set CC=gcc and CXX=g++ in the makefile for the time being and mark 
the port as working again?


--
Eric McCorkle
Computer Science Ph.D Student,
University of Massachusetts
Research Intern, IBM Research
___
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: Clean up old PRs

[Eric]

 From: Jerry je...@seibercom.net
 Date: Mon, 16 May 2011 08:02:07 -0400
 
 There are several PRs that are years (literally) old. For example:
 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/87397
 
 o 2005/10/13 ports/87397 edwin [patch] incorrect use of PAPERSIZE make
 variable in some ports
 
 Maybe it is time that some of these extremely old PRs be put to rest.
 Perhaps a new classification should be added. Presently there are
 several possible classifications:
 
 o - open
 A problem report has been submitted, no sanity checking performed.
 a - analyzed
 The problem is understood and a solution is being sought.
 f - feedback
 Further work requires additional information from the originator or
 the community - possibly confirmation of the effectiveness of a
 proposed solution.
 p - patched
 A patch has been committed, but some issues (MFC and / or
 confirmation from originator) are still open.
 r - repocopy
 The resolution of the problem report is dependent on a repocopy
 operation within the CVS repository which is awaiting completion.
 s - suspended
 The problem is not being worked on, due to lack of information or
 resources. This is a prime candidate for somebody who is looking
 for a project to do. If the problem cannot be solved at all, it
 will be closed, rather than suspended.
 c - closed
 A problem report is closed when any changes have been integrated,
 documented, and tested -- or when fixing the problem is abandoned.
 
 I am proposing a new one:
 
 x - expired
 This report is over 2 years old. If no one has bothered to fix it
 by now, then in all probability no one will.

Personally I quite like this idea, but to play devils advocate one could
just set the ancient PRs to closed, since this can be used for an abandoned
PR (as indicated in the classification descriptions).
However I like the idea of actually acknowledging that they have expired
since it may provide an interesting metric that could be measured.  It may
however be possible to still obtain that metric using a 'c' closed state -
since this is likely to be an automated PR expiry procedure perhaps whatever
batch process is doing the closing might set a suitable (consistent) 'Why'
message with the PR, something like [EXPIRED] This report is over 2 years
old. which perhaps (he says not being too familiar with the underlying
GNATS db) could be filtered for and used in generating reports/stats?

Cheers

Eric


___
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: saving a few ports from death

[Eric]

 From: Anton Shterenlikht me...@bristol.ac.uk
 Date: Wed, 27 Apr 2011 10:14:41 +0100
 To: freebsd-ports@freebsd.org
 Subject: Re: saving a few ports from death
 
 On Tue, Apr 26, 2011 at 03:55:56PM -0700, Charlie Kester wrote:
 
 My search for popularity metrics is intended to point me, as a
 maintainer, to ports I might want to adopt now, rather than wait for
 someone to complain about them.  Everything *I* use is already
 maintained, so I've moved on to looking for things other people might
 need.  But I don't want to waste my time on something that nobody uses.
 :)
 
 Interesting..
 
 I used this sh(1) script to find
 unmaintained ports that I use.
 (I couldn't find a way to do the
 job with the existing tools like
 pkg_info or portmaster):
 
 #!/bin/sh
 
 prefix=/usr/ports/
 makefile=/Makefile
 
 for file in `pkg_info -oxa | grep /`
 do
 yes=`grep MAIN ${prefix}${file}${makefile} | grep ports`
 if [ -n $yes ]
 then
 echo $file
 fi
 done
 

[SNIP]

Small observation, since that script picks up all of us who use 'ports' in
our maintainer email addresses (myself for example), might I suggest the
following tweak to your script (full address and checking for file
existence):

#!/bin/sh

prefix=/usr/ports/
makefile=/Makefile

for file in `pkg_info -oxa | grep /`
do
 if test -f ${prefix}${file}${makefile}
 then
  yes=`grep MAIN ${prefix}${file}${makefile} | grep -i 'ports@freebsd\.org'`
  if [ -n $yes ]
  then
   echo $file
  fi
 fi
Done

Although in only greping makefiles that exist it doesn't alert you to your
installed ports when the port has been removed from the tree...

It's an interesting situation and I wonder if there is a tool (I suppose
akin to portaudit) that alerts sys admins when ports they have installed are
depreciated or maintainers drop them?  Obviously one can sign up for the
various types of alerts from Freshports, but I expect a few people here have
rolled their own periodic alert tools...

Regards

Eric


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

Re: [HEADS UP] Ports Infrastructure Changes

[Eric]

 devel category is the largest one, how about divide it into :
 
 devel
 devel-perl
 devel-python
 
 wen

Is that not partially why we have the virtual categories to provide language
divisions (not to mention port name prefixes)?  I think were devel to be
split 'broad' functionality would be the best and most useful (although
harder to do than language) way of splitting things down.

Regards

Eric 


___
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: missing libjawt.so pkg_libchk report for eclipse ooo

[Eric Masson]

David Southwell da...@vizion2000.net writes:

Hi,

 What installs libjawt?

Any jre installed ?
e...@srvbsdfenssv:~ locate libjawt.so
/usr/local/diablo-jdk1.6.0/jre/lib/amd64/libjawt.so

Regards

Éric Masson

-- 
  Il veut que frjv disparaisse afin que les contacts entre pirates
  et public soit réduits. Cela afin d'assurer son pain quotidien.
 lepen va etre content d'apprendre que des ges partageant ses idees
 -+- Gleny in: http://www.le-gnu.net - Le Godwin pour les nuls -+-
___
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: rubygem-mail-2.2.10 install failure

[Eric]

 From: David Southwell da...@vizion2000.net

[SNIP]

 ERROR:  Error installing /usr/ports/distfiles/rubygem/mail-2.2.10.gem:
 mail requires i18n (~ 0.4.1, runtime)
 *** Error code 1
 
 Stop in /usr/ports/mail/rubygem-mail.

[SNIP]

I've just submitted a PR (ports/152906 [1]) to upgrade the gem to 2.2.12
which seems to sort out the dependency problem on my clean test system.

Regards

Eric

[1] http://www.freebsd.org/cgi/query-pr.cgi?pr=152906


___
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: becoming a port committor

[Eric]

 I have a lot of free time now that I am retired. I see a large number of
 ports in open status that have been waiting to be committed longer than
 30 days.
 
 What is the procedure to become a ports committor?

Normally you would become active in the ports project, submitting ports and
patches, etc.  Then after some unspecified amount of time (hopefully) an
existing committer will nominate you for a 'commit bit', portmgr@ has to
approve that.  You then you work as a committer, but with a mentor approving
your work, eventually ending up committing things by yourself.

I've also been advised that joining #bsdports on EFnet and making yourself
known will help!

Regards

Eric


___
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: Option in port depending on another port, how to handle ?

[Eric Masson]

Anonymous swel...@gmail.com writes:

Hello,

 Why not extract it as a dependency then?

   .if defined(WITH_HTTP_UWSGI_MODULE)
   CONFIGURE_ARGS+= --add-module=${UWSGI_WRKSRC}/nginx
   BUILD_DEPENDS+=  ${NONEXISTENT}:${PORTSDIR}/www/uwsgi:patch
   UWSGI_WRKSRC!=   ${MAKE} -V WRKSRC -C ${PORTSDIR}/www/uwsgi
   .endif

Well, I've upgraded to nginx-devel as the uwsgi plugin is in the base
distribution.

Don't know if having uwsgi plugin in www/nginx is desirable to a wider
audience.

I don't know if using an older revision of the uwsgi tarball would be a
major issue. If not, I could submit my first patch.

Regards

Thanks for your help

Eric Masson

-- 
 M cliquez sur les deux première bannières dans ce site.
 M http://www.xXxXbzz.fr/diabetique
 scientologie piege a cons
 -+- JS in GNU - La secte des mangeurs de sucre a frappé -+-
___
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: Option in port depending on another port, how to handle ?

[Eric Masson]

Anonymous swel...@gmail.com writes:

Hello,

 NGINX_UWSGI_MODULE_VERSION!= ${MAKE} -V PORTVERSION -C 
 ${PORTSDIR}/www/uwsgi

Great. Seems I really need to improve my make-fu.

Thanks for your answer.

Regards

Éric Masson

-- 
 FFTout le plaisir est pour moi.
 FFVous payez par carte bancaire ?
 Non, par inadvertance.
 -+- OZ in http://www.le-gnu.net : Reponse hamster à terre -+-
___
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: Option in port depending on another port, how to handle ?

[Eric Masson]

Anonymous swel...@gmail.com writes:

Hello again,

 NGINX_UWSGI_MODULE_VERSION!= ${MAKE} -V PORTVERSION -C 
 ${PORTSDIR}/www/uwsgi

Subsidiary question, as uwsgi nginx module needs uwsgi tarball, nginx
distinfo must contain related checksums  size.

Is there any way to avoid duplicating distinfo entries in both ports ?

Regards

Éric Masson

-- 
 si tu est hacker peut tu me donner des conseil ou minicier car je
 suis debutant
 PP Je te conseil 2 bon boukin pour comancé: Bled et Grevisse
 -+- MT In http://www.le-gnu.net Pas minicier, complètement sciés -+-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

net/freeswitch-core

[Eric Masson]

Hello,

When building/installing net/freeswitch-core on an amd64 8.1-RELEASE,
only the following modules are installed in
/usr/local/lib/freeswitch/mod :
e...@srvbsdfenssv:~ ll /usr/local/lib/freeswitch/mod/
total 288
-rwxr-xr-x  1 root  wheel1239 31 aoû 16:24 mod_amr.la
-rwxr-xr-x  1 root  wheel   41228 31 aoû 16:24 mod_amr.so
-rwxr-xr-x  1 root  wheel1251 31 aoû 16:24 mod_amrwb.la
-rwxr-xr-x  1 root  wheel   41208 31 aoû 16:24 mod_amrwb.so
-rwxr-xr-x  1 root  wheel1233 31 aoû 16:24 mod_bv.la
-rwxr-xr-x  1 root  wheel  139239 31 aoû 16:24 mod_bv.so
-rwxr-xr-x  1 root  wheel1263 31 aoû 16:24 mod_cdr_csv.la
-rwxr-xr-x  1 root  wheel   61225 31 aoû 16:24 mod_cdr_csv.so

Modules like mod_sofia, mod_console and many others are missing (on
i386, they're available, as tested on a i386 8.1-RELEASE).

Has anyone an idea regarding this problem, please ?

Script of the build is available here :
http://emss.free.fr/contents/informatique/FreeBSD-amd64-FreeSWITCH/fs_build.7z

Regards

Éric Masson

-- 
 Pourriez vous me dire comment réaliser un fichier autoexecutable ou
 plus presisement le fichier .exe que l'on met dedans !
 -+- T in Guide du Neuneu Usenet : autoexécution de neuneu -+-
___
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: net/freeswitch-core

[Eric Masson]

Jeremy Chadwick free...@jdc.parodius.com writes:

Hi Jeremy,

 Looks like the entire build, and installation, bombs out once it tries
 to deal with something called celt-0.7.1.tar.gz (mod_celt).  Taken
 from the build script:

Ok,

I can reproduce the problem in fs source tree on my box, gmake -d in
mod_celt directory does bomb the same way (locale settings removed to
get vanilla error messages)
file:///vol0/ports/distfiles/celt-0.7.1.tar.gz: Unsupported scheme `file'.
cannot find celt-0.7.1.tar.gz

Running gmake -d doesn't enlighten me about the possible cause of the
problem (output attached), maybe I'm missing something obvious...

Regards

Éric Masson

Script started on Tue Aug 31 20:08:56 201
GNU Make 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

This program built for amd64-portbld-freebsd8.1
Reading makefiles...
Reading makefile `Makefile'...
Reading makefile `../../../../build/modmake.rules' (search path) (no ~ 
expansion)...
Updating makefiles
 Considering target file `../../../../build/modmake.rules'.
  Looking for an implicit rule for `../../../../build/modmake.rules'.
  Trying pattern rule with stem `modmake.rules'.
  Trying implicit prerequisite `../../../../build/modmake.rules.c'.
  Trying pattern rule with stem `modmake.rules'.
  Trying implicit prerequisite `../../../../build/modmake.rules.lo'.
  Trying pattern rule with stem `modmake.rules'.
  Trying implicit prerequisite `../../../../build/modmake.rules.o'.
  Trying pattern rule with stem `modmake.rules'.
  Trying implicit prerequisite `../../../../build/modmake.rules.cpp'.
  Trying pattern rule with stem `modmake.rules'.
  Trying implicit prerequisite `../../../../build/modmake.rules,v'.
  Trying pattern rule with stem `modmake.rules'.
  Trying implicit prerequisite `../../../../build/RCS/modmake.rules,v'.
  Trying pattern rule with stem `modmake.rules'.
  Trying implicit prerequisite `../../../../build/RCS/modmake.rules'.
  Trying pattern rule with stem `modmake.rules'.
  Trying implicit prerequisite `../../../../build/s.modmake.rules'.
  Trying pattern rule with stem `modmake.rules'.
  Trying implicit prerequisite `../../../../build/SCCS/s.modmake.rules'.
  Trying pattern rule with stem `modmake.rules'.
  Trying implicit prerequisite `../../../../build/modmake.rules.c'.
  Looking for a rule with intermediate file `../../../../build/modmake.rules.c'.
   Avoiding implicit rule recursion.
   Trying pattern rule with stem `modmake.rules'.
   Trying implicit prerequisite `../../../../build/modmake.rules.w'.
   Trying pattern rule with stem `modmake.rules.c'.
   Trying implicit prerequisite `../../../../build/modmake.rules.c,v'.
   Trying pattern rule with stem `modmake.rules.c'.
   Trying implicit prerequisite `../../../../build/RCS/modmake.rules.c,v'.
   Trying pattern rule with stem `modmake.rules.c'.
   Trying implicit prerequisite `../../../../build/RCS/modmake.rules.c'.
   Trying pattern rule with stem `modmake.rules.c'.
   Trying implicit prerequisite `../../../../build/s.modmake.rules.c'.
   Trying pattern rule with stem `modmake.rules.c'.
   Trying implicit prerequisite `../../../../build/SCCS/s.modmake.rules.c'.
   Trying pattern rule with stem `modmake.rules'.
   Trying implicit prerequisite `../../../../build/modmake.rules.w'.
   Looking for a rule with intermediate file 
`../../../../build/modmake.rules.w'.
Avoiding implicit rule recursion.
Avoiding implicit rule recursion.
Trying pattern rule with stem `modmake.rules.w'.
Trying implicit prerequisite `../../../../build/modmake.rules.w,v'.
Trying pattern rule with stem `modmake.rules.w'.
Trying implicit prerequisite `../../../../build/RCS/modmake.rules.w,v'.
Trying pattern rule with stem `modmake.rules.w'.
Trying implicit prerequisite `../../../../build/RCS/modmake.rules.w'.
Trying pattern rule with stem `modmake.rules.w'.
Trying implicit prerequisite `../../../../build/s.modmake.rules.w'.
Trying pattern rule with stem `modmake.rules.w'.
Trying implicit prerequisite `../../../../build/SCCS/s.modmake.rules.w'.
  Trying pattern rule with stem `modmake.rules'.
  Trying implicit prerequisite `../../../../build/modmake.rules.lo'.
  Looking for a rule with intermediate file 
`../../../../build/modmake.rules.lo'.
   Avoiding implicit rule recursion.
   Trying pattern rule with stem `modmake.rules'.
   Rejecting impossible implicit prerequisite 
`../../../../build/modmake.rules.c'.
   Trying pattern rule with stem `modmake.rules'.
   Trying implicit prerequisite `../../../../build/modmake.rules.cpp'.
   Trying pattern rule with stem `modmake.rules.lo'.
   Trying implicit prerequisite `../../../../build/modmake.rules.lo,v'.
   Trying pattern rule with stem `modmake.rules.lo'.
   Trying implicit prerequisite `../../../../build/RCS/modmake.rules.lo,v'.
   Trying pattern rule with 

Re: current ports Mk make fetch calls wget fails to support schemes

[Eric Masson]

Jeremy Chadwick free...@jdc.parodius.com writes:

Hi,

 Hmm... Can't reproduce it here, but this is now the 2nd report of this
 problem to hit -ports.

Removing wget from path solves the issue faced when building mod_celt in
net/freeswitch.

Thanks for you help diagnosing the problem.

Éric Masson

-- 
 Il vaut mieux de dormir pendant 6 mois que vivant dans constante
 culturelle l'obscurité
 -+- Pelle in http://www.le-gnu.net Pelle le con quérant -+-
___
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 ports Problem Reports for ports you maintain

[Eric Masson]

lini...@freebsd.org writes:

Hello,

 The PRs are listed below.

 PR number:  87397
 PR title:   [patch] incorrect use of PAPERSIZE make variable in some 
 ports
 category:   print
 portname:   lpr-wrapper
 submitter:  ga...@zahemszky.hu
 arrival date:   2005-10-13 20:40:18
 PR state:   open
 URL:http://www.FreeBSD.org/cgi/query-pr.cgi?pr=87397

A followup has been submitted to the PR.

Regards

Eric Masson

-- 
 Mettre d'un coté ceux qui nous pompent l'air, de l'autre ceux qui
 brassent du vent. Nous obtiendrons un Usenet climatisé, c'est ça le
 génie français. Ca risque même d'être un peu trop ventilé.
 -+- MP in http://www.le-gnu.net : Clim et châtiment -+-
___
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: [new port] usage of shar command

[Eric]

 The major problems with backticks is that they tend to be inconspicuous
 (and easily confused with bits of dust or fly-droppings) and are often
 difficult to distinguish from quotes.
 
 Rather than write `find port_dir` (note the backticks), IMO, it is
 far easier to write $(find port_dir) - which is syntactically the
 same but visually more obvious.
 
 That's a fair point. Do you think that the text as it currently exists
 is sufficiently clear, or do you think that it still needs the
 modification you're suggesting? I'm happy to make the change (or someone
 else can if they so desire) if that's what people thing is the right way
 to go.
 
 
 Doug
 
 The text as its currently exists is a long way from being clear to a
 first timer. And I am talking about the new change that just went in.
 
 shar `find port_dir` (note the backticks),
 
 or
 
 shar $(find port_dir)
 
 both address the problem nicely.
 
 By all means go and make the correction.

I'd second making it clearer, certainly: shar `find port_dir` threw me when
I first started writing ports and was looking to submit my work.  I think
part of the issue was just I'd never used the shell archive command before
so I had no idea quite what 'shar' actually was.  Perhaps adding a one liner
to explain what is actually going to happen and why your doing it might be
useful?

Personally I think the second suggestion of shar $(find port_dir) is the
better one, it's far less likely to get mangled by font display and I expect
it's easier for people to located $() on their keyboards than ` (backtick)

Regards

Eric


___
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

[Medical package] - Presentation of FreeDiams: Free prescriber

[Eric MAEKER]

Hi all,

FreeDiams is a free, open source, BSD revised licenced app. It is part  
of the FreeMedForms project. Since version 0.4.0, FreeDiams has a  
great number of good features. Three drugs databases are available :  
French, Canada, USA.


You can find some descriptions here:

http://www.freemedforms.com/

And the user's manual here:

http://ericmaeker.fr/FreeMedForms/di-manual/

FreeDiams is actually available for MacOs, Linux and Win32. It is  
supported by the debian-med group and OpenSuse.


A source package of the v0.4.0 will be soon available in the google  
code pages :


http://code.goole.com/p/freemedforms

You can already download the sources from the SVN hosted in the google  
code site.


We are looking for sponsors, packagers, devs, drugs databases  
creators, translators... Code is Qt/C++, DB are SQLite.


If you are interessed by this project, please feel free to present  
yourself to the FreeMedForms community on its mailing list : freemedfo...@googlegroups.com


By advance, thanks for your help.
Eric Maeker, MD, France
___
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: Call for testers: www/shellinabox (Shell in a Box)

[Eric]

 From: Vitaly Magerya vmage...@gmail.com
[SNIP]
 4. Move the certificate directory to /var/shellinabox or similar
(what's our conventional location for this kind of files?).
 
 I'm not sure on the 4 though. Any thoughts?

Id say possibly /var/db/shellinabox

/var/db/ seems to be used by a fair number of services for record keeping of
various things.


___
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 ports Problem Reports for ports you maintain

[Eric Masson]

lini...@freebsd.org writes:

Hello,

 PR number:  87397
 PR title:   [patch] incorrect use of PAPERSIZE make variable in some 
 ports
 category:   print
 portname:   lpr-wrapper
 submitter:  ga...@zahemszky.hu
 arrival date:   2005-10-13 20:40:18
 PR state:   open
 URL:http://www.FreeBSD.org/cgi/query-pr.cgi?pr=87397

A fix has been sent in the PR audit trail.

Kind Regards

Éric Masson

-- 
 SS Qu'entend-je comme rumeur? les passes de Free auraient été piratés?
 Vous avez une copie de la base?  Si oui, gardez-la bien au chaud, ça
 nous fera un backup.
 -+- Rani in http://www.le-gnu.net : Et vlan, passe moi la base -+-
___
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: License Framework: Develop Best Practices

[Eric]

 From: Philip M. Gollucci pgollu...@p6m7g8.com
 Date: Tue, 15 Jun 2010 02:03:08 +
 
 On 06/15/10 00:46, Marco Bröder wrote:
 I find it especially important to have a expression for 'version X or any
 later version' (for example 'LGPLv2+'), since the following dummy example is
 not adequate:
 A very good idea, but not neccessarily the best one.  Future versions of
 licenses are not always backwards compatible?  Its GPLv2 vs GPLv3 one
 such example ?

Although does it matter in those cases about backwards compatibility?  If
the software has been released under (for example) GPLv2 or higher then
hasn't the author essentially already consented to any future version of the
GPL, no matter how incompatible they may be?

If however they re-release software under later licences (dual or otherwise)
then that's explicit and the licence entry would either be the new licence
or a combination of the new and old entries.

It would seem from reading the various posting that the two missing features
are some sort of clean way of saying this license or higher and possibly
something along the lines of like this licence for cases where 99% is the
same as an existing OS licence, but I guess that last one comes down to a
point of purpose.  Is the licence framework supposed to be a solid legal
structure or is it much like the pkg-descriptions just something we can
filter against and use to help guide us to the ports we want to install?



___
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

ports/146058 (p5-Module-Build upgrade)

[Eric]

Hi,

I wondered if anyone could take a look at (and hopefully commit) a diff I
submitted to upgrade p5-Module-Build (to fix a bug that's holding up another
port).  I've not heard anything from the maintainer when I first contacted
(9/4/10) them and the ticket has now been assigned to them for a few weeks
with no activity.

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

Thanks and regards

Eric



___
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

Rubygem hosting (bsd.sites.mk)

[Eric]

Dear all,

At the risk of cross post flaming, I thought I would bring up the matter of
RubyGem ports on the main ports list having heard nothing back from my
initial enquiry on the ruby lists [1], but perhaps since it's really about
ports then this is the right place!

I've noticed that from time to time the general migration of gems from
rubyforge.org to gemcutter.org/rubygems.org [2] (and indeed GitHub[3]) has
been mentioned on the FreeBSD ruby and ports lists, but it would appear
nothing has been changed yet in the bsd.sites.mk file to accommodate this
migration (may have missed a pr in progress of course).  Since I find myself
writing quick gem ports every now and then I thought it would be worth
bringing the matter up for a quick discussion before sending in my suggested
patch as a PR.

I personally think the cleanest thing to do is add anther MASTER_SITE for
RubyGems.org.  Now it would be nice to add their download location directly,
but that does a 302 redirect to Amazon or CloudFiles for the actual
download, so I think we'll need to pop those locations into bsd.sites.mk
directly. Thus:

# See http://rubygems.org/pages/about
.if !defined(IGNORE_MASTER_SITE_RUBYGEMS)
MASTER_SITE_RUBYGEMS+= \
 http://production.s3.rubygems.org/gems/%SUBDIR%/ \
 http://production.cf.rubygems.org/gems/%SUBDIR%/
.endif

Since it will be pretty cool to be able to update many ports by just
s/RF/RG/ in many cases I think we should have an abbreviation for the
RubyGems site thus:

MASTER_SITES_ABBREVS= CPAN:PERL_CPAN \
  SF:SOURCEFORGE \
  SFJP:SOURCEFORGE_JP \
  RG:RUBYGEMS \
  RF:RUBYFORGE

Now one thing I'm not 100% sure on is the use of the '%SUBDIR%' in the
paths, in this case none of the gems will be located in subdirectories since
the gem hosting is flat.  It would appear that the standard way of doing
things in the bsd.sites.mk is to specify a '%SUBDIR%' element, then if a
pattern is defined in the 'MASTER_SITES_SUBDIRS', that element is replaced.
Is that correct?  So for a RubyForge example, the pattern in
'MASTER_SITES_SUBDIRS' is 'RUBYFORGE:${PORTNAME:L}', which would be the name
of the port lowercased (I guess). So say for 'file-tail' that would make the
download location: 
http://files.rubyforge.vm.bytemark.co.uk/file-tail/file-tail-n.n.n.gem

So it occurs to me that we could either just not have a
'MASTER_SITES_SUBDIRS' entry for the RUBYGEMS site (easy) or we could have
one that was just the 'hardcoded' gems subdirectory, something like this:

  RUBYGEMS:gems \

Like the CENKES entry in the file.  We would then make the
'MASTER_SITE_RUBYGEMS' entries like this:
http://production.s3.rubygems.org/%SUBDIR%/
Not quite sure what the best FreeBSD ports protocol is here.  I personally
feel perhaps that makes it more complicated than it needs to be?


Finally it's a good opportunity to replace the dead mirror in the RubyForge
entry, since 'http://files.rubyforge.mmmultiworks.com' seems to have been
down for some time now.

# See http://rubyforge.org/credits/
.if !defined(IGNORE_MASTER_SITE_RUBYFORGE)
MASTER_SITE_RUBYFORGE+= \
 http://files.rubyforge.vm.bytemark.co.uk/%SUBDIR%/ \
 http://files.ruby.inoack.com/%SUBDIR%/
.endif

Any thoughts, comments, suggestions before I put a PR and associated diff
in?

Regards

Eric

---
[1] http://lists.freebsd.org/pipermail/freebsd-ruby/2010-April/000290.html
[2]
  http://lists.freebsd.org/pipermail/freebsd-ruby/2010-February/000250.html
  http://lists.freebsd.org/pipermail/freebsd-ports/2009-December/058516.html
[3] http://lists.freebsd.org/pipermail/freebsd-ruby/2010-January/000220.html

---
Diff of proposed changes for those interested:

--- bsd.sites.mk.orig2010-04-06 02:53:13.0 +0100
+++ bsd.sites.mk2010-05-04 14:54:22.0 +0100
@@ -1141,8 +1141,15 @@
 # See http://rubyforge.org/credits/
 .if !defined(IGNORE_MASTER_SITE_RUBYFORGE)
 MASTER_SITE_RUBYFORGE+= \
-http://files.rubyforge.mmmultiworks.com/%SUBDIR%/ \
-http://files.rubyforge.vm.bytemark.co.uk/%SUBDIR%/
+http://files.rubyforge.vm.bytemark.co.uk/%SUBDIR%/ \
+http://files.ruby.inoack.com/%SUBDIR%/
+.endif
+
+# See http://rubygems.org/pages/about
+.if !defined(IGNORE_MASTER_SITE_RUBYGEMS)
+MASTER_SITE_RUBYGEMS+= \
+http://production.s3.rubygems.org/gems/%SUBDIR%/ \
+http://production.cf.rubygems.org/gems/%SUBDIR%/
 .endif
 
 .if !defined(IGNORE_MASTER_SITE_SAMBA)
@@ -1493,6 +1500,7 @@
 MASTER_SITES_ABBREVS=CPAN:PERL_CPAN \
 SF:SOURCEFORGE \
 SFJP:SOURCEFORGE_JP \
+RG:RUBYGEMS \
 RF:RUBYFORGE
 MASTER_SITES_SUBDIRS=\
 APACHE_JAKARTA:${PORTNAME:S,-,/,}/source \


___
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 ports Problem Reports for ports you maintain

[Eric Masson]

lini...@freebsd.org writes:

Hello Mark,

 PR number:  87397
 PR title:   [patch] incorrect use of PAPERSIZE make variable in some 
 ports
 category:   print
 portname:   lpr-wrapper
 submitter:  ga...@zahemszky.hu
 arrival date:   2005-10-13 20:40:18
 PR state:   open
 URL:http://www.FreeBSD.org/cgi/query-pr.cgi?pr=87397

An update has been submitted to this PR on 2009/12/07.

Regards

Éric Masson

-- 
 Je dirais, à voir sortir les noms de nouveaux groupes, que la
 hiérarchie fr. est celle qui évolue le moins et le moins vite. Sans
 doûte pour favoriser la pénétration d'Internet dans les foyers...
 -+- ALG in: http://www.le-gnu.net - La stratégie fufer -+-
___
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: amavisd-new crashing

[Eric Sheesley]

Decided to check the core dump that perl left behind but this is all i
see(minus a couple thousand lines above this point with no more detail
than given here:

#1345 0x102454ff in ?? ()
#1346 0x1424448d in ?? ()
#1347 0x5440f750 in ?? ()
#1348 0x0002 in ?? ()
#1349 0x688e0375 in ?? ()
#1350 0x0158b814 in ?? ()
#1351 0xcd50 in ?? ()
#1352 0x90feeb80 in ?? ()
#1353 0x282d9b04 in ?? ()
#1354 0x0001 in ?? ()
#1355 0xbfbfeeb8 in ?? ()
#1356 0x0004 in ?? ()
Cannot access memory at address 0xbfc0
(gdb)


Sean wrote:
 On Thu, 10 Sep 2009, Eric Sheesley wrote:
 
 [mail.log snipped]
 
 
 What's in /var/log/messages? Or dmesg?
 
 I started having amavisd-new cause perl to coredump, apparently deep in
 the middle of
 Converter::UULib when a coredump was forced.
 
 
 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

amavisd-new crashing

[Eric Sheesley]

For the past week or so I've had 2-3 different emails that, as they  
are attempting to be delivered end up crashing amavisd-new(just one  
instance, not the whole daemon) leading the the error:  queue file  
write error from postfix.  Both messages appear to have been 8bitmime  
encoded from a quick glance, but no other common points.  These emails  
will continually crash amavis every 15 minutes as the servers attempt  
delivery.  I've used portmanager to rebuild amavis and all  
dependencies with no change.  Any ideas on what could be wrong?

___
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: amavisd-new crashing

[Eric Sheesley]

Here is one sample of the log(level 5 logging on).  not very descriptive
about the problem, at least i don't see it.

Sep 10 19:00:07 rogue postfix/smtpd[77645]: connect from
tx2ehsobe003.messaging.microsoft.com[65.55.88.13]
Sep 10 19:00:07 rogue postfix/smtpd[77645]: NOQUEUE:
client=tx2ehsobe003.messaging.microsoft.com[65.55.88.13]
Sep 10 19:00:08 rogue amavis[77712]: (77712-01) ESMTP::10024
/var/amavis/tmp/amavis-20090910T190007-77712: froma...@fromaddr.com -
mya...@shadowlair.com SIZE=7072 BODY=7BIT Received: from
rogue.shadowlair.com ([127.0.0.1]) by localhost (rogue.shadowlair.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP for
eshee...@shadowlair.com; Thu, 10 Sep 2009 19:00:07 -0400 (EDT)
Sep 10 19:00:08 rogue amavis[77712]: (77712-01) Checking: SukXX+6vDV2U
[65.55.88.13] froma...@fromaddr.com - mya...@shadowlair.com
Sep 10 19:00:08 rogue amavis[77712]: (77712-01) p001 1 Content-Type:
text/plain, size: 3607 B, name:
Sep 10 19:00:08 rogue postfix/smtpd[77645]: warning: lost connection
with proxy 127.0.0.1:10024
Sep 10 19:00:08 rogue amavis[78041]: TIMING [total 5 ms] - bdb-open: 5
(100%)100, rundown: 0 (0%)100
Sep 10 19:00:08 rogue postfix/cleanup[78042]: 4EDE850837:
message-id=20090910230008.4ede850...@rogue.shadowlair.com
Sep 10 19:00:08 rogue postfix/smtpd[77645]: disconnect from
tx2ehsobe003.messaging.microsoft.com[65.55.88.13]


Per olof Ljungmark wrote:
 Eric Sheesley wrote:

 For the past week or so I've had 2-3 different emails that, as they
 are attempting to be delivered end up crashing amavisd-new(just one
 instance, not the whole daemon) leading the the error:  queue file
 write error from postfix.  Both messages appear to have been 8bitmime
 encoded from a quick glance, but no other common points.  These emails
 will continually crash amavis every 15 minutes as the servers attempt
 delivery.  I've used portmanager to rebuild amavis and all
 dependencies with no change.  Any ideas on what could be wrong?
 
 Hi,
 
 Both amavis and Postfix can be made to provide rather substantial
 logging, that's what I would have done in your case. Or do you already
 have some logs to share?
 
 Also, did you check that you did not run out of memory?
 
 HTH,
 
 -- 
 per
___
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: amavisd-new crashing

[Eric Sheesley]

Actually, the directory is set to vscan as it should be(amavis runs as
that) and that user has rw privs.  If you notice below, the pid of the
processes is different between the area where content-type is mentioned
and the bdb is referenced.  For some reason there is a very brutal crash
before any real checks are run.

I've rebuilt amavis and all dependencies using portmanager with no
change.  Any other thoughts or methods of debugging.  One of the emails
causing this was sent by a friend, so not even malicious, just causing a
crash.

Chuck Swiger wrote:
 Hi--
 
 On Sep 10, 2009, at 4:23 PM, Eric Sheesley wrote:
 Sep 10 19:00:08 rogue amavis[77712]: (77712-01) ESMTP::10024
 /var/amavis/tmp/amavis-20090910T190007-77712: froma...@fromaddr.com -
 mya...@shadowlair.com SIZE=7072 BODY=7BIT Received: from
 rogue.shadowlair.com ([127.0.0.1]) by localhost (rogue.shadowlair.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for
 eshee...@shadowlair.com; Thu, 10 Sep 2009 19:00:07 -0400 (EDT)
 Sep 10 19:00:08 rogue amavis[77712]: (77712-01) Checking: SukXX+6vDV2U
 [65.55.88.13] froma...@fromaddr.com - mya...@shadowlair.com
 Sep 10 19:00:08 rogue amavis[77712]: (77712-01) p001 1 Content-Type:
 text/plain, size: 3607 B, name:
 Sep 10 19:00:08 rogue postfix/smtpd[77645]: warning: lost connection
 with proxy 127.0.0.1:10024
 Sep 10 19:00:08 rogue amavis[78041]: TIMING [total 5 ms] - bdb-open: 5
 (100%)100, rundown: 0 (0%)100
 
 It sounds like amavisd can't open a BerkeleyDB database (probably the
 nanny/cache/snmp stuff).  Make sure that /var/amavis/db exists and is
 writable by the amavisd or vscan user, whatever you are running amavisd as:
 
 # ls -l /var/amavis/db
 total 556
 -rw-r-  1 vscan  vscan   24576 Sep  9 19:01 __db.001
 -rw-r-  1 vscan  vscan  131072 Sep  9 18:44 __db.002
 -rw-r-  1 vscan  vscan  270336 Sep 10 11:43 __db.003
 -rw-r-  1 vscan  vscan  360448 Sep  9 18:44 __db.004
 -rw-r-  1 vscan  vscan4096 Sep  9 14:20 cache-expiry.db
 -rw-r-  1 vscan  vscan   90112 Sep 10 14:01 cache.db
 -rw-r-  1 vscan  vscan   12288 Sep  9 14:20 nanny.db
 -rw-r-  1 vscan  vscan   12288 Sep  9 14:20 snmp.db
 
 Regards,
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: amavisd-new crashing

[Eric Sheesley]

Another sample attached:

Sep 10 20:15:41 rogue postfix/smtpd[59483]: connect from
mail-vw0-f180.google.com[209.85.212.180]
Sep 10 20:15:41 rogue postfix/smtpd[59483]: NOQUEUE:
client=mail-vw0-f180.google.com[209.85.212.180]
Sep 10 20:15:41 rogue amavis[77720]: (77720-02) ESMTP::10024
/var/amavis/tmp/amavis-20090910T192517-77720: deadsen...@gmail.com -
e...@shadowlair.com Received: from rogue.shadowlair.com ([127.0.0.1])
by localhost (rogue.shadowlair.com [127.0.0.1]) (amavisd-new, port
10024) with ESMTP for mya...@shadowlair.com; Thu, 10 Sep 2009 20:15:41
-0400 (EDT)
Sep 10 20:15:41 rogue amavis[77720]: (77720-02) dkim: VALID
Author+Sender+MailFrom signature by i...@gmail.com, From:
deadsen...@gmail.com, a=rsa-sha256, c=relaxed/relaxed, s=gamma,
d=gmail.com
Sep 10 20:15:41 rogue amavis[77720]: (77720-02) dkim: VALID
Author+Sender+MailFrom signature by i=deadsen...@gmail.com, From:
deadsen...@gmail.com, a=rsa-sha1, c=nofws, s=gamma, d=gmail.com
Sep 10 20:15:41 rogue amavis[77720]: (77720-02) Checking: 2UIxlfrQ4TAm
[209.85.212.180] deadsen...@gmail.com - mya...@shadowlair.com
Sep 10 20:15:41 rogue amavis[77720]: (77720-02) p003 1 Content-Type:
multipart/alternative
Sep 10 20:15:41 rogue amavis[77720]: (77720-02) p001 1/1 Content-Type:
text/plain, size: 3383 B, name:
Sep 10 20:15:41 rogue amavis[77720]: (77720-02) p002 1/2 Content-Type:
text/html, size: 5031 B, name:
Sep 10 20:15:41 rogue postfix/smtpd[59483]: warning: lost connection
with proxy 127.0.0.1:10024
Sep 10 20:15:41 rogue amavis[59998]: TIMING [total 6 ms] - bdb-open: 6
(100%)100, rundown: 0 (0%)100
Sep 10 20:15:41 rogue postfix/cleanup[59992]: 8EA9F5083B:
message-id=20090911001541.8ea9f50...@rogue.shadowlair.com
Sep 10 20:15:41 rogue postfix/smtpd[59483]: disconnect from
mail-vw0-f180.google.com[209.85.212.180]


Chuck Swiger wrote:
 Hi--
 
 On Sep 10, 2009, at 4:23 PM, Eric Sheesley wrote:
 Sep 10 19:00:08 rogue amavis[77712]: (77712-01) ESMTP::10024
 /var/amavis/tmp/amavis-20090910T190007-77712: froma...@fromaddr.com -
 mya...@shadowlair.com SIZE=7072 BODY=7BIT Received: from
 rogue.shadowlair.com ([127.0.0.1]) by localhost (rogue.shadowlair.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for
 eshee...@shadowlair.com; Thu, 10 Sep 2009 19:00:07 -0400 (EDT)
 Sep 10 19:00:08 rogue amavis[77712]: (77712-01) Checking: SukXX+6vDV2U
 [65.55.88.13] froma...@fromaddr.com - mya...@shadowlair.com
 Sep 10 19:00:08 rogue amavis[77712]: (77712-01) p001 1 Content-Type:
 text/plain, size: 3607 B, name:
 Sep 10 19:00:08 rogue postfix/smtpd[77645]: warning: lost connection
 with proxy 127.0.0.1:10024
 Sep 10 19:00:08 rogue amavis[78041]: TIMING [total 5 ms] - bdb-open: 5
 (100%)100, rundown: 0 (0%)100
 
 It sounds like amavisd can't open a BerkeleyDB database (probably the
 nanny/cache/snmp stuff).  Make sure that /var/amavis/db exists and is
 writable by the amavisd or vscan user, whatever you are running amavisd as:
 
 # ls -l /var/amavis/db
 total 556
 -rw-r-  1 vscan  vscan   24576 Sep  9 19:01 __db.001
 -rw-r-  1 vscan  vscan  131072 Sep  9 18:44 __db.002
 -rw-r-  1 vscan  vscan  270336 Sep 10 11:43 __db.003
 -rw-r-  1 vscan  vscan  360448 Sep  9 18:44 __db.004
 -rw-r-  1 vscan  vscan4096 Sep  9 14:20 cache-expiry.db
 -rw-r-  1 vscan  vscan   90112 Sep 10 14:01 cache.db
 -rw-r-  1 vscan  vscan   12288 Sep  9 14:20 nanny.db
 -rw-r-  1 vscan  vscan   12288 Sep  9 14:20 snmp.db
 
 Regards,
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: ghost ports CFLAGS

[Eric Damien]

Well, I just edited the /etc/make.conf. About the clean build directories, I
performed make clean (even if portmaster is already supposed to do so,
unless instructed otherwise); I even deleted the ports tree and made a fresh
portsnap fetch extract: no use.
Not to stay stuck, I decied to include a ports.conf in make.conf just to
switch back to the other compiler (actually gcc43/g++43), on those
problematic ports. But then again, that is a temporary solution.

Do you think there may be another path to explore ?

Thanks,

Eric Damien.

On Tue, Jul 28, 2009 at 11:34 AM, Lowell Gilbert 
freebsd-ports-lo...@be-well.ilk.org wrote:

 Eric Damien jaf...@gmail.com writes:

  I edited my /etc/make.conf in order to change the default compiler via
  the CC and CXX variables. I also happened to edit the CFLAGS value,
  all of this changes enclosed within a conditional check on the
  directory, of the form:
  .if ${CURDIR:M*/ports*}
  CFLAGS= -mtune=amdfam10 -msse4e
  .endif
  I made a general config using postmaster.
  After some trouble with some ports, I decided to get rid of those
  modifications and commented the above form.
  But, I was surprised to see that some ports still present this value
  of CFLAGS at building time.
  How can I correct this mistake.

 Just a guess; you built them previously and didn't clean the build
 directories?

 Or maybe you put those options in a portmaster config file?
 [ /usr/local/etc/portmaster.rc or $HOME/.portmasterrc ...]

___
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

ghost ports CFLAGS

[Eric Damien]

Good morning.

I edited my /etc/make.conf in order to change the default compiler via 
the CC and CXX variables. I also happened to edit the CFLAGS value, all 
of this changes enclosed within a conditional check on the directory, of 
the form:

.if ${CURDIR:M*/ports*}
CFLAGS= -mtune=amdfam10 -msse4e
.endif
I made a general config using postmaster.
After some trouble with some ports, I decided to get rid of those 
modifications and commented the above form.
But, I was surprised to see that some ports still present this value of 
CFLAGS at building time.

How can I correct this mistake.

Thanks,

Eric.
___
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

open-vm-tools on -current

[Eric Masson]

Hello,

While building open-vm-tools  open-vm-tools-nox11 on today's -current,
I get the following error message :

cc -O2 -pipe -fno-strict-aliasing  -Wall -Werror -Werror -D_KERNEL -DKLD_MODULE 
-nostdinc   -I. -I@ -I@/contrib/altq -finline-limit=8000 --param 
inline-unit-growth=100 --param large-function-growth=1000 -fno-common  
-mno-align-long-strings -mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow 
-mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 
-fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef 
-Wno-pointer-sign -fformat-extensions -c vfsops.c
vfsops.c:118: error: conflicting types for 'VMBlockVFSMount'
vfsops.c:70: error: previous declaration of 'VMBlockVFSMount' was here
vfsops.c:259: error: conflicting types for 'VMBlockVFSUnmount'
vfsops.c:74: error: previous declaration of 'VMBlockVFSUnmount' was here
vfsops.c:343: error: conflicting types for 'VMBlockVFSRoot'
vfsops.c:71: error: previous declaration of 'VMBlockVFSRoot' was here
vfsops.c:379: error: conflicting types for 'VMBlockVFSStatFS'
vfsops.c:73: error: previous declaration of 'VMBlockVFSStatFS' was here
vfsops.c:389:64: error: macro VFS_STATFS passed 3 arguments, but takes just 2
vfsops.c: In function 'VMBlockVFSStatFS':
vfsops.c:389: error: 'VFS_STATFS' undeclared (first use in this function)
vfsops.c:389: error: (Each undeclared identifier is reported only once
vfsops.c:389: error: for each function it appears in.)
vfsops.c: At top level:
vfsops.c:429: error: conflicting types for 'VMBlockVFSSync'
vfsops.c:72: error: previous declaration of 'VMBlockVFSSync' was here
*** Error code 1

Stop in 
/usr/ports/emulators/open-vm-tools-nox11/work/open-vm-tools-2009.03.18-154848/modules/freebsd/vmblock.
*** Error code 1

Stop in 
/usr/ports/emulators/open-vm-tools-nox11/work/open-vm-tools-2009.03.18-154848/modules.
*** Error code 1

Stop in 
/usr/ports/emulators/open-vm-tools-nox11/work/open-vm-tools-2009.03.18-154848.
*** Error code 1

Stop in /usr/ports/emulators/open-vm-tools-nox11.

Full transcript is available here :
http://emss.free.fr/contents/informatique/open.log

Regards
 
-- 
 Tu est nez avec un cerveau  tu est grand maintenant 
 il serait temps que tu commence à t'en servir 
 -+- WC in GNU : Il est nez le divin neuneu -+-

___
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: OpenProj

[Eric L. Chen]

On Thu, 2009-02-26 at 11:18 +0530, Nataraj S Narayan wrote:
 Hi
 
 There is a port for Openproj a Project Management software in
 /usr/ports/deskutils.
 
 Is it a working one? I tried to get it compiled on FreeBSD 7.0 and
 did'nt succeed. It was asking for JDK file to be manually downloaded.
 
 Presently I am installing 7.1. Could OpenProj setup be any different now?
 
 regards
 
 Nataraj

If you won't compile java (it takes long time), install
java/diablo-jre16, but still need download manually.

In java/diablo-jre16:
Because of licensing restrictions, you must fetch the distribution
manually.

/Eric


___
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: UCS4 in python 2.6 broken

[Eric L. Chen]

On Wed, 2009-02-18 at 10:06 +0100, Dominic Fandrey wrote:
 I'm running sonata with Python 2.6, or rather I used to:
 
 File /usr/local/lib/python2.6/site-packages/gtk-2.0/glib/__init__.py, line 
 30, in module
 from glib._glib import *
 ImportError: /usr/local/lib/python2.6/site-packages/gtk-2.0/glib/_glib.so: 
 Undefined symbol PyUnicodeUCS4_DecodeUTF8
 
 The python26 port is configured correctly:
 # cd /usr/ports/lang/python26
 # make -VWITH_UCS4
 true
 #
Try reinstall py26-gobject-2.16.0 py26-cairo-1.8.2,
# portmaster py26-gobject-2.16.0 py26-cairo-1.8.2

/Eric


___
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: BIG Update for www/webalizer

[Eric Zimmerman]

John Marshall wrote:

I updated ports on one of our web servers today and discovered that
webalizer is suddenly a lot different.

A couple of days ago the port was upgraded from 2.1.10 to 2.20.1.
- command line switches have changed
- configuration file options have changed
- defaults have changed

Nothing in /usr/ports/UPDATING :-)

WARNING: Check the man page and your config files before blindly running
the new version!



thanks for the info. The main webalizer page states:

July 12, 2008  	 	Version 2.20-01 has been released. This is a drop in 
replacement for sites running v2.01 with no additional changes required, 
and all users are encouraged to upgrade when possible. Many new and 
exciting features have been added in this release. See the  CHANGES file 
for a list of what's been changed/added/fixed. Go to the download page 
to obtain a copy in your preferred format.




any idea what command line options changed based on your experience? I 
didnt see mention of command line changes at:


ftp://ftp.mrunix.net/pub/webalizer/CHANGES

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

Re: BIG Update for www/webalizer

[Eric Zimmerman]

Paul Schmehl wrote:
--On Monday, July 21, 2008 09:55:07 -0600 Eric Zimmerman 
[EMAIL PROTECTED] wrote:


thanks for the info. The main webalizer page states:

July 12, 2008   Version 2.20-01 has been released. This is a 
drop in
replacement for sites running v2.01 with no additional changes 
required, and

all users are encouraged to upgrade when possible. Many new and exciting
features have been added in this release. See the  CHANGES file for a 
list of
what's been changed/added/fixed. Go to the download page to obtain a 
copy in

your preferred format.

any idea what command line options changed based on your experience? I 
didnt

see mention of command line changes at:



Just for reference:

# webalizer -V
Webalizer V2.01-10 (FreeBSD 7.0-STABLE) English
Copyright 1997-2001 by Bradford L. Barrett


i did a comparison against the new version and there arent any missing 
or changed command line switches.

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

Re: Trouble building guile 1.8.4 (segfault in gen-scmconfig)

[Eric Schuele]

On 04/30/2008 11:35, Jason Evans wrote:
 Eric Schuele wrote:
 On 04/28/2008 16:31, Jason Evans wrote:
 What is liblthread?  

 linuxthreads, as Mezz mentioned.

 It looks to be interacting badly with malloc.

 ok.  any thoughts as to why, or how to fix it?
 
 Most likely, the linuxthreads port is allocating memory within one of
 the pthread_mutex-related functions (pthread_mutex_init()?), which is
 causing infinite recursion.  The easy solution is to stop using
 linuxthreads.  

For the archives:
Removing linuxthreads (which was not being used by anything on my
system) did in fact solve the issue.

Thanks to all.

 The hard solution is to modify linuxthreads, possibly by
 implementing _pthread_mutex_init_calloc_cb(), in order to avoid
 recursion during initialization of malloc's internal mutexes.
 
 Jason
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 
 


-- 
Regards,
Eric




signature.asc
Description: OpenPGP digital signature

Re: freebsd port: apcupsd-3.14.3_1

[Eric Zimmerman]

Robert Huff wrote:

Mike Stammer writes:


 Last night i installed apcupsd and there was a post install message
 mentioning to comment out the following in the kernel:
 
 device  uhid# Human Interface Devices
 
 i do not think this is necessary anymore as I, in the process of

 determining my first UPS was bad, tried a kernel both with and without
 the line above commented out.
 
 I now have apcupsd running with the line above uncommented in my

 kernel after exchanging my UPS for another one.
 
 The model UPS I am using is an APC BX900.
 
 Can the post install message be altered to remove the recommendation

 to comment out the device shown above?


_If_ this is true (not doubting, just saying it's a significant
change and needs to be thoroughly tested), the APCUPSD authors need
to know so they can make the change in the souce.



According to the author's web page, found here:

http://www.apcupsd.com/manual/Building_Installing_apcupsd.html#FreeBSD

says:

This port is complete and is being used by several users

I think they already have changed things to allow it to work.

I also found this page:

http://www.freebsddiary.org/apcupsd.php

which states:

FreeBSD specific issues

At the time of writing, there was a list of FreeBSD kernel configuration 
issues. These are no longer required. apcupsd now works with a GENERIC 
kernel on FreeBSD 6.1; there is no longer a need to disable uhid or 
enable egen. As well, the FreeBSD kernel panics if USB cable is 
unplugged while apcupsd is running.


In short, apcupsd works out of the box, with the correct configuration 
items.



I cannot comment on the kernel panics when unplugging the UPS as i 
haven't tested that, but everything else works without tweaking anything 
as mentioned in the post install file in the kernel (which is a good 
thing!).  Everything else in the post install msg, including setting 
UPSTYPE usb and setting DEVICE blank works as expected.


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

Re: freebsd port: apcupsd-3.14.3_1

[Eric Zimmerman]

Jeffrey Goldberg wrote:

On Apr 30, 2008, at 10:31 AM, Mike Stammer wrote:


Last night i installed apcupsd and there was a post install message
mentioning to comment out the following in the kernel:

device  uhid# Human Interface Devices

i do not think this is necessary anymore as I, in the process of
determining my first UPS was bad, tried a kernel both with and without
the line above commented out.


Are you connecting to the UPS by USB or by old-fashioned serial 
(RS-232)?  I suspect that that message would only apply for RS-232 
connections.


But that is just a guess on my part.



I used a USB cable as supplied by APC.

I do have several machines at remote sites that use RS-232 cables and 
the line above is not commented out of the kernel. They work as expected.


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

Trouble building guile 1.8.4 (segfault in gen-scmconfig)

[Eric Schuele]

Hello,

I'm having little luck building guile 1.8.4 on 7.0-STABLE.  Been failing
for some time.  I've sat quietly for a bit thinking someone might
mention/fix it but I've seen no activity.  So I thought I'd mention it.

Here is what I'm seeing:
cc -O2 -fno-strict-aliasing -pipe -march=pentium4 -Wall
-Wmissing-prototypes -Werror -o gen-scmconfig gen-scmconfig.o
-L/usr/local/lib -llthread /usr/local/lib/libgmp.so -lcrypt -lm
/usr/local/lib/libltdl.so   -Wl,--rpath -Wl,/usr/local/lib -Wl,--rpath
-Wl,/usr/local/lib
rm -f scmconfig.h.tmp
cat ./scmconfig.h.top  scmconfig.h.tmp
./gen-scmconfig  scmconfig.h.tmp
Segmentation fault (core dumped)
gmake[2]: *** [scmconfig.h] Error 139
gmake[2]: Leaving directory
`/usr/ports/lang/guile/work/guile-1.8.4/libguile'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/lang/guile/work/guile-1.8.4'
gmake: *** [all] Error 2
*** Error code 2

I then built with debug and get a bt of gen-scmconfig like so:
#0  0x2804d179 in _rtld_error () from /libexec/ld-elf.so.1
#1  0x2804b4c4 in ___tls_get_addr () from /libexec/ld-elf.so.1
#2  0x28168152 in malloc () from /lib/libc.so.7
#3  0x28089658 in _pthread_mutex_destroy () from
/usr/local/lib/liblthread.so.6
#4  0x28089702 in _pthread_mutex_trylock () from
/usr/local/lib/liblthread.so.6
#5  0x28168194 in malloc () from /lib/libc.so.7
#6  0x28089658 in _pthread_mutex_destroy () from
/usr/local/lib/liblthread.so.6
#7  0x28089702 in _pthread_mutex_trylock () from
/usr/local/lib/liblthread.so.6
#8  0x28168194 in malloc () from /lib/libc.so.7
#9  0x28089658 in _pthread_mutex_destroy () from
/usr/local/lib/liblthread.so.6
#10 0x28089702 in _pthread_mutex_trylock () from
/usr/local/lib/liblthread.so.6
#11 0x28168194 in malloc () from /lib/libc.so.7

[snip]

#96 0x28089658 in _pthread_mutex_destroy () from
/usr/local/lib/liblthread.so.6
#97 0x28089702 in _pthread_mutex_trylock () from
/usr/local/lib/liblthread.so.6
#98 0x28168194 in malloc () from /lib/libc.so.7
#99 0x28089658 in _pthread_mutex_destroy () from
/usr/local/lib/liblthread.so.6
#100 0x28089702 in _pthread_mutex_trylock ()
   from /usr/local/lib/liblthread.so.6
#101 0x28168194 in malloc () from /lib/libc.so.7
#102 0x28089658 in _pthread_mutex_destroy ()
   from /usr/local/lib/liblthread.so.6
#103 0x28089702 in _pthread_mutex_trylock ()
   from /usr/local/lib/liblthread.so.6
#104 0x28168194 in malloc () from /lib/libc.so.7
#105 0x28089658 in _pthread_mutex_destroy ()
   from /usr/local/lib/liblthread.so.6
#106 0x28089702 in _pthread_mutex_trylock ()
   from /usr/local/lib/liblthread.so.6
.
#1 I stopped bothering to scroll.

Anyone else seeing this?  Thoughts?

Thanks in advance.

-- 
Regards,
Eric




signature.asc
Description: OpenPGP digital signature

Re: [Boinc_opt] FreeBSD Port: boinc-setiathome-enhanced-5.27_2

[Eric J Korpela]

Yes, try putting an #include cmath at the top of
analyzeFuncs_fpu.cpp.  If that works, I will make the change in our
source.

Eric

On Jan 29, 2008 1:30 AM, Rene Ladan [EMAIL PROTECTED] wrote:
 2008/1/29, alex [EMAIL PROTECTED]:
  Rene Ladan wrote:
  
   I guess I need to add   USE_GCC=4.2+  in the Makefile, since FreeBSD
   6.3 still uses GCC 3.4.6, while FreeBSD 7+ use GCC 4.2.
  
   Could you try that?  I only have a 7.0 box...
  
   Thanks,
   Rene
  
  Ok,
 
  I tried again. I added gcc 4.2 and used a compiler override
 
  [EMAIL PROTECTED] /usr/ports/astro/boinc-setiathome-enhanced]# env
  |grep CC
  CC=/usr/local/bin/gcc42
  [EMAIL PROTECTED] /usr/ports/astro/boinc-setiathome-enhanced]# env
  |grep CXX
  CXX=/usr/local/bin/g++42
 
  [EMAIL PROTECTED] /usr/ports/astro/boinc-setiathome-enhanced]# $CC
  --version
  gcc42 (GCC) 4.2.3 20071024 (prerelease)
  Copyright (C) 2007 Free Software Foundation, Inc.
 
  /usr/local/bin/g++42 -DHAVE_CONFIG_H -I. -I..  -O2 -fno-strict-aliasing

  -pipe  -mfpmath=387 -I/usr/local/include -funroll-loops -ffast-math -O3
  -I/usr/include -I/usr/include/openssl  -fPIC -DPIC -DHAVE_CONFIG_H  -O2
  -fno-strict-aliasing -pipe  -mfpmath=387 -I/usr/local/include
  -funroll-loops -ffast-math -O3 -I/usr/include -I/usr/include/openssl
  -DHAVE_CONFIG_H -DTEXT_UI -DNDEBUG -DCLIENT -I../db
  -I/usr/local/include/BOINC -I/usr/local -I/usr/local/api
  -I/usr/local/lib -I/usr/local/sched -I/usr/local/db -D_THREAD_SAFE
  -pthread   -O2 -fno-strict-aliasing -pipe -mfpmath=387
  -I/usr/local/include -funroll-loops -ffast-math -O3 -O2
  -fno-strict-aliasing -pipe  -mfpmath=387 -I/usr/local/include
  -funroll-loops -ffast-math -O3 -I/usr/include -I/usr/include/openssl -MT
  seti_boinc-analyzeFuncs_fpu.o -MD -MP -MF
  .deps/seti_boinc-analyzeFuncs_fpu.Tpo -c -o
  seti_boinc-analyzeFuncs_fpu.o `test -f 'vector/analyzeFuncs_fpu.cpp' ||
  echo './'`vector/analyzeFuncs_fpu.cpp
  vector/analyzeFuncs_fpu.cpp: In function 'int fpu_ChirpData(float
  (*)[2], float (*)[2], int, double, int, double)':
  vector/analyzeFuncs_fpu.cpp:171: error: 'floor' was not declared in this
  scope
  gmake[2]: *** [seti_boinc-analyzeFuncs_fpu.o] Error 1
  gmake[2]: Leaving directory
  `/usr/ports/astro/boinc-setiathome-enhanced/work/boinc-setiathome-enhanced-5.27/client'
  gmake[1]: *** [all-recursive] Error 1
  gmake[1]: Leaving directory
  `/usr/ports/astro/boinc-setiathome-enhanced/work/boinc-setiathome-enhanced-5.27'
  gmake: *** [all] Error 2
  *** Error code 2
 
  Any more ideas? :)
 
 Hmm, floor(3) is part of libm / math.h here...

 %gcc -v
 Using built-in specs.
 Target: i386-undermydesk-freebsd
 Configured with: FreeBSD/i386 system compiler
 Thread model: posix
 gcc version 4.2.1 20070719  [FreeBSD]

 What happens if you comment out CPUTYPE from /etc/make.conf ? (if it is 
 defined,
 CPUTYPE=prescott works for me)


 Thanks,
 Rene
 --
 GPG fingerprint = E738 5471 D185 7013 0EE0  4FC8 3C1D 6F83 12E1 84F6
 (subkeys.pgp.net)

 It won't fit on the line.
 -- me, 2001
 ___
 boinc_opt mailing list
 [EMAIL PROTECTED]
 http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_opt

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

Re: Encountered a problem with GNOME gdm

[Eric L. Chen]

Hi,
I think use /usr/bin/env bash is better than /usr/local/bin/bash in
portability.

/Eric
On Sat, 2008-01-19 at 02:23 +0530, आशीष शुक्ल Ashish Shukla wrote:
 Hi,
 
 I encountered a problem with gdm. The file
 /usr/local/etc/gdm/Xsession needs /usr/local/bin/bash for its
 execution, whereas /bin/sh  is specified. Following is the patch
 which will fix this problem. Is this already reported as PR, hmm...?
 
 8-8-
 --- /usr/local/etc/gdm/Xsession~2008-01-17 01:17:04.0 +0530
 +++ /usr/local/etc/gdm/Xsession 2008-01-18 23:55:39.0 +0530
 @@ -1,4 +1,4 @@
 -#!/bin/sh
 +#!/usr/local/bin/bash
  #
  # This is SORT OF LIKE an X session, but not quite.  You get a command as the
  # first argument (it could be multiple words, so run it with eval).  As a
 8-8-
 
 TIA
 ___
 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: pkg_delete: package 'xorg-drivers-7.3' doesn't have a prefix

[Eric Crist]

On Dec 28, 2007, at 12:47 PM, Stephen Montgomery-Smith wrote:


Mon Si wrote:

Dear list,
I'm experiencing problems when I try to portupgrade the xorg-driver
port. The old version of the port can't be uninstalled during the
portupgrade due to an undefined prefix.
The port can't be deleted by pkg_delete -f xorg-drivers-7.3
Does anybody know how to upgrade / remove this port?
Thanks in advance,
Simon


If nothing else works, you could try
rm -rf /var/db/pkg/xorg-drivers-7.3


If I remember correctly, there are detailed instructions in /usr/ports/ 
UPDATING -- go back to notes for sometime in May of 2007, and there's  
a really long entry on upgraded to Xorg 7.x from 6.9.  I think the  
entry specifically mentions 7.2, but it should work for 7.3 as well.


HTH
-
Eric F Crist
Secure Computing Networks


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

Xephyr on freebsd...

[Eric Schuele]

Hello,

I was wondering if there is a port (that I can't seem to find), or one
in the making of Xephyr (Xnest next generation?).

If not... has anyone tried and had any luck with grabbing the sources
from git and building it?  Care to comment on pitfalls?

-- 
Regards,
Eric




signature.asc
Description: OpenPGP digital signature

Re: Port comparison failed

[Eric]

Doug Barton wrote:

On Wed, 19 Sep 2007, Eric wrote:


Anyone have a way to fix this:

snip portsnap output
Building new INDEX files... done.
portconf-1.2!   Comparison failed
portmaster-1.9  !   Comparison failed


Version 1.9 is really old, we're up to version 1.20 now. Are you sure 
your port tree is up to date?



it happens when i run portsnap and then get new ports via:

pkg_version -v | grep \


I can't think of any reason that wouldn't work, which leads me to 
believe that you've got bigger issues lurking somewhere.


i tried uninstalling and then reinstalling the ports above but it 
didnt fix the issue.


I assume that after you reinstalled portmaster that you had version 1.20?

I use portmaster to update ports. I do not have any other port 
management tool installed.


Before I wrote the -L feature for portmaster, I used to use 'pkg_version 
-v -L=' as an alias to find out what needed rebuilding. Assuming you're 
using version 1.20 of portmaster, you might want to check the man page 
and try the -L option to see if portmaster can find the problem.


hth,

Doug



somehow i had /var/db/pkg entries for 1.9 and 1.20. I deleted the 1.9. 
thanks for the info. things seem to look good now


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

Port comparison failed

[Eric]

Anyone have a way to fix this:

snip portsnap output
Building new INDEX files... done.
portconf-1.2!   Comparison failed
portmaster-1.9  !   Comparison failed

it happens when i run portsnap and then get new ports via:

pkg_version -v | grep \

i tried uninstalling and then reinstalling the ports above but it didnt 
fix the issue.


I use portmaster to update ports. I do not have any other port 
management tool installed.


Thanks!

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

Re: [Boinc_opt] setiathome-enhanced 5.27 : configure step unreliable?

[Eric J Korpela]

I just checked the diffs.  It is the removal of the processor specific
flags that broke the build.

In addition, it's probably more compatible with future builds to
specify the --disable-server --disable-graphics command line options
on the configure command line rather than to edit the Makefile.am

Regards,

Eric

On 8/30/07, Eric J Korpela [EMAIL PROTECTED] wrote:
 Hi Rene,

 Just getting back from vacation, so am just seeing this now.

 The major issue seems to be with the vectorized stuff.  If you look at
 the file client/Makefile.am, you will see some specific compile
 options for different files.  For example, analyzeFuncs_sse.cpp needs
 to be compiled with the GCC -msse flag which defines certain macros to
 allow SSE to be used.  If -msse is not used, the build fails in the
 manner you've shown.

 I suspect when you removed the cpu specific compiler (-m) options you
 broke the build.
 [EMAIL PROTECTED] checks which processor the application is running on and
 avoids incompatible code.   In other words the application is generic
 even though it contains processor specific code.  But in order to
 compile, the processor specific code needs the appropriate processor
 specific compiler flags.

 Eric




 On 8/29/07, Rene Ladan [EMAIL PROTECTED] wrote:
  Hi,
 
  I've updated the FreeBSD port of setiathome-enhanced to 5.27 and it also
  has been committed to the ports tree.  However there seems to be a problem
  with the generated configure, it does not properly detect xmmintrin.h on
  some systems even when present (it is located in /usr/include).  The
  strange thing is that the file _does_ get detected on my box:
 
  FreeBSD 7.0-CURRENT i386, 2007-08-20
 
  The resulting application even produces valid results :) :
  http://setiathome.berkeley.edu/results.php?userid=211311
  (look for computer 2960826, the other one is a Windows XP box at work)
 
  Some failure reports from users are at:
 
  http://head.miwibox.org/tb/index.php?action=describe_portid=1806
  http://amd64.miwibox.org/tb/index.php?action=describe_port%26id=1245
  and
  http://home.tiscali.nl/rladan/freebsd/sah/config_make.log.gz
(uploaded, sent per private email)
 
  When originally designing the port, I've chosen to slightly modify the build
  infrastructure to:
  * match the FreeBSD BOINC port,
  * remove some unnecessary/unuseable stuff (server, graphics)
  * take some FreeBSD-only shortcuts,
  * remove some polluting -mCPU_SPECIFIC compiler options, they are set in the
port Makefile instead to keep the source more CPU-independent.
  I've not changed anything else.  The recipe to create the FreeBSD source
  tarball from the setiathome_enhanced-client-cvs-2007-08-08.tar.gz tarball
  is at:
 
  http://home.tiscali.nl/rladan/freebsd/sah/seti-recipe.sh
  http://home.tiscali.nl/rladan/freebsd/sah/patches.diff
   (referenced by the .sh file)
 
  The recipe recreates the configure and Makefile.in files, I've used the
  following tools for this as installed by the devel/autotools port:
  * aclocal 1.10
  * autoheader 2.61
  * autoconf 2.61
  * automake 1.10
 
  Can someone shed a light on it?  I don't see anything obviously wrong 
  myself.
 
  Regards,
  Rene
  --
  GPG fingerprint = E738 5471 D185 7013 0EE0  4FC8 3C1D 6F83 12E1 84F6 
  (subkeys.pgp.net)
 
  It won't fit on the line.
  -- me, 2001
 
  ___
  boinc_opt mailing list
  [EMAIL PROTECTED]
  http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_opt
 

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

Re: [Boinc_opt] setiathome-enhanced 5.27 : configure step unreliable?

[Eric J Korpela]

Hi Rene,

Just getting back from vacation, so am just seeing this now.

The major issue seems to be with the vectorized stuff.  If you look at
the file client/Makefile.am, you will see some specific compile
options for different files.  For example, analyzeFuncs_sse.cpp needs
to be compiled with the GCC -msse flag which defines certain macros to
allow SSE to be used.  If -msse is not used, the build fails in the
manner you've shown.

I suspect when you removed the cpu specific compiler (-m) options you
broke the build.
[EMAIL PROTECTED] checks which processor the application is running on and
avoids incompatible code.   In other words the application is generic
even though it contains processor specific code.  But in order to
compile, the processor specific code needs the appropriate processor
specific compiler flags.

Eric




On 8/29/07, Rene Ladan [EMAIL PROTECTED] wrote:
 Hi,

 I've updated the FreeBSD port of setiathome-enhanced to 5.27 and it also
 has been committed to the ports tree.  However there seems to be a problem
 with the generated configure, it does not properly detect xmmintrin.h on
 some systems even when present (it is located in /usr/include).  The
 strange thing is that the file _does_ get detected on my box:

 FreeBSD 7.0-CURRENT i386, 2007-08-20

 The resulting application even produces valid results :) :
 http://setiathome.berkeley.edu/results.php?userid=211311
 (look for computer 2960826, the other one is a Windows XP box at work)

 Some failure reports from users are at:

 http://head.miwibox.org/tb/index.php?action=describe_portid=1806
 http://amd64.miwibox.org/tb/index.php?action=describe_port%26id=1245
 and
 http://home.tiscali.nl/rladan/freebsd/sah/config_make.log.gz
   (uploaded, sent per private email)

 When originally designing the port, I've chosen to slightly modify the build
 infrastructure to:
 * match the FreeBSD BOINC port,
 * remove some unnecessary/unuseable stuff (server, graphics)
 * take some FreeBSD-only shortcuts,
 * remove some polluting -mCPU_SPECIFIC compiler options, they are set in the
   port Makefile instead to keep the source more CPU-independent.
 I've not changed anything else.  The recipe to create the FreeBSD source
 tarball from the setiathome_enhanced-client-cvs-2007-08-08.tar.gz tarball
 is at:

 http://home.tiscali.nl/rladan/freebsd/sah/seti-recipe.sh
 http://home.tiscali.nl/rladan/freebsd/sah/patches.diff
  (referenced by the .sh file)

 The recipe recreates the configure and Makefile.in files, I've used the
 following tools for this as installed by the devel/autotools port:
 * aclocal 1.10
 * autoheader 2.61
 * autoconf 2.61
 * automake 1.10

 Can someone shed a light on it?  I don't see anything obviously wrong myself.

 Regards,
 Rene
 --
 GPG fingerprint = E738 5471 D185 7013 0EE0  4FC8 3C1D 6F83 12E1 84F6 
 (subkeys.pgp.net)

 It won't fit on the line.
 -- me, 2001

 ___
 boinc_opt mailing list
 [EMAIL PROTECTED]
 http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_opt

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

Re: Stupid question

[Eric]

Pablo Murillo wrote:

Hello

My name is Pablo, I'm from Argentina, I'm new on FreeBSD, and I have a 
very stupid question about ports
How can I re-make a port and change the options selected the first 
time I make the port ?
For example, I make the port for assp (/usr/ports/mail/assp) and I don't 
have MySQL installed, and I hit Enter to quickly (sorry), and now, I 
can't get the options screen again.




try

make config

from your port directory and you will be back in business!

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

Re: mail/horde

[Eric]

Beech Rintoul wrote:

On Wednesday 01 August 2007, Andrew Pantyukhin said:

Good luck  with your install and feel free to ask any specific 
questions you may have.


Beech - Horde Maintainer



on a somewhat related note, any idea when we will see DIMP get put into 
the ports tree? it looks nice


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

Re: FreeBSD Port: nxserver-1.4.0_1

[Eric Masson]

Robert Gilaard [EMAIL PROTECTED] writes:

Hi,

 I've noticed that nomachine has updated their freenx packages for
 different distributions. Now they even have amd64 native packages and I
 was wondering if that means we will see the amd64 version in freebsd
 anytime soon.

A port of 2.1.0 libs and freenx 0.6.0 is available here :
http://www.deweyonline.com/nx/freebsd.html

There's an ongoing work on 3.0 libs (search [EMAIL PROTECTED]
archives), freenx 0.7.0 has been released.

The FreeNX project will go under a complete rewrite soon, like explained
in the announce of the 0.7.0 release :

[EMAIL PROTECTED]
Okay, now we come to a section, which should answer all open questions:

- When will the next version be released? FreeNX development is so
unstable and unreliable. It almost feels like releases are done based on
mood.

The next version will be released in ~ 3 months if there is something to
release ( and there sure will be something ;-)).

That means we change to a time based release schedule now after a talk by 
Martin Michlmayr, former debian project leader, did convince me.

Next release date: 2007-10-10

I'm really really sorry for any inconvenience that not released, but 
tagged and not released even though there were critical bugs versions 
did cause you.

I know that there something did go terribly wrong from 2005-2006 and again
in 2006. And now the long delay for 0.7.0 again and still no new bugs 
fixed that occurred in my Question for Bugfixes thread.

I have made many many mistakes in the past and I'm sorry for that.

I think and hope a time based release schedule will fix at least all of 
_those_ issues.

- Why the fourth redesign? Won't this introduce many new bugs? Won't it
make the software not really unstable again? Shouldn't the software be
fixed instead of writing new things and introducing lots and lots of more
features.

First of all:

FreeNX was rapid prototyping, from a one night hack to what you have now.

There is one rule in prototype development: Throw the prototype away.

When I first learned that rule in university, I did not understand it.

But now that I see that the current code base gets more and more messy
and bugs cannot be really fixed and new bugs keep popping up and old
bugs get discussed on the ML again and again ...

... I am sick of it. With NX 3.0.0 it is necessary to do a redesign
anyway, so I decided to DESIGN it from scratch.

I'll take over some parts of the old code, but it'll be actually
DESIGNED and not just thrown together.

And for example that nx@ login will be optional from the start on so
finally our open source clients will be able to login directly and all
those SSH issues will at least with our clients be no longer an issue
and you can use public keys, smart cards, whatever to actually do the
login ...

( And if you need to use the commercial client, you can hack a modified
nxssh in. )

See also next question:

- Do you stick with bash or do you switch to some scripting language like 
python, perl, ruby, whatever ?

I'll stick with whatever is appropriate for the task.

As I know bash best, I'll stick with it for most parts, but there will be
also some parts written in C.

And the version will be so modular, that the language really does not 
matter anymore.

Btw. I have mostly heard:

Oh, wow its bash, it was easy to fix for me. And not: I don't know that 
language unfortunately.

So it is a good choice? I dunno.

I'll now try to keep all components really, really simple, so that they 
are not using any advanced things no one understands on first sight, but 
easily changeable and customizable.

The problems that freenx nxnode was not as stable and error free as !M 
nxnode were two:

- I first hacked it together and it has grown out of a 1 night hack
- I did not look at the actually source components how things are done, 
but just looked at client / server protocol. So I did write code without 
really understanding it.
- There had been some bad design issues, which had proven really hard to 
fix and which had lead to hard to trace race conditions after race 
condition.
- I did not actually design or think about it, but just looked at what !M 
did and tried to do the same as best as I could.

That is why I am now doing a re-design and I disagree that this is the 
fourth attempt. I had changed some major things in nxnode and nxserver 
before, but it was all still only code-change not code-rewrite.

The goals of the new design are:

- flexible and customizable, so that new developers can join easily.
- stable and not feature creep, so that features are not affecting the
  core functionality

While the features are incorporated into the design, they have the lowest 
priority in implementation.

- What will the redesign be based on? NX 3.0.0?

The redesign will be based on a stable fork() of NX 3.0.0:

Leopold did convice me now that slh is and always has been right. Sorry, 
for any misunderstanding in the past?

We need to have our own version of the NX 

Re: experimental qemu-devel port update, please test!

[Eric Anderson]

On 07/13/07 15:46, Juergen Lock wrote:

On Thu, Jul 12, 2007 at 01:07:50PM -0500, Craig Boston wrote:

On Thu, Jul 12, 2007 at 12:52:52PM -0500, Craig Boston wrote:

For some reason when the ioctl is issued, curproc points to a totally
bogus proc structure.  curthread seems to be sane as far as I can tell,
but the process it claims to belong to is full of junk.

Aha!  The problem isn't that curproc is garbage, but rather that it's
being interpreted wrong.

struct proc has some extra fields when KSE is #defined.  KSE recently
became a kernel option and was put in the DEFAULTS file, so everyone's
kernel has it defined.  But kqemu is being compiled without it.

I compiled with -DKSE and now kqemu works!


Aaah-haah!  Thanks for catching this one! :)


This seems like it would be a common problem for modules compiled
outside the kernel tree.  Is there an established way to get the
standard configuration options?


 Good q...


I'm thinking also about other options like SMP, that for instance
changes the way mutexes work.

Craig


 Okay what do you guys think about the following patch for now:
(the SMP thing might actually be the cause for ports/113430, can
someone verify?)



The patch applies cleanly, and it builds.  It also *WORKS*! :)

I can't say anything about that PR though.

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

Clamav CPU race

[Eric Frazier]

I have found a few bits and pieces about Clamav and various race/ 
denial of service issues with FreeBSD and Linux, some of which were  
related to certain types of files being scanned, some related to  
thread safety issues. What I am wondering is with 6.2 is there now a  
definitive solution in place to prevent races, or is this still  
something in process?


I did find this thread which looks very much like my issue.

http://www.nabble.com/Re%3A-Clamav-90_2-Lockup-with-freebsd-6.2-%28fwd 
%29-tf3349158.html

also
http://tinyurl.com/2g3dk4

But this left off with 0.90.2 and was fixed in ports,  however I am  
having a problem very much like this CPU race with 6.2 and 0.90.3 
(installed from ports) I have not yet been able to reproduce the  
error, but it does seem to correspond with the higher load we get  
between 12 and 2AM when various reports come into our mail server.


Of course I would be glad to help debug this if anyone has  
suggestions, right now I am going to try to reproduce the error with  
a script sending lots of attachments and go from there.



I am not entirely sure if this kind of question is considered on  
topic, so I apologize if I guessed wrong..


Thanks,

Eric




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

Re: experimental qemu-devel port update, please test!

[Eric Anderson]

Craig Boston wrote:

On Thu, Jul 12, 2007 at 12:52:52PM -0500, Craig Boston wrote:

For some reason when the ioctl is issued, curproc points to a totally
bogus proc structure.  curthread seems to be sane as far as I can tell,
but the process it claims to belong to is full of junk.


Aha!  The problem isn't that curproc is garbage, but rather that it's
being interpreted wrong.

struct proc has some extra fields when KSE is #defined.  KSE recently
became a kernel option and was put in the DEFAULTS file, so everyone's
kernel has it defined.  But kqemu is being compiled without it.

I compiled with -DKSE and now kqemu works!

This seems like it would be a common problem for modules compiled
outside the kernel tree.  Is there an established way to get the
standard configuration options?

I'm thinking also about other options like SMP, that for instance
changes the way mutexes work.



Great work!  Thanks for chugging on it..

Do you think this could affect nvidia kernel modules?  I think there was 
an alternate thread about nvidia modules causing systems to panic/lock up.


Eric



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

Re: experimental qemu-devel port update, please test!

[Eric Anderson]

Juergen Lock wrote:

On Sun, Jul 08, 2007 at 01:15:35PM -0500, Eric Anderson wrote:

On 07/07/07 09:02, Juergen Lock wrote:

In article [EMAIL PROTECTED] you write:

On 07/05/07 22:31, Eric Anderson wrote:



[...]
Although now I have the issue where using kqemu-kmod causes my system to 
reboot or power off.  :(


Any ideas?

This seems to be a -current issue, it doesn't happen for me at least
(6.2 and previously also 6.1.)  You could check if it is dependent
on the version of the used qemu (the 0.9.0 port, the version of
qemu-devel in ports, or the not-yet-committed updated I posted),
but I doubt it.  What may help is finding out which commit to -current
started kqemu to break (find an older version that worked, then
binary-search), or at least a backtrace from a kernel compiled
without -fomit-frame-pointer (putting DDB in the config seems to do
that for amd64 at least, but rebuild the entire kernel.)  There also
is an open issue for kqemu on amd64 smp,
http://www.freebsd.org/cgi/query-pr.cgi?pr=113430
dunno if its related...
Juergen


My host is i386, SMP, and it also happens with the current qemu-devel port. 
 It must have been something in -CURRENT that changed, probably since 
May15th-ish.  I can't do a binary search anytime soon to find it.  In the 
past, I've recompiled kqemu and that has done the trick.  I have all the 
debugging built in, but that doesn't stop the system from rebooting or 
powering off.


Hmm an UP kernel might be worth a try too...

Juergen



Hmm - with and without UP, I get a panic, but I managed to catch a panic 
in _vm_map_lock, something like:


_vm_map_lock()
vm_map_wire()
kqemu_lock_user_page()
mon_user_map()


I'll try to get a real bt..

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

Re: experimental qemu-devel port update, please test!

[Eric Anderson]

On 07/09/07 08:00, Eric Anderson wrote:

Juergen Lock wrote:

On Sun, Jul 08, 2007 at 01:15:35PM -0500, Eric Anderson wrote:

On 07/07/07 09:02, Juergen Lock wrote:

In article [EMAIL PROTECTED] you write:

On 07/05/07 22:31, Eric Anderson wrote:
[...]
Although now I have the issue where using kqemu-kmod causes my system to 
reboot or power off.  :(


Any ideas?

This seems to be a -current issue, it doesn't happen for me at least
(6.2 and previously also 6.1.)  You could check if it is dependent
on the version of the used qemu (the 0.9.0 port, the version of
qemu-devel in ports, or the not-yet-committed updated I posted),
but I doubt it.  What may help is finding out which commit to -current
started kqemu to break (find an older version that worked, then
binary-search), or at least a backtrace from a kernel compiled
without -fomit-frame-pointer (putting DDB in the config seems to do
that for amd64 at least, but rebuild the entire kernel.)  There also
is an open issue for kqemu on amd64 smp,
http://www.freebsd.org/cgi/query-pr.cgi?pr=113430
dunno if its related...
Juergen
My host is i386, SMP, and it also happens with the current qemu-devel port. 
 It must have been something in -CURRENT that changed, probably since 
May15th-ish.  I can't do a binary search anytime soon to find it.  In the 
past, I've recompiled kqemu and that has done the trick.  I have all the 
debugging built in, but that doesn't stop the system from rebooting or 
powering off.

Hmm an UP kernel might be worth a try too...

Juergen



Hmm - with and without UP, I get a panic, but I managed to catch a panic 
in _vm_map_lock, something like:


_vm_map_lock()
vm_map_wire()
kqemu_lock_user_page()
mon_user_map()


I'll try to get a real bt..

Eric


Hmm - I suspect this commit or something near it is the issue:

http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/vm/vm_map.c.diff?r1=1.384;r2=1.385;sortby=date;f=h;f=u

Or the 1.384 - 1.385 change by attilio@ (cc'ed).


Eric







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

FreeBSD Port: lzma-4.48

[Eric Kingston]

There is a bug in LZMA running on amd64.  LZMA, an archiver port,
segmentation faults on files  1-5 GB in size.  I've tested this on three
different xeon dual multi-core processor servers.  In each case, lzma core
dumps in the exact same spot and the resulting file size for each is exactly
the same.  Files less than 1 GB seem to work ok.  LZMA seems to work on any
size file without a problem on the FreeBSD i386 platform.  When I spoke with
a friend of mine, he says that he compresses 160GB files daily without a
problem, on his i386 systems.

 

Eric,

 

[EMAIL PROTECTED]

 

 

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

FreeBSD Port: lzma-4.48

[Eric Kingston]

There is a bug in LZMA running on amd64.  LZMA, an archiver port,
segmentation faults on files  1-5 GB in size.  I've tested this on three
different xeon dual multi-core processor servers.  In each case, lzma core
dumps in the exact same spot and the resulting file size for each is exactly
the same.  Files less than 1 GB seem to work ok.  LZMA seems to work on any
size file without a problem on the FreeBSD i386 platform.  When I spoke with
a friend of mine, he says that he compresses 160GB files daily without a
problem, on his i386 systems.

 

Eric,

 

[EMAIL PROTECTED]

 

 

P.S.  Here is my machine info..

FreeBSD elrond.esreco.net 6.2-RELEASE-p5 FreeBSD 6.2-RELEASE-p5 #0: Sun Jun
17 13:37:57 MDT 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ELROND  amd64

 

 

 

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

Re: experimental qemu-devel port update, please test!

[Eric Anderson]

On 07/05/07 22:31, Eric Anderson wrote:

On 07/02/07 15:30, Juergen Lock wrote:

Looks like its time for this again...  Many bugs have been fixed,
some features have been added, like, qemu-system-arm has grown
emulation of a few PDAs like some Zaurus models, etc.  As always,
please test now, before I commit this, so we won't be in for
nasty surprises afterwards...


Works great so far on -CURRENT, thanks!

Did the vmwarevga thing ever settle down, and become stable?




Although now I have the issue where using kqemu-kmod causes my system to 
reboot or power off.  :(


Any ideas?


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

Re: experimental qemu-devel port update, please test!

[Eric Anderson]

On 07/02/07 15:30, Juergen Lock wrote:

Looks like its time for this again...  Many bugs have been fixed,
some features have been added, like, qemu-system-arm has grown
emulation of a few PDAs like some Zaurus models, etc.  As always,
please test now, before I commit this, so we won't be in for
nasty surprises afterwards...


Works great so far on -CURRENT, thanks!

Did the vmwarevga thing ever settle down, and become stable?

Eric

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

Re: FreeBSD Port: R-2.4.1_1

[Eric van Gyzen]

Rong-en Fan wrote:
 On 5/30/07, Wiebe Pestman [EMAIL PROTECTED] wrote:
 Hallo Eric,
 Could you give an indication when R is going to be upgraded to R-2.5.0
 in the
 FreeBSD ports collection?
 Best regards,
 Wiebe Pestman
 
 There is a PR 112713 pending Eric's approval.
 The patch at
 
 http://people.freebsd.org/~rafan/R-2.5.0.diff
 
 is ready to commit. If Eric is busy, then I will update
 this port tomorrow.
 
 Regards,
 Rong-En Fan

I haven't had time to look at it.  Rong-En, perhaps you
should go ahead and update the port.

Thanks for your work!

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

Re: FreeBSD Port: R-2.5.0

[Eric van Gyzen]

Joey Mingrone wrote:
 Hi Eric,
 
 I sent you a message a while back about some linking errors when
 upgrading to R-2.4.1.  I don't recall changing anything, but it
 installed after updating my ports tree a few days later.  I'm having
 the same problems upgrading to 2.5.0.  The linking error is below.
 Any suggestions? *Note*, there are no linking errors when running the
 erroneous command below with gfortran.
 
 Thanks,
 
 Joey
 
 ...
 ...
 cc -std=gnu99 -export-dynamic -L/usr/local/lib -o R.bin Rmain.o -L../../lib 
 -lR
 /usr/local/lib/gcc-4.2.1/libgfortran.so.2: undefined reference to
 [EMAIL PROTECTED]'
 /usr/local/lib/gcc-4.2.1/libgfortran.so.2: undefined reference to
 [EMAIL PROTECTED]'
 /usr/local/lib/gcc-4.2.1/libgfortran.so.2: undefined reference to
 [EMAIL PROTECTED]'
 /usr/local/lib/gcc-4.2.1/libgfortran.so.2: undefined reference to
 [EMAIL PROTECTED]'
 /usr/local/lib/gcc-4.2.1/libgfortran.so.2: undefined reference to
 [EMAIL PROTECTED]'
 /usr/local/lib/gcc-4.2.1/libgfortran.so.2: undefined reference to
 [EMAIL PROTECTED]'

Joey,

I'm curious:  Instead of linking with gfortran, try gcc42.

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

Re: another qemu-devel port update ready for testing

[Eric Anderson]

On 05/27/07 07:58, Juergen Lock wrote:

On Sat, May 26, 2007 at 06:02:06PM -0500, Eric Anderson wrote:

On a recent -CURRENT (with the new GCC):

# make
...
===  Configuring for qemu-devel-0.9.0s.20070526
WARNING: cc looks like gcc 4.x
QEMU is known to have problems when compiled with gcc 4.x
It is recommended that you use gcc 3.x to build QEMU
To use this compiler anyway, configure with --disable-gcc-check
===  Script configure failed unexpectedly.
Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the
/usr/ports/emulators/qemu-devel/work/qemu-snapshot-2007-05-26_05/config.log
including the output of the failure of your make command. Also, it might be
a good idea to provide an overview of all packages installed on your system
(e.g. an `ls /var/db/pkg`).
*** Error code 1

Stop in /usr/ports/emulators/qemu-devel.
*** Error code 1

Stop in /usr/ports/emulators/qemu-devel.


Hmm that should not happen...  Do you have an old version of
bsd.gcc.mk maybe?

Juergen



# $FreeBSD: ports/Mk/bsd.gcc.mk,v 1.12 2007/05/19 22:06:14 pav Exp $


That the right one?

Eric

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

Re: another qemu-devel port update ready for testing

[Eric Anderson]

On 05/27/07 13:52, Juergen Lock wrote:

On Sun, May 27, 2007 at 12:32:18PM -0500, Eric Anderson wrote:

On 05/27/07 07:58, Juergen Lock wrote:

On Sat, May 26, 2007 at 06:02:06PM -0500, Eric Anderson wrote:

On a recent -CURRENT (with the new GCC):

# make
...
===  Configuring for qemu-devel-0.9.0s.20070526
WARNING: cc looks like gcc 4.x
QEMU is known to have problems when compiled with gcc 4.x
It is recommended that you use gcc 3.x to build QEMU
To use this compiler anyway, configure with --disable-gcc-check
===  Script configure failed unexpectedly.
Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the
/usr/ports/emulators/qemu-devel/work/qemu-snapshot-2007-05-26_05/config.log
including the output of the failure of your make command. Also, it might 
be
a good idea to provide an overview of all packages installed on your 
system

(e.g. an `ls /var/db/pkg`).
*** Error code 1

Stop in /usr/ports/emulators/qemu-devel.
*** Error code 1

Stop in /usr/ports/emulators/qemu-devel.

Hmm that should not happen...  Do you have an old version of
bsd.gcc.mk maybe?

Juergen


# $FreeBSD: ports/Mk/bsd.gcc.mk,v 1.12 2007/05/19 22:06:14 pav Exp $


That the right one?


Yeah.  Ok probably CONFIGURE_ARGS needs to come after the
bsd.port.pre.mk include for it to pick up the right ${CC}...  try this:



Same thing..

===  Vulnerability check disabled, database not found
===  Found saved configuration for qemu-devel-0.9.0s.20070526
===  Extracting for qemu-devel-0.9.0s.20070526
= MD5 Checksum OK for qemu/qemu-snapshot-2007-05-26_05.tar.bz2.
= SHA256 Checksum OK for qemu/qemu-snapshot-2007-05-26_05.tar.bz2.
===   qemu-devel-0.9.0s.20070526 depends on file: 
/usr/local/bin/perl5.8.8 - found

===  Patching for qemu-devel-0.9.0s.20070526
===   qemu-devel-0.9.0s.20070526 depends on file: 
/usr/local/bin/perl5.8.8 - found

===  Applying FreeBSD patches for qemu-devel-0.9.0s.20070526
===   qemu-devel-0.9.0s.20070526 depends on package: 
kqemu-kmod=1.3.0pre5 - found
===   qemu-devel-0.9.0s.20070526 depends on executable in : texi2html - 
found

===   qemu-devel-0.9.0s.20070526 depends on executable in : gmake - found
===   qemu-devel-0.9.0s.20070526 depends on file: 
/usr/local/bin/perl5.8.8 - found
===   qemu-devel-0.9.0s.20070526 depends on file: 
/usr/local/bin/sdl-config - found

===   qemu-devel-0.9.0s.20070526 depends on shared library: SDL.11 - found
===  Configuring for qemu-devel-0.9.0s.20070526
WARNING: cc looks like gcc 4.x
QEMU is known to have problems when compiled with gcc 4.x
It is recommended that you use gcc 3.x to build QEMU
To use this compiler anyway, configure with --disable-gcc-check
===  Script configure failed unexpectedly.
Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the
/usr/ports/emulators/qemu-devel/work/qemu-snapshot-2007-05-26_05/config.log
including the output of the failure of your make command. Also, it might be
a good idea to provide an overview of all packages installed on your system
(e.g. an `ls /var/db/pkg`).
*** Error code 1

Stop in /usr/ports/emulators/qemu-devel.
*** Error code 1

Stop in /usr/ports/emulators/qemu-devel.





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

Re: another qemu-devel port update ready for testing

[Eric Anderson]

On a recent -CURRENT (with the new GCC):

# make
===  Vulnerability check disabled, database not found
===  Found saved configuration for qemu-0.9.0
= qemu-snapshot-2007-05-26_05.tar.bz2 doesn't seem to exist in 
/usr/ports/distfiles/qemu.

= Attempting to fetch from http://qemu-forum.ipi.fi/qemu-snapshots/.
qemu-snapshot-2007-05-26_05.tar.bz2   100% of 1918 kB   72 kBps 
00m00s

===  Extracting for qemu-devel-0.9.0s.20070526
= MD5 Checksum OK for qemu/qemu-snapshot-2007-05-26_05.tar.bz2.
= SHA256 Checksum OK for qemu/qemu-snapshot-2007-05-26_05.tar.bz2.
===   qemu-devel-0.9.0s.20070526 depends on file: 
/usr/local/bin/perl5.8.8 - found

===  Patching for qemu-devel-0.9.0s.20070526
===   qemu-devel-0.9.0s.20070526 depends on file: 
/usr/local/bin/perl5.8.8 - found

===  Applying FreeBSD patches for qemu-devel-0.9.0s.20070526
===   qemu-devel-0.9.0s.20070526 depends on package: 
kqemu-kmod=1.3.0pre5 - found
===   qemu-devel-0.9.0s.20070526 depends on executable in : texi2html - 
found

===   qemu-devel-0.9.0s.20070526 depends on executable in : gmake - found
===   qemu-devel-0.9.0s.20070526 depends on file: 
/usr/local/bin/perl5.8.8 - found
===   qemu-devel-0.9.0s.20070526 depends on file: 
/usr/local/bin/sdl-config - found

===   qemu-devel-0.9.0s.20070526 depends on shared library: SDL.11 - found
===  Configuring for qemu-devel-0.9.0s.20070526
WARNING: cc looks like gcc 4.x
QEMU is known to have problems when compiled with gcc 4.x
It is recommended that you use gcc 3.x to build QEMU
To use this compiler anyway, configure with --disable-gcc-check
===  Script configure failed unexpectedly.
Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the
/usr/ports/emulators/qemu-devel/work/qemu-snapshot-2007-05-26_05/config.log
including the output of the failure of your make command. Also, it might be
a good idea to provide an overview of all packages installed on your system
(e.g. an `ls /var/db/pkg`).
*** Error code 1

Stop in /usr/ports/emulators/qemu-devel.
*** Error code 1

Stop in /usr/ports/emulators/qemu-devel.



On 05/26/07 13:17, Juergen Lock wrote:

It's been a while since I last updated the qemu-devel port, and
among many arm/mips/ppc/sparc imporvements there were also vmwarevga
and some i386/amd64 bugs fixed in qemu cvs, so possibly a few more
guests run now (also i386 guests on qemu-system-x86_64, there was
an mmu emulation bug fixed that could affect those.)  I also would
like you to test existing guests that did already run correctly,
in order to catch possible regressions before I commit this update.

 Thanx, and enjoy!
Juergen

Index: Makefile
===
RCS file: /home/pcvs/ports/emulators/qemu-devel/Makefile,v
retrieving revision 1.77
diff -u -r1.77 Makefile
--- Makefile19 May 2007 20:04:37 -  1.77
+++ Makefile26 May 2007 15:29:44 -
@@ -6,8 +6,7 @@
 #
 
 PORTNAME=	qemu

-PORTVERSION=   0.9.0s.20070405
-PORTREVISION=  4
+PORTVERSION=   0.9.0s.20070526
 CATEGORIES=emulators
 MASTER_SITES=  http://qemu.org/:release \
http://qemu-forum.ipi.fi/qemu-snapshots/:snapshot \
@@ -15,7 +14,7 @@
http://www.volny.cz/xnavara/qemu/:snapshot \
http://people.brandeis.edu/~jcoiner/qemu_idedma/:idedma \
http://people.freebsd.org/~maho/qemu/:misc
-DISTNAME=  ${PORTNAME}-snapshot-2007-04-05_05
+DISTNAME=  ${PORTNAME}-snapshot-2007-05-26_05
 DISTFILES= ${DISTNAME}${EXTRACT_SUFX}:snapshot
 DIST_SUBDIR=   qemu
 EXTRACT_ONLY=  ${DISTNAME}${EXTRACT_SUFX}
Index: distinfo
===
RCS file: /home/pcvs/ports/emulators/qemu-devel/distinfo,v
retrieving revision 1.45
diff -u -r1.45 distinfo
--- distinfo7 Apr 2007 19:14:42 -   1.45
+++ distinfo26 May 2007 14:06:06 -
@@ -1,6 +1,6 @@
-MD5 (qemu/qemu-snapshot-2007-04-05_05.tar.bz2) = 
48321d0997db88f09f01d38500c52807
-SHA256 (qemu/qemu-snapshot-2007-04-05_05.tar.bz2) = 
48835ca90ced5cba2230fc95502b648167b5ca7247f885ee398ba891dbbf4c1b
-SIZE (qemu/qemu-snapshot-2007-04-05_05.tar.bz2) = 1721640
+MD5 (qemu/qemu-snapshot-2007-05-26_05.tar.bz2) = 
3fe2cf8c5cb26431499056bd08bb5be8
+SHA256 (qemu/qemu-snapshot-2007-05-26_05.tar.bz2) = 
55e73f0593c5d31ba3483e8034542c5ab33217cc3048995dd94edf9640e8411e
+SIZE (qemu/qemu-snapshot-2007-05-26_05.tar.bz2) = 1964534
 MD5 (qemu/patch3_cirrus) = ebe7ed9fce804c49e024bc93bfdfc810
 SHA256 (qemu/patch3_cirrus) = 
e862371834b7d895a896fbdb84fd9f70d17b5729a6f6789a48a61504fc941e11
 SIZE (qemu/patch3_cirrus) = 8817
Index: pkg-plist
===
RCS file: /home/pcvs/ports/emulators/qemu-devel/pkg-plist,v
retrieving revision 1.21
diff -u -r1.21 pkg-plist
--- pkg-plist   9 Apr 2007 22:11:23 -   1.21
+++ pkg-plist   26 May 2007 14:32:52 -
@@ -1,6 +1,7 @@
 bin/qemu
 bin/qemu-img
 bin/qemu-system-arm
+bin/qemu-system-m68k
 

Re: experimental qemu-devel port update, please test!

[Eric Anderson]

On 04/05/07 16:03, Juergen Lock wrote:

Hi!

 There have been a few interesting commits to qemu cvs, like,
a qcow2 corruption bugfix, vmware vga emulation (-vmwarevga), and
several emulated eepro100 (fxp) nic variants (-net nic,model=i82557b
-net user worked for me with FreeBSD and linux guests, and seemed even
slightly faster than the rtl8139 that already outperforms the default
ne2kpci), so I prepared another qemu-devel port update that I now want
you all to test with your various guests before I commit it!

 TIA, and enjoy...
Juergen



So far so good.  All previous features seem to work, and the vmwarevga 
option does too.  I'll try it with more testing this weekend, but it 
should be ok to commit I believe.


Thanks a ton!!

(looking forward to playing with the eepro driver!),
Eric

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

Re: experimental qemu-devel port update, please test!

[Eric Anderson]

On 04/05/07 16:03, Juergen Lock wrote:

Hi!

 There have been a few interesting commits to qemu cvs, like,
a qcow2 corruption bugfix, vmware vga emulation (-vmwarevga), and
several emulated eepro100 (fxp) nic variants (-net nic,model=i82557b
-net user worked for me with FreeBSD and linux guests, and seemed even
slightly faster than the rtl8139 that already outperforms the default
ne2kpci), so I prepared another qemu-devel port update that I now want
you all to test with your various guests before I commit it!

 TIA, and enjoy...
Juergen

Remove files: files/patch-audio::ossaudio.c files/patch-bh



Building it now.  Quick question:  why have some diffs below in the 
patch, when you say remove those files?  Just curious..


Eric




Index: Makefile
===
RCS file: /home/pcvs/ports/emulators/qemu-devel/Makefile,v
retrieving revision 1.72
diff -u -r1.72 Makefile
--- Makefile25 Mar 2007 16:33:01 -  1.72
+++ Makefile5 Apr 2007 16:08:57 -
@@ -6,7 +6,7 @@
 #
 
 PORTNAME=	qemu

-PORTVERSION=   0.9.0s.20070322
+PORTVERSION=   0.9.0s.20070405
 CATEGORIES=emulators
 MASTER_SITES=  http://qemu.org/:release \
http://qemu-forum.ipi.fi/qemu-snapshots/:snapshot \
@@ -14,7 +14,7 @@
http://www.volny.cz/xnavara/qemu/:snapshot \
http://people.brandeis.edu/~jcoiner/qemu_idedma/:idedma \
http://people.freebsd.org/~maho/qemu/:misc
-DISTNAME=  ${PORTNAME}-snapshot-2007-03-22_05
+DISTNAME=  ${PORTNAME}-snapshot-2007-04-05_05
 DISTFILES= ${DISTNAME}${EXTRACT_SUFX}:snapshot
 DIST_SUBDIR=   qemu
 EXTRACT_ONLY=  ${DISTNAME}${EXTRACT_SUFX}
Index: distinfo
===
RCS file: /home/pcvs/ports/emulators/qemu-devel/distinfo,v
retrieving revision 1.44
diff -u -r1.44 distinfo
--- distinfo25 Mar 2007 16:33:01 -  1.44
+++ distinfo5 Apr 2007 16:09:15 -
@@ -1,6 +1,6 @@
-MD5 (qemu/qemu-snapshot-2007-03-22_05.tar.bz2) = 
b1d9d1b68094a9679b77d8b08796a7e4
-SHA256 (qemu/qemu-snapshot-2007-03-22_05.tar.bz2) = 
be19f224e83fd90064f26b8d09fe018c4de7d27663f11544d494ac52d03808fa
-SIZE (qemu/qemu-snapshot-2007-03-22_05.tar.bz2) = 1685829
+MD5 (qemu/qemu-snapshot-2007-04-05_05.tar.bz2) = 
48321d0997db88f09f01d38500c52807
+SHA256 (qemu/qemu-snapshot-2007-04-05_05.tar.bz2) = 
48835ca90ced5cba2230fc95502b648167b5ca7247f885ee398ba891dbbf4c1b
+SIZE (qemu/qemu-snapshot-2007-04-05_05.tar.bz2) = 1721640
 MD5 (qemu/patch3_cirrus) = ebe7ed9fce804c49e024bc93bfdfc810
 SHA256 (qemu/patch3_cirrus) = 
e862371834b7d895a896fbdb84fd9f70d17b5729a6f6789a48a61504fc941e11
 SIZE (qemu/patch3_cirrus) = 8817
Index: files/patch-audio::ossaudio.c
===
RCS file: /home/pcvs/ports/emulators/qemu-devel/files/patch-audio::ossaudio.c,v
retrieving revision 1.2
diff -u -r1.2 patch-audio::ossaudio.c
--- files/patch-audio::ossaudio.c   10 Mar 2007 17:03:05 -  1.2
+++ files/patch-audio::ossaudio.c   5 Apr 2007 16:10:24 -
@@ -1,11 +0,0 @@
-Index: qemu/audio/ossaudio.c
-@@ -21,8 +21,8 @@
-  * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-  * THE SOFTWARE.
-  */
--#include sys/mman.h
- #include sys/types.h
-+#include sys/mman.h
- #include sys/ioctl.h
- #include sys/soundcard.h
- #include assert.h
Index: files/patch-bh
===
RCS file: /home/pcvs/ports/emulators/qemu-devel/files/patch-bh,v
retrieving revision 1.4
diff -u -r1.4 patch-bh
--- files/patch-bh  10 Mar 2007 17:03:05 -  1.4
+++ files/patch-bh  5 Apr 2007 16:32:18 -
@@ -1,26 +0,0 @@
-Index: qemu/dyngen-exec.h
-===
-RCS file: /cvsroot/qemu/qemu/dyngen-exec.h,v
-retrieving revision 1.12
-diff -w -u -d -r1.12 dyngen-exec.h
 dyngen-exec.h  12 May 2004 19:32:15 -  1.12
-+++ dyngen-exec.h  21 May 2004 15:00:41 -
-@@ -21,6 +21,8 @@
- #define __DYNGEN_EXEC_H__
- 
- #include stddef.h

-+#include stdio.h
-+#include config.h
- 
- typedef unsigned char uint8_t;

- typedef unsigned short uint16_t;
-@@ -54,9 +56,6 @@
- #define UINT32_MAX(4294967295U)
- #define UINT64_MAX((uint64_t)(18446744073709551615))
- 
--typedef struct FILE FILE;

--extern int fprintf(FILE *, const char *, ...);
--extern int printf(const char *, ...);
- #undef NULL
- #define NULL 0
- #ifdef _BSD
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
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: cyrus-sasl alternative?

[Eric]

Jona Joachim wrote:

Anton Blajev a écrit :

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello group,
what alternative can I use insted of the port scheduled for deletion:

portname:   security/cyrus-sasl

snip

If you also need a POP3/IMAP server you might want to take a look at 
Dovecot. I'm using Dovecot SASL.


maybe i missed something, but whats wrong with the sasl2 port? isnt that 
what most people are using already?

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

Re: hide dependency in graphics/xpdf port

[Eric P. Scott]

Try inserting something like this before .if defined(A4) in the
port's Makefile:


.if defined(WITH_LIBPAPER)
LIB_DEPENDS+=   paper.2:${PORTSDIR}/print/libpaper
CONFIGURE_ARGS+=-with-libpaper-library=${LOCALBASE}/lib \
--with-libpaper-includes=${LOCALBASE}/include
.else
CONFIGURE_ARGS+=--without-libpaper-library
.endif


If that solves the problem, submit a Followup to PR ports/110058
with the additional logic so it can be incorporated in the
upgrade to xpdf 3.02.

(Using A4 is not a factor here.)

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

Re: hide dependency in graphics/xpdf port

[Eric P. Scott]

Let's try that again, without the missing-hyphen typo:

.if defined(WITH_LIBPAPER)
LIB_DEPENDS+=   paper.2:${PORTSDIR}/print/libpaper
CONFIGURE_ARGS+=--with-libpaper-library=${LOCALBASE}/lib \
--with-libpaper-includes=${LOCALBASE}/include
.else
CONFIGURE_ARGS+=--without-libpaper-library
.endif

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

Zimbra Port for FreeBSD.

[Eric De La Cruz Lugo]

Heads up.

voting poll for FreeBSD port for Zimbra.

http://www.zimbra.com/forums/showthread.php?t=1247page=9

greetings from Merida, Yucatan, Mexico.

Eric De La Cruz Lugo.


 

TV dinner still cooling? 
Check out Tonight's Picks on Yahoo! TV.
http://tv.yahoo.com/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]