mailman: can't fetch

[chevy]

Hello,all.

please fix it , thank you very much !!

test# make
===>  Vulnerability check disabled, database not found
===>  Found saved configuration for mailman-2.1.8_3

You may change the following build options:
MM_USERNAME=mailman The username of the Mailman user.
MM_USERID=91The user ID of the Mailman user.
MM_GROUPNAME=mailmanThe group to which the Mailman user will belong.
MM_GROUPID=MM_USERIDThe group ID for the Mailman user.
MM_DIR=mailman  Mailman will be installed in /usr/local/mailman.
CGI_GID=www The group name or id under which your web server
executes CGI scripts.
IMGDIR=www/iconsIcon images will be installed in
/usr/local/www/icons.

=> indexing-2.1.6-0.1.patch.gz doesn't seem to exist in
/usr/ports/distfiles/mailman.
=> Attempting to fetch from http://www.openinfo.co.uk/mm/patches/444879/ .
fetch:
http://www.openinfo.co.uk/mm/patches/444879/indexing-2.1.6-0.1.patch.gz:
Operation timed out
=> Attempting to fetch from
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/mailman/
.
fetch:
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/mailman/indexing-2.1.6-0.1.patch.gz:
File unavailable (e.g., file not found, no access)
=> Couldn't fetch it - please try to retrieve this
=> port manually into /usr/ports/distfiles/mailman and try again.
*** Error code 1

Stop in /usr/ports/mail/mailman.


--
Regards.

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

Re: How to configure apache-ant to use bsdjava ?

[Jean-Baptiste Quenot]

* Hans Lambermont:
> 
> How can I configure apache-ant such that bsdjava is used instead of
> java/linux-sun-jdk14 ? I see no knobs in the Makefile to set this up.

Hello,

The javavm(1) manual page will give you some hints ;-)
-- 
 Jean-Baptiste Quenot
aka  John Banana Qwerty
http://caraldi.com/jbq/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FreeBSD Port: databases/py-psycopg

[Aaron Hilton]

Hello,

I am trying to install django, but have run into all sorts of  
dependency snafoos.  What is your recommendation for sticking to  
FreeBSD 8.1 Stable as closely as possible and yet satisfy the  
Postgresql 8.0 or 8.1 dependency for django and the recommended psycopg?


Sincerely,
- Aaron.
___
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: databases/py-psycopg

[Tobias Roth]

On Thu, Jul 20, 2006 at 03:10:17AM -0700, Aaron Hilton wrote:
> Hello,
> 
> I am trying to install django, but have run into all sorts of  
> dependency snafoos.  What is your recommendation for sticking to  
> FreeBSD 8.1 Stable as closely as possible and yet satisfy the  
> Postgresql 8.0 or 8.1 dependency for django and the recommended psycopg?

My recommendation to install django is to execute the following
commands (as root):

# cd /usr/ports/www/py-django
# make install

That should take care of all dependencies, unless you have special
requirements? If unsure about how to install software on FreeBSD,
you can always check the appropriate section in the handbook, you
will find that on http://www.freebsd.org/

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

Re: New portmaster version available for testing/feedback

[Hans Lambermont]

Doug Barton wrote:

> Doug Barton wrote:
> 
>> I just uploaded a version that has what should be a fix for this, can
>> you give it a try? And thanks for catching this, you're right, it's
>> an oversight on my part.
> 
> I'm curious if you've had a chance to try that fix, as I'd like to
> commit the new version sometime soon.

It's nice to have bootable backups ;-) I just tested the same upgrade
and it works OK now :

===>>> Upgrade for howl-1.0.0_1 to avahi-0.6.11_1 succeeded

I miss one dependency though :

# pkg_info -R avahi-0.6.11_1
Required by:
gimp-2.2.11,1
kde-3.5.2
planner-0.13_3

The old avahi-0.6.10_3 also had :
> # pkg_info -R avahi-0.6.10_3
> Required by:
> vlc-0.8.5_2

Is this a dependency-merge omission ? It looks like avahi-0.6.11_1 only
has the howl-1.0.0_1 dependencies.

> Also, in re-reading your message it occurs to me that one of the problems
> with what you did previously is that you specified just 'howl' as the second
> argument to -o, and that isn't enough. You either need to specify net/howl
> ala portupgrade, or howl-1.0.0_1 (i.e., the installed port name from
> /var/db/pkg).

Ah yes, perhaps this is a good thing to check for ? ;-)

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

HEADSUP: New UIDs/GIDs files under ports/

[Florent Thoumie]

FYI.

 Forwarded Message 
From: Florent Thoumie <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
cvs-all@FreeBSD.org
Subject: cvs commit: ports GIDs UIDs
Date: Thu, 20 Jul 2006 11:25:46 + (UTC)

flz 2006-07-20 11:25:46 UTC

  FreeBSD ports repository

  Added files:
.GIDs UIDs 
  Log:
  Please welcome UIDs and GIDs file. Those have been created from the UID/GID
  part of the Porter's Handbook. They're stored here to get more visibility.
  Please use these files exclusively when registering new users/groups.
  Documentation change is coming.
  
  Approved by:portmgr (erwin)
  
  Revision  ChangesPath
  1.1   +77 -0 ports/GIDs (new)
  1.1   +88 -0 ports/UIDs (new)

-- 
Florent Thoumie
[EMAIL PROTECTED]
FreeBSD Committer


signature.asc
Description: This is a digitally signed message part

Re: conflicting dependency

[Chuck Swiger]

John E Hein wrote:

Let's say there are two ports A & B.
They both provide libfoo.so.1 (and so register CONFLICTS with each other).

Now port C wants to use libfoo (and doesn't care if it gets it
from A or B).

What does port C list in it's LIB_DEPENDS?


Whichever one the author of port C chooses.

Quite often, at least for things like the BerkeleyDB, the author of port C 
will provide tunable OPTIONS or WITH_ or WITHOUT_ flags that you as the user 
of the port can tune to choose a particular version that you like.



What if it lists A and someone installs B... does A get registered as
the dependency when C is installed even though A is not installed?


No, the port should be registered against B and not A, if B is installed.

However, if a porter misses listing a necessary dependency, then things can 
get a little confused, and running "pkgdb -F" might help...


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

Re: conflicting dependency

[John E Hein]

Chuck Swiger wrote at 09:39 -0400 on Jul 20, 2006:
 > John E Hein wrote:
 > > Let's say there are two ports A & B.
 > > They both provide libfoo.so.1 (and so register CONFLICTS with each other).
 > > 
 > > Now port C wants to use libfoo (and doesn't care if it gets it
 > > from A or B).
 > > 
 > > What does port C list in it's LIB_DEPENDS?
 > 
 > Whichever one the author of port C chooses.
 > 
 > Quite often, at least for things like the BerkeleyDB, the author of port C 
 > will provide tunable OPTIONS or WITH_ or WITHOUT_ flags that you as the user 
 > of the port can tune to choose a particular version that you like.

Just for purposes of clarification, in this example, for purposes of
what C wants libfoo for, either libfoo from A or B will do.  C doesn't
care.


 > > What if it lists A and someone installs B... does A get registered as
 > > the dependency when C is installed even though A is not installed?
 > 
 > No, the port should be registered against B and not A, if B is installed.

I agree.  It should.  But how does the ports infrastructure accomplish
that?

If the porter listed A as the dependency and libfoo is already
installed via B, what is the mechanism in the ports infrastructure by
which B gets registered as the dependency?

B could have been installed 6 months ago before the user decided today
that he wants to use C.

Maybe there is no way right now to register the "installed"
alternative dependency automatically.


 > However, if a porter misses listing a necessary dependency, then
 > things can get a little confused, and running "pkgdb -F" might
 > help...

It's not that he missed listing a dependency.  The problem is that he
can't list both A & B - they conflict.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: conflicting dependency

[Chuck Swiger]

John E Hein wrote:

Chuck Swiger wrote at 09:39 -0400 on Jul 20, 2006:

John E Hein wrote:
> Let's say there are two ports A & B.
> They both provide libfoo.so.1 (and so register CONFLICTS with each other).
> 
> Now port C wants to use libfoo (and doesn't care if it gets it

> from A or B).
> 
> What does port C list in it's LIB_DEPENDS?


Whichever one the author of port C chooses.

Quite often, at least for things like the BerkeleyDB, the author of port C 
will provide tunable OPTIONS or WITH_ or WITHOUT_ flags that you as the user 
of the port can tune to choose a particular version that you like.


Just for purposes of clarification, in this example, for purposes of
what C wants libfoo for, either libfoo from A or B will do.  C doesn't
care.


That's right.  Plenty of software will work with anything from BDB-1.85 
through 4.x, for example.



What if it lists A and someone installs B... does A get registered as
the dependency when C is installed even though A is not installed?


No, the port should be registered against B and not A, if B is installed.


I agree.  It should.  But how does the ports infrastructure accomplish
that?


It uses pkg_which to figure out which port the file being depended upon 
actually comes from.



If the porter listed A as the dependency and libfoo is already
installed via B, what is the mechanism in the ports infrastructure by
which B gets registered as the dependency?


The package database keeps track of all files installed by ports and knows 
which port installed which file.  See "man pkg_which".


--
-Chuck

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

problems building net/py-pcap on 5.5...?

[Chuck Swiger]

Hi, all--

[ Port maintainer of py-pcap BCC:ed. ]

I just tried playing with the pcs port that gnn@ just mentioned, which needs 
py-pcap, only I can't seem to build this port on a FreeBSD-5.5 system:


[ ... ]
creating build/temp.freebsd-5.5-STABLE-i386-2.4
cc -fno-strict-aliasing -DNDEBUG -O -pipe -march=pentium -D__wchar_t=wchar_t 
-DTHREAD_STACK_SIZE=0x2 -O -pipe -march=pentium -fPIC -DSWIG_COBJECT_TYPES 
-I/usr/local/include/python2.4 -c pcap.c -o 
build/temp.freebsd-5.5-STABLE-i386-2.4/pcap.o

In file included from pcap.c:2515:
constants.c:8: error: `SWIG_PY_INT' undeclared here (not in a function)
constants.c:8: error: initializer element is not constant
constants.c:8: error: (near initialization for `pcapmodule_DLT[0].type')
constants.c:8: error: initializer element is not constant
constants.c:8: error: (near initialization for `pcapmodule_DLT[0]')
constants.c:11: error: initializer element is not constant
constants.c:11: error: (near initialization for `pcapmodule_DLT[1].type')
constants.c:11: error: initializer element is not constant
constants.c:11: error: (near initialization for `pcapmodule_DLT[1]')
constants.c:14: error: initializer element is not constant
constants.c:14: error: (near initialization for `pcapmodule_DLT[2].type')
[ ...approximately 50 similar warnings elided... ]
constants.c:170: error: (near initialization for `pcapmodule_DLT[52]')
constants.c:172: error: initializer element is not constant
constants.c:172: error: (near initialization for `pcapmodule_DLT[53]')
pcap.c: In function `init_pcap':
pcap.c:4220: warning: passing arg 2 of `SWIG_Python_InstallConstants' discards 
qualifiers from pointer target type
pcap.c:4230: warning: passing arg 3 of `PyModule_AddStringConstant' discards 
qualifiers from pointer target type

error: command 'cc' failed with exit status 1
*** Error code 1

Stop in /usr/ports/net/py-pcap.
346.96s real  109.23s user  78.57s system  54%

I'm using python-2.4.3, swig-1.3.29_2 and this kernel & world are:


FreeBSD sec.pkix.net 5.5-STABLE FreeBSD 5.5-STABLE #0: Wed Jun 28 13:43:02 EDT 
2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SEC  i386


Thanks for your time if you can help,
--
-Chuck

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

Re: conflicting dependency

[John E Hein]

Chuck Swiger wrote at 10:44 -0400 on Jul 20, 2006:
 > > If the porter listed A as the dependency and libfoo is already
 > > installed via B, what is the mechanism in the ports infrastructure by
 > > which B gets registered as the dependency?
 > 
 > The package database keeps track of all files installed by ports and knows 
 > which port installed which file.  See "man pkg_which".

Then I am seeing different behavior for some reason.  I see a @pkgdep
entry for an uninstalled port.  I'll see if I can track down why.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Netrek port appears broken

[Bill Moran]

It doesn't seem to have a maintainer.

[EMAIL PROTECTED] ~]$ netrek
bash: /usr/X11R6/bin/netrek: cannot execute binary file
[EMAIL PROTECTED] ~]$  file /usr/X11R6/bin/netrek
/usr/X11R6/bin/netrek: FreeBSD/i386 compact demand paged executable

This happens whether I install BRMH or COWS.

[EMAIL PROTECTED] ~]$ uname -a
FreeBSD vanquish.pgh.priv.collaborativefusion.com 6.1-RELEASE FreeBSD 
6.1-RELEASE #4: Tue May 16 12:43:32 EDT 2006 [EMAIL 
PROTECTED]:/usr/obj/usr/src/sys/VANQUISH  i386

-- 
Bill Moran
Collaborative Fusion Inc.


IMPORTANT: This message contains confidential information and is
intended only for the individual named. If the reader of this
message is not an intended recipient (or the individual
responsible for the delivery of this message to an intended
recipient), please be advised that any re-use, dissemination,
distribution or copying of this message is prohibited. Please
notify the sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or
error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. The
sender therefore does not accept liability for any errors or
omissions in the contents of this message, which arise as a
result of e-mail transmission.

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

libtool not happy building apache modules

[Matt Sealey]

===>  Generating apache plist
/usr/local/build-1/libtool --silent --mode=compile cc -prefer-pic -O -pipe 
-I/usr/local/include/mysql -D_THRE
AD_SAFE  -D_THREAD_SAFE -D_REENTRANT -O -pipe -I/usr/local/include/mysql 
-D_THREAD_SAFE -g -O2 -pthread -I/us
r/local/include/apache22  -I/usr/local/include/apr-1   
-I/usr/local/include/apr-1 -I/usr/local/include/db42 -
I/usr/local/include  -c -o fcgi_buf.lo fcgi_buf.c && touch fcgi_buf.slo
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
apxs:Error: Command failed with rc=65536

I am getting this ALL of the time now. I haven't changed a thing; from what I 
remember this is libtool
getting confused about my compiler settings and so on, but I have no 
definitions set for CC, I didn't
change the compiler ever, I just don't understand why it spontaneously broke 
for everything. Previously
I was having trouble with the mod_python port which did this, but all my other 
modules worked fine.

Any clues on what I can rebuild/reconfigure in order to get this to work? It's 
important that we install
some new modules this week.

-- 
Matt Sealey <[EMAIL PROTECTED]>
Manager, Genesi, Developer Relations

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

Re: libtool not happy building apache modules

[michael johnson]

On 7/20/06, Matt Sealey <[EMAIL PROTECTED]> wrote:



===>  Generating apache plist
/usr/local/build-1/libtool --silent --mode=compile cc -prefer-pic -O -pipe
-I/usr/local/include/mysql -D_THRE
AD_SAFE  -D_THREAD_SAFE -D_REENTRANT -O -pipe -I/usr/local/include/mysql
-D_THREAD_SAFE -g -O2 -pthread -I/us
r/local/include/apache22  -I/usr/local/include/apr-1
-I/usr/local/include/apr-1 -I/usr/local/include/db42 -
I/usr/local/include  -c -o fcgi_buf.lo fcgi_buf.c && touch fcgi_buf.slo
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
apxs:Error: Command failed with rc=65536

I am getting this ALL of the time now. I haven't changed a thing; from
what I remember this is libtool
getting confused about my compiler settings and so on, but I have no
definitions set for CC, I didn't
change the compiler ever, I just don't understand why it spontaneously
broke for everything. Previously
I was having trouble with the mod_python port which did this, but all my
other modules worked fine.

Any clues on what I can rebuild/reconfigure in order to get this to work?
It's important that we install
some new modules this week.



reinstall or update libtool


--

Matt Sealey <[EMAIL PROTECTED]>
Manager, Genesi, Developer Relations

___
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: libtool not happy building apache modules

[Matt Sealey]

But this is the libtool from APR (/usr/local/build-1/libtool). And I've rebuilt 
APR and libtool15, all day, testing the
modules I want to install, to no avail.
--
Matt Sealey <[EMAIL PROTECTED]>
Manager, Genesi, Developer Relations



  _  

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of michael johnson
Sent: Thursday, July 20, 2006 11:31 AM
To: [EMAIL PROTECTED]
Cc: freebsd-ports@freebsd.org
Subject: Re: libtool not happy building apache modules




On 7/20/06, Matt Sealey <[EMAIL PROTECTED]> wrote: 


===>  Generating apache plist
/usr/local/build-1/libtool --silent --mode=compile cc -prefer-pic -O -pipe 
-I/usr/local/include/mysql -D_THRE
AD_SAFE  -D_THREAD_SAFE -D_REENTRANT -O -pipe -I/usr/local/include/mysql 
-D_THREAD_SAFE -g -O2 -pthread -I/us 
r/local/include/apache22  -I/usr/local/include/apr-1   
-I/usr/local/include/apr-1 -I/usr/local/include/db42 -
I/usr/local/include  -c -o fcgi_buf.lo fcgi_buf.c && touch fcgi_buf.slo
libtool: compile: unable to infer tagged configuration 
libtool: compile: specify a tag with `--tag'
apxs:Error: Command failed with rc=65536

I am getting this ALL of the time now. I haven't changed a thing; from what I 
remember this is libtool
getting confused about my compiler settings and so on, but I have no 
definitions set for CC, I didn't 
change the compiler ever, I just don't understand why it spontaneously broke 
for everything. Previously
I was having trouble with the mod_python port which did this, but all my other 
modules worked fine.

Any clues on what I can rebuild/reconfigure in order to get this to work? It's 
important that we install 
some new modules this week.


reinstall or update libtool
 


--
Matt Sealey <[EMAIL PROTECTED]>
Manager, Genesi, Developer Relations

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

uim-qt build error

[Dan Reinholz]

Trying to build texproc/uim-qt on FreeBSD 6.1-Release
results in the following error:

===>  Building for uim-qt-1.1.1
(cd /usr/ports/textproc/uim-qt/work/uim-1.1.1/qt &&
gmake LIBS="-luim -luim-custom")
Making all in chardict
gmake[1]: Entering directory
`/usr/ports/textproc/uim-qt/work/uim-1.1.1/qt/chardict'
Making all in po
gmake[2]: Entering directory
`/usr/ports/textproc/uim-qt/work/uim-1.1.1/qt/chardict/po'
gmake[2]: Nothing to be done for `all'.
gmake[2]: Leaving directory
`/usr/ports/textproc/uim-qt/work/uim-1.1.1/qt/chardict/po'
gmake[2]: Entering directory
`/usr/ports/textproc/uim-qt/work/uim-1.1.1/qt/chardict'
/bin/sh /usr/local/bin/libtool --tag=CXX --mode=link
c++  -O2 -pipe -Wnon-virtual-dtor -Wno-long-long
-Wcast-align -Wconversion -Wchar-subscripts -Wall -W
-Wpointer-arith -Wwrite-strings -Wformat-security 
-L/usr/X11R6/lib  -L/usr/local/lib -o uim-chardict-qt
-L/usr/X11R6/lib -L/usr/lib -lqt-mt -lXext -lX11
uim_chardict_qt-chardict-qt.o
uim_chardict_qt-chardict-bushuviewwidget.o
uim_chardict_qt-chardict-chargridview.o
uim_chardict_qt-chardict-kseparator.o
uim_chardict_qt-chardict-unicodeviewwidget.o
-L/usr/local/lib -lintl -L/usr/local/lib -liconv
-R/usr/local/lib -luim -luim-custom
c++ -O2 -pipe -Wnon-virtual-dtor -Wno-long-long
-Wcast-align -Wconversion -Wchar-subscripts -Wall -W
-Wpointer-arith -Wwrite-strings -Wformat-security -o
uim-chardict-qt uim_chardict_qt-chardict-qt.o
uim_chardict_qt-chardict-bushuviewwidget.o
uim_chardict_qt-chardict-chargridview.o
uim_chardict_qt-chardict-kseparator.o
uim_chardict_qt-chardict-unicodeviewwidget.o 
-L/usr/X11R6/lib -L/usr/local/lib -L/usr/lib -lqt-mt
-lXext -lX11 /usr/X11R6/lib/libuim-custom.so
/usr/X11R6/lib/libuim.so /usr/local/lib/libintl.so
/usr/local/lib/libiconv.so -Wl,--rpath
-Wl,/usr/X11R6/lib -Wl,--rpath -Wl,/usr/local/lib
-Wl,--rpath -Wl,/usr/X11R6/lib -Wl,--rpath
-Wl,/usr/local/lib
/usr/X11R6/lib/libqt-mt.so: undefined reference to
`pthread_cleanup_pop'
/usr/X11R6/lib/libqt-mt.so: undefined reference to
`pthread_attr_destroy'
/usr/X11R6/lib/libqt-mt.so: undefined reference to
`pthread_attr_init'
/usr/X11R6/lib/libqt-mt.so: undefined reference to
`pthread_exit'
/usr/X11R6/lib/libqt-mt.so: undefined reference to
`pthread_cancel'
/usr/X11R6/lib/libqt-mt.so: undefined reference to
`pthread_testcancel'
/usr/X11R6/lib/libqt-mt.so: undefined reference to
`pthread_cleanup_push'
/usr/X11R6/lib/libqt-mt.so: undefined reference to
`pthread_attr_getschedpolicy'
/usr/X11R6/lib/libqt-mt.so: undefined reference to
`pthread_attr_setinheritsched'
/usr/X11R6/lib/libqt-mt.so: undefined reference to
`pthread_attr_setstacksize'
/usr/X11R6/lib/libqt-mt.so: undefined reference to
`pthread_attr_setschedparam'
/usr/X11R6/lib/libqt-mt.so: undefined reference to
`pthread_attr_setdetachstate'
/usr/X11R6/lib/libqt-mt.so: undefined reference to
`pthread_cond_timedwait'
gmake[2]: *** [uim-chardict-qt] Error 1
gmake[2]: Leaving directory
`/usr/ports/textproc/uim-qt/work/uim-1.1.1/qt/chardict'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/usr/ports/textproc/uim-qt/work/uim-1.1.1/qt/chardict'
gmake: *** [all-recursive] Error 1
*** Error code 2

Stop in /usr/ports/textproc/uim-qt.


Any help is greatly appreciated,

Dan

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: uim-qt build error

[Jeremy Chadwick]

On Thu, Jul 20, 2006 at 09:41:22AM -0700, Dan Reinholz wrote:
> /bin/sh /usr/local/bin/libtool --tag=CXX --mode=link
> c++  -O2 -pipe -Wnon-virtual-dtor -Wno-long-long
> -Wcast-align -Wconversion -Wchar-subscripts -Wall -W
> -Wpointer-arith -Wwrite-strings -Wformat-security 
> -L/usr/X11R6/lib  -L/usr/local/lib -o uim-chardict-qt
> -L/usr/X11R6/lib -L/usr/lib -lqt-mt -lXext -lX11
> uim_chardict_qt-chardict-qt.o
> uim_chardict_qt-chardict-bushuviewwidget.o
> uim_chardict_qt-chardict-chargridview.o
> uim_chardict_qt-chardict-kseparator.o
> uim_chardict_qt-chardict-unicodeviewwidget.o
> -L/usr/local/lib -lintl -L/usr/local/lib -liconv
> -R/usr/local/lib -luim -luim-custom
> c++ -O2 -pipe -Wnon-virtual-dtor -Wno-long-long
> -Wcast-align -Wconversion -Wchar-subscripts -Wall -W
> -Wpointer-arith -Wwrite-strings -Wformat-security -o
> uim-chardict-qt uim_chardict_qt-chardict-qt.o
> uim_chardict_qt-chardict-bushuviewwidget.o
> uim_chardict_qt-chardict-chargridview.o
> uim_chardict_qt-chardict-kseparator.o
> uim_chardict_qt-chardict-unicodeviewwidget.o 
> -L/usr/X11R6/lib -L/usr/local/lib -L/usr/lib -lqt-mt
> -lXext -lX11 /usr/X11R6/lib/libuim-custom.so
> /usr/X11R6/lib/libuim.so /usr/local/lib/libintl.so
> /usr/local/lib/libiconv.so -Wl,--rpath
> -Wl,/usr/X11R6/lib -Wl,--rpath -Wl,/usr/local/lib
> -Wl,--rpath -Wl,/usr/X11R6/lib -Wl,--rpath
> -Wl,/usr/local/lib
> /usr/X11R6/lib/libqt-mt.so: undefined reference to
> `pthread_cleanup_pop'
> 
> Any help is greatly appreciated,

Looks like the libtool call to c++ is missing the -pthread
argument, or as an alternative, missing -lpthread.

-- 
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networkinghttp://www.parodius.com/ |
| UNIX Systems Administrator   Mountain View, CA, USA |
| Making life hard for others since 1977.   PGP: 4BD6C0CB |

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

Re: conflicting dependency

[Scot Hetzel]

On 7/19/06, John E Hein <[EMAIL PROTECTED]> wrote:

Let's say there are two ports A & B.
They both provide libfoo.so.1 (and so register CONFLICTS with each other).

Now port C wants to use libfoo (and doesn't care if it gets it
from A or B).

What does port C list in it's LIB_DEPENDS?

What if it lists A and someone installs B... does A get registered as
the dependency when C is installed even though A is not installed?



In the port Cs Makefile, you add:

.if exists(${PREFIX}/bin/file found only in Port B)
PORTA_STAT= OFF
PORTB_STAT= ON
.else
PORTA_STAT= ON
PORTB_STAT= OFF
.endif

OPTIONS = PORTA "Depends on libfoo from port A" ${PORTA_STAT} \
 PORTB "Depends on libfoo from port B" ${PORTB_STAT}

.if defined(WITH_PORTA) || !defined(WITHOUT_PORTA)
LIB_DEPENDS+= foo.1:${PORTSDIR}/dependancy on Port A
.elif defined(WITH_PORTB)
LIB_DEPENDS+= foo.1:${PORTSDIR}/dependancy on Port B
.else
IGNORE= Must choose either port A or B
.endif

This allows the admin to install either port A or B, and port C will
automatically detect which port is installed, as well as allowing the
admin to choose which to install.

Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: conflicting dependency

[Pav Lucistnik]

John E Hein píše v st 19. 07. 2006 v 18:30 -0600:

> Let's say there are two ports A & B.
> They both provide libfoo.so.1 (and so register CONFLICTS with each other).
> 
> Now port C wants to use libfoo (and doesn't care if it gets it
> from A or B).

> What if it lists A and someone installs B... does A get registered as
> the dependency when C is installed even though A is not installed?

Yes, A will get registered as a dependency.

There is no systematic solution to this problem at the moment.
I'd love someone (Gabor?) working on fixing this defect.

-- 
Pav Lucistnik <[EMAIL PROTECTED]>
  <[EMAIL PROTECTED]>

... the obese drugged penguin used by Linux.
  -- Scott Long


signature.asc
Description: Toto je digitálně	 podepsaná část	 zprávy

FreeBSD Port: ftp/curl

[Andrew Pantyukhin]

I wonder if it's possible to resolve the situation when
(defined(WITH_GNUTLS) && !defined(WITHOUT_SSL)) in a
friendlier way than a simple IGNORE. I have WITH_GNUTLS
in my make.conf and I don't have WITHOUT_SSL there. It
would be great if you could make the port choose on its own,
either way would be perfect.

Thanks!
___
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: ftp/curl

[Scot Hetzel]

On 7/20/06, Andrew Pantyukhin <[EMAIL PROTECTED]> wrote:

I wonder if it's possible to resolve the situation when
(defined(WITH_GNUTLS) && !defined(WITHOUT_SSL)) in a
friendlier way than a simple IGNORE. I have WITH_GNUTLS
in my make.conf and I don't have WITHOUT_SSL there. It
would be great if you could make the port choose on its own,
either way would be perfect.



I had a look at the ports Makefile, and there is only one thing that
is holding the port back, from doing what you want.  The port defines:

.if !defined(WITHOUT_SSL)
USE_OPENSSL= yes
.endif

before it includes bsd.port.pre.mk.  If this could be included after
the bsd.port.pre.mk, then the port could have been made to work as you
wanted.  Since USE_OPENSSL is defined in bsd.port.pre.mk, it needs to
be defined before this *.mk file.  If it could be moved into
bsd.port.post.mk, then the ports Makefile could be changed as follows;

-.if !defined(WITHOUT_SSL)
-USE_OPENSSL= yes
-.endif

.include 

-.if defined(WITH_GNUTLS) && !defined(WITHOUT_SSL)
-IGNORE= may only use GNU TLS if WITHOUT_SSL is defined
+.if defined(WITH_GNUTLS)
+WITHOUT_SSL= yes
+.else
+USE_OPENSSL= yes
.endif

Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Can't install ruby-bdb on RELEASE-6.1

[Jim Trigg]

I'm setting up a new system with 6.1-RELEASE, and I forgot to install
portupgrade from a package during the OS install.  ruby-bdb fails to
build, complaining that it doesn't know how to make 'all' (it doesn't
specify which directory it's in, but it's right after it runs
extconf.rb).  Any clues?

(Note: when I posted this earlier I mentioned changing LOCALBASE.  Further
testing has shown that it fails regardless of LOCALBASE setting.)

Thanks,
Jim

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

Re: conflicting dependency

[RW]

On Thursday 20 July 2006 01:30, John E Hein wrote:
> Let's say there are two ports A & B.
> They both provide libfoo.so.1 (and so register CONFLICTS with each other).
>
> Now port C wants to use libfoo (and doesn't care if it gets it
> from A or B).
>
> What does port C list in it's LIB_DEPENDS?
>
> What if it lists A and someone installs B... does A get registered as
> the dependency when C is installed even though A is not installed?
>
> This must have been solved already... I just don't see where.



Many of these problems have been avoided by abstracting the dependency into 
the portsystem itself. For example USE_OPENLDAP=yes delegates the choice of 
LDAP  version to ports system.

In most cases this is just a way of having a  global default, but some are a 
bit more sophisticated. For example USE_GCC=3.4+ specifies version 3.4 or 
above of gcc; and there is some logic to determine whether this can be 
satisfied from the base system, or existing installed ports, before a new 
dependency is added.




> ___
> 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: uim-qt build error

[Dan Reinholz]

Thanks,

I don't have a lot of experience with compiling, but I
managed to figure it out. I just had to modify the
make as follows:

make CXXFLAGS="${CXXFLAGS} -pthread" install clean

I believe this should probably be easy enough to fix
in the port. ; )

Dan



__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fvwm 2.5.17 Issue

[Parv]

in message <[EMAIL PROTECTED]>, wrote Cy
Schubert thusly...
>
> Fvwm2 2.5.17 was released, however it contains a nasty little bug
> which causes it to ignore colour specification for the text in a
> title bar. Until this issue is addressed, I will hold off on
> updating the port.

Thanks Cy for both being current with the fvwm release & holding
back till the bug is fixed.


  - Parv

-- 

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

Re: HEADSUP: New UIDs/GIDs files under ports/

[Philip M. Gollucci]

>   Please welcome UIDs and GIDs file. Those have been created from the UID/GID
>   part of the Porter's Handbook. They're stored here to get more visibility.
>   Please use these files exclusively when registering new users/groups.
>   Documentation change is coming.
That rocks!

-- 

Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708
Consultant / http://p6m7g8.net/Resume/resume.shtml
Senior Software Engineer - TicketMaster - http://ticketmaster.com
1024D/A79997FA F357 0FDD 2301 6296 690F  6A47 D55A 7172 A799 97F

"In all that I've done wrong I know I must have done something right to
deserve a hug every morning and butterfly kisses at night."
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FreeBSD Port: linux_base-fc-4_6 - BROKEN PORT

[alexus]

dev# make install distclean
===>  Vulnerability check disabled, database not found
===>  Extracting for linux_base-fc-4_5
=> MD5 Checksum OK for rpm/i386/fedora/4/basesystem-8.0-5.noarch.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/basesystem-8.0-5.noarch.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/bash-3.0-31.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/bash-3.0-31.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/bzip2-1.0.2-16.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/bzip2-1.0.2-16.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/bzip2-libs-1.0.2-16.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/bzip2-libs-1.0.2-16.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/compat-db-4.2.52-2.FC4.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/compat-db-4.2.52-2.FC4.i386.rpm.
=> MD5 Checksum OK for
rpm/i386/fedora/4/compat-libstdc++-296-2.96-132.fc4.i386.rpm.
=> SHA256 Checksum OK for
rpm/i386/fedora/4/compat-libstdc++-296-2.96-132.fc4.i386.rpm.
=> MD5 Checksum OK for
rpm/i386/fedora/4/compat-libstdc++-33-3.2.3-47.fc4.i386.rpm.
=> SHA256 Checksum OK for
rpm/i386/fedora/4/compat-libstdc++-33-3.2.3-47.fc4.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/coreutils-5.2.1-48.1.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/coreutils-5.2.1-48.1.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/db4-4.3.27-5.fc4.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/db4-4.3.27-5.fc4.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/elfutils-libelf-0.108-1.i386.rpm.
=> SHA256 Checksum OK for
rpm/i386/fedora/4/elfutils-libelf-0.108-1.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/fedora-release-4-2.noarch.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/fedora-release-4-2.noarch.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/filesystem-2.3.4-1.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/filesystem-2.3.4-1.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/freetype-2.1.9-2.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/freetype-2.1.9-2.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/gdbm-1.8.0-25.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/gdbm-1.8.0-25.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/glib-1.2.10-16.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/glib-1.2.10-16.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/glibc-2.3.6-3.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/glibc-2.3.6-3.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/glibc-common-2.3.6-3.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/glibc-common-2.3.6-3.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/grep-2.5.1-48.2.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/grep-2.5.1-48.2.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/info-4.8-8.fc4.2.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/info-4.8-8.fc4.2.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/libacl-2.2.32-1.FC4.2.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/libacl-2.2.32-1.FC4.2.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/libattr-2.4.24-1.FC4.1.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/libattr-2.4.24-1.FC4.1.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/libgcc-4.0.2-8.fc4.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/libgcc-4.0.2-8.fc4.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/libselinux-1.23.11-1.1.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/libselinux-1.23.11-1.1.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/libstdc++-4.0.2-8.fc4.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/libstdc++-4.0.2-8.fc4.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/libtermcap-2.0.8-41.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/libtermcap-2.0.8-41.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/ncurses-5.4-19.fc4.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/ncurses-5.4-19.fc4.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/pcre-5.0-4.1.fc4.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/pcre-5.0-4.1.fc4.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/popt-1.10.1-23.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/popt-1.10.1-23.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/readline-5.0-3.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/readline-5.0-3.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/rpm-4.4.1-23.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/rpm-4.4.1-23.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/setserial-2.17-19.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/setserial-2.17-19.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/setup-2.5.44-1.1.noarch.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/setup-2.5.44-1.1.noarch.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/slang-1.4.9-17.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/slang-1.4.9-17.i386.rpm.
=> MD5 Checksum OK for rpm/i386/fedora/4/termcap-5.4-7fc4.noarch.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/4/termcap-5.4-7fc4.noarch.rpm.
=> MD

FreeBSD Port: gettext-0.14.5_2 - BROKEN PORT!

[alexus]

===>  Building for gettext-0.14.5_2
Making all in autoconf-lib-link
Making all in m4
Making all in tests
Making all in gettext-runtime
make  all-recursive
Making all in doc
Making all in intl
/bin/sh /usr/local/bin/libtool --mode=compile cc -c
-DLOCALEDIR=\"/usr/local/share/locale\"
-DLOCALE_ALIAS_PATH=\"/usr/local/share/locale\"
-DLIBDIR=\"/usr/local/libdata\" -DIN_LIBINTL  -DENABLE_RELOCATABLE=1
-DIN_LIBRARY -DINSTALLDIR=\"/usr/local/lib\" -DNO_XMALLOC
-Dset_relocation_prefix=libintl_set_relocation_prefix
-Drelocate=libintl_relocate  -DDEPENDS_ON_LIBICONV=1 -DHAVE_CONFIG_H -I. -I.
-I.. -I/usr/local/include -O2 -fno-strict-aliasing -pipe  ./bindtextdom.c
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
*** Error code 1

Stop in /usr/ports/devel/gettext/work/gettext-0.14.5/gettext-runtime/intl.
*** Error code 1

Stop in /usr/ports/devel/gettext/work/gettext-0.14.5/gettext-runtime.
*** Error code 1

Stop in /usr/ports/devel/gettext/work/gettext-0.14.5/gettext-runtime.
*** Error code 1

Stop in /usr/ports/devel/gettext/work/gettext-0.14.5.
*** Error code 1

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

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

Stop in /usr/ports/archivers/rpm.
*** Error code 1

Stop in /usr/ports/emulators/linux_base-fc4.
dev# uname -a
FreeBSD dev.hotcamsluts.com 6.1-RELEASE-p2 FreeBSD 6.1-RELEASE-p2 #0: Mon
Jul  3 01:22:25 EDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
i386
dev# 


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

Re: Can't install ruby-bdb on RELEASE-6.1

[Sergey Matveychuk]

Jim Trigg wrote:
> I'm setting up a new system with 6.1-RELEASE, and I forgot to install
> portupgrade from a package during the OS install.  ruby-bdb fails to
> build, complaining that it doesn't know how to make 'all' (it doesn't
> specify which directory it's in, but it's right after it runs
> extconf.rb).  Any clues?
> 
> (Note: when I posted this earlier I mentioned changing LOCALBASE.  Further
> testing has shown that it fails regardless of LOCALBASE setting.)

Make sure you have a fresh ports tree.
May be you should reinstall ruby.

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

is somebody working on a xorg 7.1 port to FreeBSD ?

[Andreas Klemm]

Hi,

interested to know, if there was only a talk or work going
on to bring xorg 7.1 into freebsd ports.

For me personally it means to get a chance of getting
perhaps drm to run on my graphics card.

drm0:  port 0x7000-0x70ff mem 
0xe000-0xe7ff,0xf901-0xf901 irq 16 at device 0.0 on pci1
info: [drm] AGP at 0xf000 128MB

Whenever I run X11 I get this message:
info: [drm] Initialized radeon 1.24.0 20060225
error: [drm:pid1703:radeon_do_init_cp] *ERROR* Cannot initialise DRM on this 
card

Would have liked to try a never X server by a -snap port.
But the xorg server snap port is still at 6.8.

Any idea ?

Thanks a lot

Andreas ///

-- 
Andreas Klemm - Powered by FreeBSD 6
Need a magic printfilter today ? -> http://www.apsfilter.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"