x11/ecore outdated

2007-08-31 Thread [LoN]Kamikaze
Hello,

I wanted to port entrance, but it seems the ecore Snapshot in ports is too old.
Is there an update to be expected?

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


textproc/p5-XML-LibXML Install Error

2007-08-31 Thread Cy Schubert
Has anyone seen this before. This is on the AMD64 platform running FreeBSD 
AMD64 with most ports (the ones that would build that is) built for AMD64. 
Perl 5.8.8 was built successfully for AMD64. This builds and installs when 
the system is booted in IA32 mode using FreeBSD ports built for IA32.

===  Checking if textproc/p5-XML-LibXML already installed
Files found in blib/arch: installing files in blib/lib into architecture 
dependent library tree
Writing /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/XML/LibXML/.packlist
Can't load '/usr/local/lib/perl5/site_perl/5.8.8/mach/auto/XML/LibXML/Common
/Common.so' for module XML::LibXML::Common: /usr/local/lib/perl5/site_perl/5
.8.8/mach/auto/XML/LibXML/Common/Common.so: Undefined symbol PL_sv_undef 
at /usr/local/lib/perl5/5.8.8/mach/DynaLoader.pm line 230.
 at /usr/local/lib/perl5/site_perl/5.8.8/mach/XML/LibXML.pm line 12
Compilation failed in require at /usr/local/lib/perl5/site_perl/5.8.8/mach/X
ML/LibXML.pm line 12.
BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.8.8/ma
ch/XML/LibXML.pm line 12.
Compilation failed in require at /usr/local/lib/perl5/site_perl/5.8.8/mach/X
ML/LibXML/SAX/Parser.pm line 8.
BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.8.8/ma
ch/XML/LibXML/SAX/Parser.pm line 8.
Compilation failed in require at /usr/local/lib/perl5/site_perl/5.8.8/XML/SA
X.pm line 147.
*** Error code 2

Stop in /dsk02/wrkdir/usr/ports/textproc/p5-XML-LibXML/work/XML-LibXML-1.63.
*** Error code 1

Stop in /usr/ports/textproc/p5-XML-LibXML.
bob# 



-- 
Cheers,
Cy Schubert [EMAIL PROTECTED]
FreeBSD UNIX:  [EMAIL PROTECTED]   Web:  http://www.FreeBSD.org

e**(i*pi)+1=0


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


Re: Problems with Firefox 2.0.0.6 and FreeBSD-STABLE 6.2

2007-08-31 Thread Simon Barner
 First, excuse me my top-posting, but... Is this the correct list for
 this mail about a Firefox problem?

It's not a wrong list, but freebsd-gnome (in Cc:, f'up2 set), would have
been even better (they maintain the firefox port as you can see from
the Makefile or by running `make maintainer').
 
 2007/8/28, TooMany Secrets [EMAIL PROTECTED]:
  Hi!
 
  My system:
 
  uname -a
  FreeBSD klingon.vlex.com 6.2-STABLE FreeBSD 6.2-STABLE #0: Sun Aug 12
  18:52:17 CEST 2007
  [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KLINGON  i386
 
  Firefox version port:
  firefox-2.0.0.6,1   Web browser based on the browser portion of Mozilla
  firefox-i18n-2.0.0.6 Localized interface for Firefox
 
  Other ports:
  nspluginwrapper-0.9.91.4_2
  linux-flashplugin-7.0r69
 
  Firefox runs fine, it doesn't hang or anything about. But the problem
  comes when I open any url, and I can't move up or down the page, or go
  to another tab. The firefox make a lag and I can't make anything.
  Times it lasts more, and other times it lasts less time, but is very
  very annoying, because I use it in my workstation at work.
 
  Anybody could help me, please? And excuse me my bad english...

Something seems broken on your system. Did you try an rebuild firefox
(maybe even with all its dependencies)?

-- 
Best regards / Viele Grüße, [EMAIL PROTECTED]
 Simon Barner[EMAIL PROTECTED]


pgpmne3sYfv0k.pgp
Description: PGP signature


HPLIP ugen

2007-08-31 Thread Brian Wagener
When using HPLIP your usb printer has to use the ugen driver in order for
all printing/scanning/status functionality to be present. The problem is, my
printer loads as a umass device so it doesn't get detected by hplip.

Does anyone know of a workaround for this? Is there anyway to force my
printer to use ugen instead of umass? I can't just remove umass because
other devices require it.

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


Re: HPLIP ugen

2007-08-31 Thread Lars Eighner

On Sat, 1 Sep 2007, Brian Wagener wrote:


When using HPLIP your usb printer has to use the ugen driver in order for
all printing/scanning/status functionality to be present. The problem is, my
printer loads as a umass device so it doesn't get detected by hplip.

Does anyone know of a workaround for this? Is there anyway to force my
printer to use ugen instead of umass? I can't just remove umass because
other devices require it.


The only way is to use a kernel built without umass (and without ulpt).  If
you can boot without umass, you can load umass from the command line (using
kldload) after the printer is attached.  Although I have not actually tried
it, I believe you have to unload umass if for some reason you printer is
detached and you want to reattach it.  If your printer has a card device, it
will work with HPLIP, so you don't need umass for your camera, if it uses a
supported type of card.  If you must have a umass device to boot, you're
screwed, but you probably can get your printer to print with HPIJS.

I have personally tested using a kernel without umass (and of course without
ulpt) to boot in order to successfully attach a psc 1350 (which registers
electronically as a 1300), then loading umass to use with an Olympus camera.
The result was everything was fully functional (but FAX was not tested).  Of
course it was pointless to attach the Olympus as the psc 1350 will read
Olympus cards, but it seems to demonstrate that (some? many? most?) umass
devices will work this way.

Of course most people will not mind the loss of ulpt if their printer works
with ugen, but the loss of umass is more serious.  There seems to be some
awareness among the port maintainers that this is a serious problem  There
is a certain logic to having the more specific ports grab a device if they
can before the general port gets a shot --- except it doesn't work out so
well in this case, so I have no idea whether a fix is on the horizen.

--
Lars Eighner
http://www.larseighner.com/index.html
8800 N IH35 APT 1191 AUSTIN TX 78753-5266

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