OCILib Ports
Hello guys, there is someone that already working on OCILib port? http://orclib.sourceforge.net/ Ciao Franco ___ 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: OCILib Ports
Le Ven 6 fév 09 à 9:00:01 +0100, Franco Marchesini franco.marches...@gmail.com écrivait : Hello guys, Hello, there is someone that already working on OCILib port? http://orclib.sourceforge.net/ It seems interesting, but this is a wrapper on Oracle's OCI, and ATM there is no supported OCI in the ports tree. Do you think that it could work with oracle8-client or with linux-oracle-instantclient? Regards, -- Th. Thomas. pgp20rTjK5b9A.pgp Description: PGP signature
Re: OCILib Ports
Hello, I read in documentatione that there is support for instantclient... Now prepare a virtual machine and I try to compile. Ciao Franco http://orclib.sourceforge.net/doc/html/group__g__install.html Oracle Instant Client Support OCILIB supports Oracle Instant Client. On Microsoft Windows, there is no difference between using a regular Oracle client and an Instant Client with OCILIB On Unix-like systems, the Instant Client is divised in different packages. Public headers and shared libs are not part of the same package. So, you must provide the following options to the configure command : * with-oracle-headers-path : location the public header files * with-oracle-lib-path : location the oracle shared lib If your instant client package containing the shared libs does not have a symbolic link 'libclntsh.[shared lib extension]' to the fully qualified shared lib real name, you must create it : Example on Linux : * $ ln -s $ORALIBPATH/libclntsh.so.10.1 $ORALIBPATH/libclntsh.so --- 2009/2/6 Thierry Thomas thie...@freebsd.org: Le Ven 6 fév 09 à 9:00:01 +0100, Franco Marchesini franco.marches...@gmail.com écrivait : Hello guys, Hello, there is someone that already working on OCILib port? http://orclib.sourceforge.net/ It seems interesting, but this is a wrapper on Oracle's OCI, and ATM there is no supported OCI in the ports tree. Do you think that it could work with oracle8-client or with linux-oracle-instantclient? Regards, -- Th. Thomas. ___ 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
OT: problem with apache
Are there any Apache gurus out these willing help with a (hopefully) small problem? If so, please contact me privately. Robert Huff ___ 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: Xorg disaster
Lars Eighner schrieb: Xorg upgrade (gory details follow) went south. I must have a working graphics browser by Monday. This is pretty much *vital*, as in a matter of survival. What is the fastest and/or surest way to get a platform that will run firefox or opera? a. try to get my nvidia hardware to work with a generic (vesa or vga) driver? b. try to downgrade Xorg to something that worked. Deinstall the nvidia driver and try a. first. Chances are high you will have something usable. If that doesn't work: do b. . Good Luck! Uli. Hints on either course would be appreciated. What happened: upgraded system from 7.1 prerelease to 7.1 release p2. cvsupped the ports tree. Upgraded Xorg and nvidia-driver (after upgrading perl and everything portupgrade -fr perl5.8 will upgrade (as the script failed miserably). This was after 20090124 when the mouse problem was supposed to be fixed. What happens: first there is something undefined in nvidia's libwfb so I changed the symbolic link to point to Xorg's version of the lib. That message went away, but there are tons of Generic Event Extension missing messages and no mouse --- what is more the accessibility keypad mouse thing doesn't work at all. I can't pay my bills and I can't get to another computer to use someone else's browser to do it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: OCILib Ports
Le Ven 6 fév 09 à 10:05:27 +0100, Franco Marchesini franco.marches...@gmail.com écrivait : Hello, Hello, I read in documentatione that there is support for instantclient... Now prepare a virtual machine and I try to compile. Beware: instantclient does not provide a native FreeBSD library, linux emulation is required. Anyway, good luck! -- Th. Thomas. pgpi0tFZQvKY0.pgp Description: PGP signature
Lend FreeBSD 7 or 8 access for ports upgrade?
Greetings, could someone lend me an account on his FreeBSD machine for a couple of days so that I can update sysutils/e2fsprogs to a new upstream release? Any architecture will do. I do not need root access, but I need to be able to ssh in and build ports, obviously. It's easier for me if vim, rsync, ports-mgmt/porttools and cvs are installed and the firewall allows CVS to the anoncvs servers. :-) Reason for asking is that I've trashed my /usr filesystem on 7.1-RELEASE with growfs fsck and want to do forensics before reinstalling everything to figure how growfs managed to eat /usr, and a separate account would likely allow me to update the e2fsprogs port much sooner. Contact me off-list with offers (if I don't reply, I'm swamped with offers ;-)). Thanks in advance. Best regards Matthias ___ 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: Xorg disaster
On Thu, 5 Feb 2009, Alex Goncharov wrote: ,--- You/Lars (Thu, 5 Feb 2009 20:20:50 -0600 (CST)) * | Xorg upgrade (gory details follow) went south. I must have a working | graphics browser by Monday. This is pretty much *vital*, as in a matter of | survival. Been there (last week) -- know what you mean. | What is the fastest and/or surest way to get a platform that will run | firefox or opera? | | a. try to get my nvidia hardware to work with a generic (vesa or vga) driver? | b. try to downgrade Xorg to something that worked. I tried b -- very successfully. The path is (roughly): 1. Find the dependencies of xproto and xextproto: pkg_info -R xproto-\* xextproto-\* | wc -l Prepare to remove those (new) packages from your system. 2. Before you remove them, record their names and origins -- you will need them to either get their old versions from ftp.freebsd.org or too build from ports source. 3. Remove the packages identified in step 1. 4. FTP-get or build the old versions. If you are to build them, you need the old ports tree: use this tag in your ports-supfile: *default release=cvs tag=. date=2009.01.23.12.00.00 Thanks. It was how to set the wayback machine that was the missing piece to the puzzle. I did this since I am on dial-up and had not deleted the old distfiles (and did not have any of the packages. It wasn't a bed of roses and plenty of restoring is still ahead, but the mission critical stuff now works. I would not recommend your own build under the circumstances: FTP-getting is much faster, of course -- the whole process will take you about two hours, I think. No doubt, but having the monster distfiles still on-hand tips the balance. This seems to make the point: never delete the last cycle distfiles. I use the nv driver BTW -- perfectly -- in the old (downgraded to) X. yes xorg 7.3 seems to work perfectly. The display would work but the mouse wouldn't with 7.4. I suspect the fix for the hal-moused battle does not work nv. -- 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 freebsd-ports-unsubscr...@freebsd.org
Re: Xorg disaster
Lars Eighner wrote: Xorg upgrade (gory details follow) went south. I must have a working graphics browser by Monday. This is pretty much *vital*, as in a matter of survival. What is the fastest and/or surest way to get a platform that will run firefox or opera? a. try to get my nvidia hardware to work with a generic (vesa or vga) driver? b. try to downgrade Xorg to something that worked. c. Use the new Xorg with the included nv driver instead of the nvidia binary driver. I usually use the binary driver, but I recently upgraded to the new Xorg and for a variety of reasons decided to try out the Xorg nv driver and didn't have any problems. FWIW, as a general course of action I find it useful to upgrade _everything_ on the system (base, ports, etc.) first before doing the nvidia driver, since the compiled parts are sensitive to changes in the underlying source and headers. Also, make sure that you have followed the instructions in /usr/ports/UPDATING, and you might also consider clearing out /usr/local/lib/compat/pkg if it exists. hth, Doug -- This .signature sanitized for your protection ___ 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
tcl/tk 8.6.x ports
Is there a reason why lang/tcl86, x11-toolkits/tk86, and their threaded versions are not included in lang/Makefile and x11-toolkits/Makefile, even though they've been hooked up in Mk/bsd.tcl.mk? If not, would someone mind connecting them? Regards, b. ___ 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: Xorg disaster
On Fri, Feb 6, 2009 at 12:11 PM, Lars Eighner portsu...@larseighner.com wrote: I use the nv driver BTW -- perfectly -- in the old (downgraded to) X. yes xorg 7.3 seems to work perfectly. The display would work but the mouse wouldn't with 7.4. I suspect the fix for the hal-moused battle does not work nv. The video driver (nv) shouldn't have any effect on an input driver (mouse). If you still have xorg 7.4 installed, try running hal-device and check if your mouse is enabled or ignored. I had this problem due to an extra configuration file under /usr/local/share/hal that had disabled hal's ability to manage my /dev/psm0. If you can post both the output of hal-device and the Xorg.0.log (from xorg 7.4), someone should be able to resolve your mouse issue. Scot ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: enlightenment-0.16.999.042_1,2
Sondre Tristan Midttun wrote: I'm having some problems with installing the enlightenment-devel port. I posted on FreeBSD forums here: http://forums.freebsd.org/showthread.php?t=1958 I'm not a maintainer, but I'll try... It seems that you skipped the installation of devel/e_dbus. Can you please: 1. Send output of 'make clean; make configure' in ports directory. 2. Build devel/e_dbus by hand a try to rebuild enlightenment-devel. I really dunno how this can happen because enlightenment-devel depends on e_dbus. -- Sphinx of black quartz judge my vow. ___ 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: Xorg disaster
On Fri, Feb 6, 2009 at 8:35 PM, Doug Barton do...@freebsd.org wrote: c. Use the new Xorg with the included nv driver instead of the nvidia binary driver. I usually use the binary driver, but I recently upgraded to the new Xorg and for a variety of reasons decided to try out the Xorg nv driver and didn't have any problems. You're lucky. On my system (nvidia 8500GT card) only vesa driver works without issues. FWIW, as a general course of action I find it useful to upgrade _everything_ on the system (base, ports, etc.) first before doing the nvidia driver, since the compiled parts are sensitive to changes in the underlying source and headers. Done and you might also consider clearing out /usr/local/lib/compat/pkg if it exists. Undone, I'll try Reagrds -- Diego Depaoli ___ 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: Message when updating ports
Leslie Jensen wrote: I've obviously got a problem with several of my +CONTENTS files. I've got help from the list to edit some of the files, but I get a feeling that I need to replace the /var/db/pkg/* infrastructure. Can it be done and how do I go about it? Otherwise I'd be glad if someone will give me a suggestion on how I should solve the problem below? : Leaving directory `/usr/ports/devel/gio-fam-backend/work/glib-2.18.4/g io/fam' === Registering installation for gio-fam-backend-2.18.4 === Cleaning for gio-fam-backend-2.18.4 === Updating package dependency entry for each dependent port === devel/dbus-glib is listed as a dependency === but there is no installed version As Scot told you a while ago, your /var/db/pkg/* files are corrupt. To fix this exact problem you need to do 'portmaster devel/dbus-glib' which will rebuild the port and fix all the +CONTENTS files. You should do this for each port that comes up with this problem. You might also consider using the --check-depends option. hope this helps, Doug -- This .signature sanitized for your protection ___ 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
Minor fix for KDE 4 monitor screen saver/power save nit
Hi All,
KDE 4.1.4 (and I believe KDE 4.2.0) has an issue with krunner that stops
the monitor from dropping into power save mode if the screen saver kicks
in before the power save timeout. This bugged me sufficiently to find a
fix, so thought I'd share this in case this issue is bugging anyone else.
The relevant KDE bug report is here:
http://bugs.kde.org/show_bug.cgi?id=165265
I've backported the fix from the 4.2 tree for KDE 4.1.4. Stick the
attached patch in /usr/ports/x11/kdebase4-workspace/files and
rebuild/reinstall the port.
For KDE 4.2.0, the patch obtained by running:
svn diff -c916964 svn://anonsvn.kde.org/home/kde/branches/KDE/4.2/kdebase
should work with some minor tweaks to the patch meta data. Same
procedure applies as for 4.1.4.
I've confirmed the attached patch resolves the issue for 4.1.4.
Cheers,
Lawrence
Index: ../krunner/lock/lockprocess.cc
===
--- ../krunner/lock/lockprocess.cc.orig (revision 916963)
+++ ../krunner/lock/lockprocess.cc (revision 916964)
@@ -1104,7 +1104,6 @@
return; // no resuming with dialog visible or when not visible
if( mSuspended mHackProc.state() == QProcess::Running )
{
-XForceScreenSaver(QX11Info::display(), ScreenSaverReset );
QPainter p( this );
p.drawPixmap( 0, 0, mSavedScreen );
p.end();
Index: ../krunner/xautolock.cpp
===
--- ../krunner/xautolock.cpp.orig 2008-08-28 18:07:00.0 +1000
+++ ../krunner/xautolock.cpp2009-02-06 17:05:19.0 +1100
@@ -83,8 +83,10 @@
mActive = false;
mTimerId = startTimer( CHECK_INTERVAL );
+// This is an internal clock timer (in seconds), used instead of querying
system time.
+// It is incremented manually, preventing from problems with clock jumps.
+// In other words, this is the 'now' time and the reference point for
other times here.
mElapsed = 0;
-
}
//---
@@ -126,8 +128,6 @@
{
mActive = true;
resetTrigger();
-XSetScreenSaver(QX11Info::display(), mTimeout + 10, 100, PreferBlanking,
DontAllowExposures); // We'll handle blanking
-kDebug() XSetScreenSaver mTimeout + 10;
}
//---
@@ -138,8 +138,6 @@
{
mActive = false;
resetTrigger();
-XSetScreenSaver(QX11Info::display(), 0, 100, PreferBlanking,
DontAllowExposures); // No blanking at all
-kDebug() XSetScreenSaver 0;
}
//---
@@ -148,12 +146,15 @@
//
void XAutoLock::resetTrigger()
{
+// Time of the last user activity (used only when the internal XScreensaver
+// idle counter is not available).
mLastReset = mElapsed;
+// Time when screensaver should be activated.
mTrigger = mElapsed + mTimeout;
#ifdef HAVE_XSCREENSAVER
xautolock_lastIdleTime = 0;
#endif
-XForceScreenSaver( QX11Info::display(), ScreenSaverReset );
+// Do not reset the internal X screensaver here (no XForceScreenSaver())
}
//---
@@ -205,12 +206,11 @@
bool activate = false;
-// kDebug() now mTrigger;
+// This is the test whether to activate screensaver. If we have reached
the time
+// and for the whole timeout period there was no activity (which would
change mTrigger
+// again), activate.
if (mElapsed = mTrigger)
-{
-resetTrigger();
activate = true;
-}
#ifdef HAVE_DPMS
BOOL on;
@@ -222,6 +222,8 @@
// that is always smaller than DPMS timeout (X bug I guess). So if DPMS
// saving is active, simply always activate our saving too, otherwise
// this could prevent locking from working.
+// X.Org 7.4: With this version activating DPMS resets the screensaver
idle timer,
+// so keep this. It probably makes sense to always do this anyway.
if(state == DPMSModeStandby || state == DPMSModeSuspend || state ==
DPMSModeOff)
activate = true;
if(!on mDPMS) {
Index: ../krunner/saverengine.cpp
===
--- ../krunner/saverengine.cpp.orig (revision 916963)
+++ ../krunner/saverengine.cpp (revision 916964)
@@ -46,7 +46,11 @@
// Save X screensaver parameters
XGetScreenSaver(QX11Info::display(), mXTimeout, mXInterval,
mXBlanking, mXExposures);
-// ... and disable it
+// And disable it. The internal X screensaver is not used at all, but we
use its
+// internal idle timer (and it is also used by DPMS support in X). This
timer must not
+// be altered by this code, since e.g. resetting the counter after
activating our
+// screensaver would prevent DPMS from activating. We use the timer merely
Re: Minor fix for KDE 4 monitor screen saver/power save nit
On Sat, 07 Feb 2009 16:55:31 +1100, Lawrence Stewart wrote: Hi All, KDE 4.1.4 (and I believe KDE 4.2.0) has an issue with krunner that stops the monitor from dropping into power save mode if the screen saver kicks in before the power save timeout. This bugged me sufficiently to find a fix, so thought I'd share this in case this issue is bugging anyone else. The relevant KDE bug report is here: http://bugs.kde.org/show_bug.cgi?id=165265 I've backported the fix from the 4.2 tree for KDE 4.1.4. Stick the attached patch in /usr/ports/x11/kdebase4-workspace/files and rebuild/reinstall the port. For KDE 4.2.0, the patch obtained by running: svn diff -c916964 svn://anonsvn.kde.org/home/kde/branches/KDE/4.2/kdebase should work with some minor tweaks to the patch meta data. Same procedure applies as for 4.1.4. I've confirmed the attached patch resolves the issue for 4.1.4. Cheers, Lawrence Thanks for report! KDE4 ports will be updated to 4.2.0 soon, so I've added patches to our local repo. Max ___ 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
