Le 10/11/2008 à 21:53:32+, Matthew Seaman a écrit
> Albert Shih wrote:
>
> > Maybe my question is not very clear
> >
> > The p5 package work in shell, because the PATH is in the shell.
> >
> > But when I use the application throught the web it's not working. But I
> > don't known how t
Le 10/11/2008 à 22:35:44+0100, Mel a écrit
> On Monday 10 November 2008 21:36:43 Albert Shih wrote:
>
> > But when I use the application throught the web it's not working. But I
> > don't known how to tell apache ? mod_perl ? the PATH.
>
Thanks for your help
> Check the shell script /usr/local/
Albert Shih wrote:
Maybe my question is not very clear
The p5 package work in shell, because the PATH is in the shell.
But when I use the application throught the web it's not working. But I
don't known how to tell apache ? mod_perl ? the PATH.
If you're using mod_perl2, then Apache w
On Monday 10 November 2008 21:36:43 Albert Shih wrote:
> But when I use the application throught the web it's not working. But I
> don't known how to tell apache ? mod_perl ? the PATH.
Apache.
Check the shell script /usr/local/sbin/envvars. In short, any file
in /usr/local/etc/apache22/envvars.d
Le 10/11/2008 à 11:10:02-0500, Jerry McAllister a écrit
> On Mon, Nov 10, 2008 at 12:08:05PM +0100, Albert Shih wrote:
>
> > Hi all
> >
>
> Whenever you use some command or address some file in a script or within a
> program, you should use the full path - starting with '/' so instead of
> lc
On Mon, Nov 10, 2008 at 12:08:05PM +0100, Albert Shih wrote:
> Hi all
>
> I've PATH problem with a perl package (I don't knwon anything about
> perl).
>
> I run rt (3.8) under apache22 + mod_perl2 and on some p5 librairie I've got
> message like
>
Hi all
I've PATH problem with a perl package (I don't knwon anything about
perl).
I run rt (3.8) under apache22 + mod_perl2 and on some p5 librairie I've got
message like
Command 'dot' not found in /bin, /usr/bin at
/usr/local/lib/perl5/site_perl/5.8.8/GraphViz.
On Mon, 11 Feb 2008 19:11:32 +0100 (CET) Wojciech Puchar wrote:
> > serafina# dmesg -a | grep -A1 ABI
> > Additional ABI support:
> > linux
> >
> > serafina# /etc/rc.d/abi restart
> > Additional ABI support: linux.
> >
> magic starts here. sorry.
:-)
> > serafina# /compat/linux/bin/sh
> > sh-3.
Written by Steve Franks on 02/11/08 13:56>>
> So my problem is that things are expecting libs in
> /usr/compat/linux/lib instead of /usr/compat/linux/usr/lib, and when
> they don't find it in linux/lib they go straight to the FreeBSD
> version?
>
> So should I be fixing my path, or linking linux/u
Am 11.02.2008, 20:56 Uhr, schrieb Steve Franks <[EMAIL PROTECTED]>:
So should I be fixing my path, or linking linux/usr/lib to linux/lib, or
what?
On Feb 11, 2008 12:06 PM, Reid Linnemann <[EMAIL PROTECTED]> wrote:
work around this by linking
/usr/compat/linux/usr/lib/librt.so.1 to the actu
So my problem is that things are expecting libs in
/usr/compat/linux/lib instead of /usr/compat/linux/usr/lib, and when
they don't find it in linux/lib they go straight to the FreeBSD
version?
So should I be fixing my path, or linking linux/usr/lib to linux/lib, or what?
Steve
On Feb 11, 2008 12
Written by Michael Ross on 02/11/08 12:42>>
> Am 11.02.2008, 19:26 Uhr, schrieb Reid Linnemann <[EMAIL PROTECTED]>:
>
>
>> It is not finding the FreeBSD versions of libraries. There is no
>> /usr/lib/librt.so.1 in FreeBSD, that is linux's real-time threading
>> library. Try brandelf /usr/compat/l
Am 11.02.2008, 19:26 Uhr, schrieb Reid Linnemann <[EMAIL PROTECTED]>:
It is not finding the FreeBSD versions of libraries. There is no
/usr/lib/librt.so.1 in FreeBSD, that is linux's real-time threading
library. Try brandelf /usr/compat/linux/usr/lib/librt.so.1 to see if
it's branded.
[EMAIL
Written by Steve Franks on 02/11/08 12:11>>
> I think my problem lies elsewhere: linux & abi started, but no
> difference! I have the linux .so files right in compat/linux/usr/lib,
> but it always finds the freeBSD versions first!
>
> Steve
>
> sh-3.00$ kldstat
> Id Refs AddressSize Nam
serafina# dmesg -a | grep -A1 ABI
Additional ABI support:
linux
serafina# /etc/rc.d/abi restart
Additional ABI support: linux.
magic starts here. sorry.
serafina# /compat/linux/bin/sh
sh-3.00# ls
ls: error while loading shared libraries: /usr/lib/librt.so.1: ELF file OS
ABI invalid
Mich
I think my problem lies elsewhere: linux & abi started, but no
difference! I have the linux .so files right in compat/linux/usr/lib,
but it always finds the freeBSD versions first!
Steve
sh-3.00$ kldstat
Id Refs AddressSize Name
1 19 0xc040 926ed4 kernel
21 0xc0d27000 5a74
Am 11.02.2008, 18:53 Uhr, schrieb Wojciech Puchar
<[EMAIL PROTECTED]>:
if not set it and rerun /etc/rc.d/abi
serafina# kldload linux
serafina# /etc/rc.d/abi start
Additional ABI support:.
should be
Additional ABI support:linux.
you miss
linux_enable="YES"
in rc.conf
If I linux_enab
if not set it and rerun /etc/rc.d/abi
serafina# kldload linux
serafina# /etc/rc.d/abi start
Additional ABI support:.
should be
Additional ABI support:linux.
you miss
linux_enable="YES"
in rc.conf
___
freebsd-questions@freebsd.org mailing list
h
Am 11.02.2008, 18:20 Uhr, schrieb Wojciech Puchar
<[EMAIL PROTECTED]>:
did you have
linux_enable="YES" in your rc.conf
if not set it and rerun /etc/rc.d/abi
serafina# kldload linux
serafina# /etc/rc.d/abi start
Additional ABI support:.
serafina# /compat/linux/bin/sh
sh-3.00# ls
ls: error
sh-3.00$ ls
ls: error while loading shared libraries: /usr/lib/librt.so.1: ELF
file OS ABI invalid
sh-3.00$
Sothat don't seem right. How do I get
/compat/linux/bin/sh to work right? New .shrc file? Something I
missed?
[EMAIL PROTECTED] ~]$ /compat/linux/bin/sh
sh-
I think I have a major problem with my linux compatibility. It
started when a third party setup program complained about ELF ABI
types on a shared library, so I did a little experiment:
> /compat/linux/bin/sh
sh-3.00$ ls
ls: error while loading shared libraries: /usr/lib/librt.so.1: ELF
file OS A
On Fri, 16 Mar 2007, Jonathan Horne wrote:
i recently switched from KDE to XFCE4. underneath, i also switch my DM from
kdm to slim. now that slim is operating, my paths have changed significantly
when i log in via the GUI login. my current paths:
[EMAIL PROTECTED] ~]$ echo $PATH
./:/bin:/u
i recently switched from KDE to XFCE4. underneath, i also switch my DM from
kdm to slim. now that slim is operating, my paths have changed significantly
when i log in via the GUI login. my current paths:
[EMAIL PROTECTED] ~]$ echo $PATH
./:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
conversl
On Friday 31 March 2006 13:44, Gary Schenk wrote:
> Beech Rintoul wrote:
> > On Friday 31 March 2006 13:28, Gary Schenk wrote:
> >> OK, guys, I need help. what obvious thing am I missing here.
> >>
> >> Fresh install of seamonkey from a fresh ports update. I try to start
> >>
> >> seamonkey:
> >>
Beech Rintoul wrote:
On Friday 31 March 2006 13:28, Gary Schenk wrote:
OK, guys, I need help. what obvious thing am I missing here.
Fresh install of seamonkey from a fresh ports update. I try to start
seamonkey:
> seamonkey
seamonkey: Command not found.
OK. Now this:
> /usr/X11R6/bin/seamo
On Friday 31 March 2006 13:28, Gary Schenk wrote:
> OK, guys, I need help. what obvious thing am I missing here.
>
> Fresh install of seamonkey from a fresh ports update. I try to start
>
> seamonkey:
> > seamonkey
>
> seamonkey: Command not found.
>
> OK. Now this:
> > /usr/X11R6/bin/seamonkey
>
Gary Schenk wrote:
OK, guys, I need help. what obvious thing am I missing here.
Fresh install of seamonkey from a fresh ports update. I try to start
seamonkey:
> seamonkey
seamonkey: Command not found.
OK. Now this:
> /usr/X11R6/bin/seamonkey
Seamonkey starts.
OK, must be the path:
> ec
OK, guys, I need help. what obvious thing am I missing here.
Fresh install of seamonkey from a fresh ports update. I try to start
seamonkey:
> seamonkey
seamonkey: Command not found.
OK. Now this:
> /usr/X11R6/bin/seamonkey
Seamonkey starts.
OK, must be the path:
> echo $PATH
/sbin:/bin:/us
"Tom Vollmer" <[EMAIL PROTECTED]> writes:
> is a CODE 1 and the other two error lines indicate that
> "../../dev/fxp/if_fxp.c" and "../../sys/pci/if.sis.c" do not exists. When
> perform a "Find" to locate the files, they appear to be in the correct place
> in the file system. Can a source file m
Tom Vollmer wrote:
Whomever-
During the process of compiling my own kernel, I have an issue of the make
utility not being able to find "if_fxp.c" and "if_sis.c". Both exist in the
appropriate place in the file system. The version of freeBSD I am using is
4.6". Any suggestions?
It sounds li
"Tom Vollmer" <[EMAIL PROTECTED]> writes:
> Whomever-
>
> During the process of compiling my own kernel, I have an issue of the make
> utility not being able to find "if_fxp.c" and "if_sis.c". Both exist in the
> appropriate place in the file system. The version of freeBSD I am using is
> 4.6".
Whomever-
During the process of compiling my own kernel, I have an issue of the make
utility not being able to find "if_fxp.c" and "if_sis.c". Both exist in the
appropriate place in the file system. The version of freeBSD I am using is
4.6". Any suggestions?
Tom Vollmer
To Unsubscribe: send
32 matches
Mail list logo
