Wondering if anyone has encountered this problem where gdb/gcc doesn't
seem to be getting the line number info right.
I compiled code in as
--
gcc45 -g -W -Wall -O0 -std=c99 -D_BSD_SOURCE -DDEBUG -D__BSD_VISIBLE
-DFREEBSD -c
--
On Sun, Feb 27, 2011 at 07:30:38PM -0500, Eric Dedrick wrote:
Wondering if anyone has encountered this problem where gdb/gcc doesn't
seem to be getting the line number info right.
I compiled code
I'm having a nuisance problem, especially when I try to update my
ports. I'm using cups as an example, but other ports show the
problem:
root# pw usershow cups
pw: no such user `cups'
root# pw useradd cups -g cups -u 193
pw: user 'cups' already exists
Any idea what the problem is and how to fix
I'm running 4.8 and XF86 Version 4.2.1.
DPMS isn't working right on my new machine (ASUS A7A266 motherboard).
1. The monitor is capable of doing DPMS
2. DPMS works fine when the monitor is just displaying a text console
3. DPMS does not work from X
4. I have checked my /etc/X11/XF86Config
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Natd hasn't exactly been working as it used to either. Any idea what this
means?
Jul 24 23:26:43 dsl-146-127 /kernel: arp: 192.168.0.1 is on lo0 but got
reply from 00:04:76:b8:94:10 on ep0
Jul 24 23:28:17 dsl-146-127 /kernel: arp: 128.211.146.127 is on lo0 but
got reply from
It usually occurs when you have them all plugged into the same
circuit. My natd connection is connected to a switch connected to my
DSL modem. My internal NIC is connected to a switch where all of my
computers are connected. Natd works just fine.
The messages with lo0 makes me wonder if you
Do you have 192.168.0.1 as your default router on the other machines?
Apparently not. Thanks. That fixed it.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Just to clarify, I mean that using portupgrade will
(hopefully, and in my experience, almost always) take
care of your dependencies during the upgrade process,
thus saving you from the IMO less preferable
alternative of running more than one version of a
port.
Have you tried portupgrade
Yup. See the new attachements. Again, thank you so much for the help.
On Wed, 24 Jul 2002, Dan Nelson wrote:
In the last episode (Jul 24), Eric Dedrick said:
i'm going to have to ask that anybody else who knows please step in
here...
to know where it's dying, i'd need to see
oh wow i didn't notice that one.
run /compat/linux/sbin/ldconfig -p and see where it's looking for
ld-linux.so.2. the line should be something like:
ld-linux.so.2 (ELF) = /lib/ld-linux.so.2
but yeah, rebuild that kernel and modules!
I've rebuilt them so many times figuring that was the
11590 ktrace NAMI /compat/svr4/lib/ld-linux.so.2
Why does it think the binary is an svr4 binary? That's why the
syscalls still don't match and you get SIGSYS after a while. Something
sounds really out of sync.
That's kind of what I thought. I tried re-brandelf'ing my version of
uhmm you can always kludge by ln -s /compat/linux /compat/svr4 ::)
just curious... do you have anything in /compat/svr4?
A symbolic link to /usr/compat/linux/lib.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
but then it's looking for /usr/compat/linux/lib/lib/ld-linux.so.2
make /compat/svr4 - /compat/linux
No change.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
If you don't load the svr4 module (and don't have options COMPAT_SVR4
in your config file), it shouldn't look in /compat/svr4. Try removing
those and see what happens.
Symlinking /compat/svr4 to /compat/linux won't do a thing, since the
syscalls don't match.
I get:
$ opera
ELF
$ opera
ELF interpreter /compat/svr4/lib/ld-linux.so.2 not found
[1] 11964 Abort trap
Now that's really confusing. Without the svr4 module loaded, the
string /compat/svr4 should not exist anywhere in the kernel (it's
defined in /sys/svr4/svr4_sysvec.c). There is simply no way you
Getting a bit better, but now it looks like it thinks the binary is a
native BSD one instead of Linux. If you run file
/usr/local/opera/lib/opera/5.05_tp1/opera-static, what does it print?
$ file /usr/local/opera/lib/opera/5.05_tp1/opera-static
Date: Tue, 23 Jul 2002 10:52:49 -0500 (EST)
From: Eric Dedrick [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: linux compatability broken?
I recently made a few kernel changes so I remade world.
It would seem that linux compatability is now broken. At first things
were
i hope you have a semi-recent ports tree, because you need
linux_base-7.1.
installing linux_base 7.1 from the ports gives me the following error.
Advice? Thanks.
---
(several screen fulls of the same type of stuff)...
file /usr/share/zoneinfo/right/US/Eastern from install of
the old version of linux_base that you have. if
you don't know how to do that, you can always:
install /usr/ports/sysutils/portupgrade
then, do:
portupgrade -o emulators/linux_base linux_base-\*
that should take care of that.
-Adam
(07.23.2002 @ 2024 PST): Eric Dedrick said, in 1.4K:
i
20 matches
Mail list logo
