I'm trying to upgrade from -stable to 5, but the build failed at rtld-elf.
One error and a whole lot of warnings. I don't know where I should start as
I'm new to current (even though it's technically not -current). I swear I
followed the instructions in UPGRADING. Any help would be greatly
recent changes to either file. Any ideas on what was going on?
Thanks again,
Evan Dower
From: Evan Dower [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: buildworld failure, rtld-elf, RELENG_5_0
Date: Thu, 23 Jan 2003 00:17:14 -0800
I'm trying to upgrade from -stable to 5, but the build failed at rtld
On Thu, Jan 23, 2003 at 09:15:24AM -0800, Evan Dower wrote:
An update:
CVSup'ing didn't fix the problem, but when I deleted the rtld.c and mv'd
/etc/make.conf /etc/make.conf.hide, it stopped at
/usr/src/contrib/amd/amd/srvr_nfs.c. So, I deleted that file, CVSup'd, and
built again, and
On Thu, 13 Jun 2002, Alex Zepeda wrote:
On Thu, Jun 13, 2002 at 12:26:05PM +1000, Bruce Evans wrote:
rtld still uses asms with the old, broken/fragile 0 constraint. This
constraint is especially broken/fragile if things are pessimized by
compiling without optimizations.
D'oh!
Is
On Fri, Jun 14, 2002 at 07:09:06PM +1000, Bruce Evans wrote:
Not really. It is a transient bug that is almost as easy to fix as
warn about.
So when can I expect the fix to be committed? :-D
- alex
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
On Thu, Jun 13, 2002 at 12:26:05PM +1000, Bruce Evans wrote:
rtld still uses asms with the old, broken/fragile 0 constraint. This
constraint is especially broken/fragile if things are pessimized by
compiling without optimizations.
D'oh!
Is there any chance of sticking a warning in the
Alex Zepeda wrote:
On Thu, Jun 13, 2002 at 12:26:05PM +1000, Bruce Evans wrote:
rtld still uses asms with the old, broken/fragile 0 constraint. This
constraint is especially broken/fragile if things are pessimized by
compiling without optimizations.
D'oh!
Is there any chance of
* Terry Lambert [EMAIL PROTECTED] escriurères
Alex Zepeda wrote:
On Thu, Jun 13, 2002 at 12:26:05PM +1000, Bruce Evans wrote:
rtld still uses asms with the old, broken/fragile 0 constraint. This
constraint is especially broken/fragile if things are pessimized by
compiling without
Juli Mallett wrote:
Errr, it was with 0 level optimisation that is the problem, not a real
level. Read carefully what bde said, and look at hte warnings and how
GCC deals with the code in question.
Also, your example is very wrong, read make(1)'s section on dealing with
variables.
I
* Terry Lambert [EMAIL PROTECTED] escriurères
Juli Mallett wrote:
Errr, it was with 0 level optimisation that is the problem, not a real
level. Read carefully what bde said, and look at hte warnings and how
GCC deals with the code in question.
Also, your example is very wrong, read
So what's up with -current?
I had to install gawk to get the kernel to build (and world too for that
matter).. I haven't had the balls to put the one true awk back in place.
But now whether in world mode or not I get:
blarf:/usr/src/libexec/rtld-elf#make
cc -O0 -Wall -DFREEBSD_ELF -I/usr/src
-elf#make
cc -O0 -Wall -DFREEBSD_ELF -I/usr/src/libexec/rtld-elf/i386
^^^
-I/usr/src/libexec/rtld-elf -elf -fpic -DPIC -Wformat=2
-Wno-format-extra-args -c /usr/src/libexec/rtld-elf/rtld.c
/usr/src/libexec/rtld-elf/rtld.c: In function `atomic_decr_int':
/usr/src/libexec/rtld-elf/i386
On Thu, Jan 24, 2002 at 01:25:54PM +, David Malone wrote:
Cool, thanks!
Bruch pointed out that we still have a small problem with the man
page. Both brk and sbrk are now library functions, but their man
page is still in section 2.
Hmm, I see.
The proper fix would be to repo-copy
=== libexec/rtld-elf
chflags noschg /usr/libexec/ld-elf.so.1
chflags noschg /usr/libexec/ld-elf.so.1.old
cp -p /usr/libexec/ld-elf.so.1 /usr/libexec/ld-elf.so.1.old
cp:No such file or directory
*** Error code 1
Stop in /usr/src/libexec/rtld-elf.
*** Error code 1
Stop in /usr/src/libexec
Alfred Perlstein wrote:
=== libexec/rtld-elf
chflags noschg /usr/libexec/ld-elf.so.1
chflags noschg /usr/libexec/ld-elf.so.1.old
cp -p /usr/libexec/ld-elf.so.1 /usr/libexec/ld-elf.so.1.old
cp:No such file or directory
*** Error code 1
I think we need to copy 'cp' in installworld as well
In article [EMAIL PROTECTED],
Alfred Perlstein [EMAIL PROTECTED] wrote:
=== libexec/rtld-elf
chflags noschg /usr/libexec/ld-elf.so.1
chflags noschg /usr/libexec/ld-elf.so.1.old
cp -p /usr/libexec/ld-elf.so.1 /usr/libexec/ld-elf.so.1.old
cp:No such file or directory
^
|
Why
* John Polstra [EMAIL PROTECTED] [000719 17:45] wrote:
In article [EMAIL PROTECTED],
Alfred Perlstein [EMAIL PROTECTED] wrote:
=== libexec/rtld-elf
chflags noschg /usr/libexec/ld-elf.so.1
chflags noschg /usr/libexec/ld-elf.so.1.old
cp -p /usr/libexec/ld-elf.so.1 /usr/libexec/ld-elf.so
Alfred Perlstein wrote:
I needed to add 'cp' to src/Makefile.inc1, Marcel explained it to me
Oh, so it was "cp" that wasn't found, I take it. We should change
the message in make so it's more like what shells say ("command not
found").
but I'm sorry I did, -current is terribly broken. I
* John Polstra [EMAIL PROTECTED] [000719 18:32] wrote:
Alfred Perlstein wrote:
I needed to add 'cp' to src/Makefile.inc1, Marcel explained it to me
Oh, so it was "cp" that wasn't found, I take it. We should change
the message in make so it's more like what shells say ("command not
new copies from scratch. I did a make world and the compile finished
successfully.
I am using dual PPro-200
- Original Message -
From: "John Polstra" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, July 15, 2000 5:34 PM
Subject: Re: rtld-elf
[Wh
In article 000c01bfeef3$8c71b8f0$[EMAIL PROTECTED],
Tony Johnson [EMAIL PROTECTED] wrote:
So on Friday Morning, I deleted all my cvs source code and cvsup
all new copies from scratch. I did a make world and the compile
finished successfully.
Whew, you had me worried for awhile there.
with =
freebsd-5.0. The install breaks with rtld-elf when the install put the =
new copy of ld-elf.s0.1 onto my system. Most f my prgrams signal 11 =
until I put the old ne back. Is there smething I was supposed t do =
befre this??
Yours is the only trouble report I've seen for the new version
Hmmm.. I have been experiencing a problem when I
installworld with freebsd-5.0. The install breaks with rtld-elf when the
install put the new copy of ld-elf.s0.1 onto my system. Most f my prgrams
signal 11 until I put the old ne back. Is there smething I was supposed t
do befre this??
In article [EMAIL PROTECTED],
Max Khon [EMAIL PROTECTED] wrote:
Seems that this patch fixed the problem for me.
I can not reproduce it anymore.
That's good news. Thanks for testing it! I'll commit it later
today.
John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
In article [EMAIL PROTECTED],
Max Khon [EMAIL PROTECTED] wrote:
applet_viewer bombs out with a lot of stuff in the output like this
(until killed -9):
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
The last time this problem happened (I thought I fixed
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
If any of you can reproduce this problem fairly reliably, please try
the appended patch for "src/libexec/rtld-elf/lockdflt.c" and let me
know if it solves the problem.
Thanks,
John
Index:
hi, there!
On Sun, 23 Jan 2000, John Polstra wrote:
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
If any of you can reproduce this problem fairly reliably, please try
the appended patch for "src/libexec/rtld-elf/lockdflt.c" and let me
know if it solves t
hi, there!
applet_viewer bombs out with a lot of stuff in the output like this
(until killed -9):
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf
On Fri, Jan 21, 2000 at 06:42:51PM +0600, Max Khon wrote:
hi, there!
applet_viewer bombs out with a lot of stuff in the output like this
(until killed -9):
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c
In article [EMAIL PROTECTED],
Max Khon [EMAIL PROTECTED] wrote:
hi, there!
applet_viewer bombs out with a lot of stuff in the output like this
(until killed -9):
ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55
Really?! Augh. Naturally this comes just hours after I
I've seen it with yesterdays current and libc_r threads, and it's intermittent.
Russell
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In article [EMAIL PROTECTED],
Russell L. Carter [EMAIL PROTECTED] wrote:
I've seen it with yesterdays current and libc_r threads, and it's intermittent.
Did this problem just start, or has it been there for awhile? I
haven't changed the dynamic linker in -current since January 9, and
I'm
I am fairly certain that Java + TYA worked before Jan 7 -- haven't
upgraded my system since then.
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
|From [EMAIL PROTECTED] Fri Jan 21 11:23:14 2000
|
|In article [EMAIL PROTECTED],
|Russell L. Carter [EMAIL PROTECTED] wrote:
| I've seen it with yesterdays current and libc_r threads, and it's intermittent.
|
|Did this problem just start, or has it been there for awhile? I
|haven't changed the
In article [EMAIL PROTECTED],
Amancio Hasty [EMAIL PROTECTED] wrote:
I am fairly certain that Java + TYA worked before Jan 7 -- haven't
upgraded my system since then.
Yes, that assert that failed wasn't in the dynamic linker on January
7. What I need to know is: did it start failing soon
hi, there!
On Fri, 21 Jan 2000, John Polstra wrote:
Really?! Augh. Naturally this comes just hours after I have merged
the latest changes into -stable *sigh*.
Could you please make sure your src/libexec/rtld-elf is
up-to-date? rtld.c should be at revision 1.41.
yes. my src/libexec
36 matches
Mail list logo
