On Tue, Jun 29, 2010 at 01:26:23PM +0200, Dag-Erling Smørgrav wrote:
> Anton Shterenlikht writes:
> > However, I've got this set on 3 ia64 boxes.
> > On two of them I don't have this lzma problem.
>
> Because they either don't have liblzma installed from ports, or they
> have a different version
Anton Shterenlikht writes:
> However, I've got this set on 3 ia64 boxes.
> On two of them I don't have this lzma problem.
Because they either don't have liblzma installed from ports, or they
have a different version that works.
DES
--
Dag-Erling Smørgrav - d...@des.no
__
2010/6/29 Anton Shterenlikht :
> On Tue, Jun 29, 2010 at 12:03:39PM +0200, Dag-Erling Smørgrav wrote:
>> Anton Shterenlikht writes:
>> > # make buildenv
>> > Entering world for ia64:ia64
>> > # env
>> > LIBRARY_PATH=/usr/local/lib
>>
>> where does this come from? Your .bashrc or something?
>
> I'
On Tue, Jun 29, 2010 at 12:03:39PM +0200, Dag-Erling Smørgrav wrote:
> Anton Shterenlikht writes:
> > # make buildenv
> > Entering world for ia64:ia64
> > # env
> > LIBRARY_PATH=/usr/local/lib
>
> where does this come from? Your .bashrc or something?
I've this set in $HOME/.tcsh. I don't rememb
On 2010-06-29 11:59, Anton Shterenlikht wrote:
> LIBRARY_PATH=/usr/local/lib
There's your problem. Remove this environment variable, and try
buildworld again. :)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
Anton Shterenlikht writes:
> # make buildenv
> Entering world for ia64:ia64
> # env
> LIBRARY_PATH=/usr/local/lib
where does this come from? Your .bashrc or something?
% make buildenv
% unset LIBRARY_PATH
then run the cc command again.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
Dag-Erling Smørgrav writes:
> This confirms my suspicion that ld is picking up the wrong liblzma:
> > attempt to open /usr/local/lib/liblzma.a succeeded
> but I still can't figure out why.
Uh, I must be blind. It uses /usr/local/lib/liblzma.a because
-L/usr/local/lib was specified on the command
On Tue, Jun 29, 2010 at 11:25:40AM +0200, Dag-Erling Smørgrav wrote:
> Anton Shterenlikht writes:
> > http://seis.bris.ac.uk/~mexas/ia64-lzma-problem.txt
>
> This confirms my suspicion that ld is picking up the wrong liblzma:
>
> > attempt to open /usr/local/lib/liblzma.a succeeded
>
> but I st
On 2010-06-29 11:25, Dag-Erling Smørgrav wrote:
> Anton Shterenlikht writes:
>> http://seis.bris.ac.uk/~mexas/ia64-lzma-problem.txt
>
> This confirms my suspicion that ld is picking up the wrong liblzma:
>
>> attempt to open /usr/local/lib/liblzma.a succeeded
>
> but I still can't figure out wh
Anton Shterenlikht writes:
> http://seis.bris.ac.uk/~mexas/ia64-lzma-problem.txt
This confirms my suspicion that ld is picking up the wrong liblzma:
> attempt to open /usr/local/lib/liblzma.a succeeded
but I still can't figure out why. Can you do the following:
% make buildenv
% env
and also
On Mon, Jun 28, 2010 at 06:39:29PM +0200, Dag-Erling Smørgrav wrote:
> Anton Shterenlikht writes:
> > I think this only happens when I copy from one xterm to another,
> > to paste into the mailer. I've checked the command which
> > I put in a file, and all seems fine. Also, the latest
> > error me
Anton Shterenlikht writes:
> I think this only happens when I copy from one xterm to another,
> to paste into the mailer. I've checked the command which
> I put in a file, and all seems fine. Also, the latest
> error message suggests that the command is fine:
OK, can you do it again with -Wl,--ve
On Mon, Jun 28, 2010 at 03:58:35PM +0200, Dag-Erling Smørgrav wrote:
> Anton Shterenlikht writes:
> > cc -v -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo
> > date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo
> > kill.lo ln.lo ls.lo mkdir.lo mv.lo pkil
Anton Shterenlikht writes:
> cc -v -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo
> date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo
> kill.lo ln.lo ls.lo mkdir.lo mv.lo pkill.lo ps.lo pwd.lo ealpath.lo rm.lo
> rmdir.lo setfacl.lo sh.lo stty.lo sync
On Mon, Jun 28, 2010 at 02:38:10PM +0200, Dag-Erling Smørgrav wrote:
> Anton Shterenlikht writes:
> > # cc -v -static -o rescue [...]
> > cc: cat.lo: No such file or directory
>
> Umm, try again from the object directory, /usr/obj/usr/src/rescue/rescue/
that's better:
# cd /usr/src/
# make buil
Anton Shterenlikht writes:
> # cc -v -static -o rescue [...]
> cc: cat.lo: No such file or directory
Umm, try again from the object directory, /usr/obj/usr/src/rescue/rescue/
> # /usr/obj/usr/src/rescue/rescue/../librescue/exec.o: Permission
> denied
That's weird, can you check the ownership of
On Fri, Jun 25, 2010 at 11:47:59AM +0200, Dag-Erling Smørgrav wrote:
> Anton Shterenlikht writes:
> > So, just for me to be clear, I need to proceed with the buildworld,
> > until I get the error, and then, without cleaning anything, do
> >
> > % cd /usr/src
> > % make buildenv
> > % cd rescue/res
On Sun, Jun 27, 2010 at 10:45:21PM +0200, Dag-Erling Smørgrav wrote:
> Garrett Cooper writes:
> > Sorry to jump in, but could you please copy your source tree on
> > the failing machine elsewhere, run make clean cleandir, and try
> > applying the patch attached to the post below [1] and see wh
Garrett Cooper writes:
> Sorry to jump in, but could you please copy your source tree on
> the failing machine elsewhere, run make clean cleandir, and try
> applying the patch attached to the post below [1] and see whether or
> not the issue is resolved?
Umm... the error you got was complete
2010/6/25 Anton Shterenlikht :
> On Thu, Jun 24, 2010 at 05:50:59PM +0200, Dag-Erling Smørgrav wrote:
>> Anton Shterenlikht writes:
>> > Dag-Erling Smørgrav writes:
>> > > I expect this to produce the same error as before; if not, there is
>> > > something seriously wrong.
>> > the error is diffe
Anton Shterenlikht writes:
> So, just for me to be clear, I need to proceed with the buildworld,
> until I get the error, and then, without cleaning anything, do
>
> % cd /usr/src
> % make buildenv
> % cd rescue/rescue
> % make
>
> Is that correct?
Yes. Then you take the cc comand line that fail
On Thu, Jun 24, 2010 at 05:50:59PM +0200, Dag-Erling Smørgrav wrote:
> Anton Shterenlikht writes:
> > Dag-Erling Smørgrav writes:
> > > I expect this to produce the same error as before; if not, there is
> > > something seriously wrong.
> > the error is different...
> >
> > echo fsck_ffs: /usr/li
On Jun 24, 2010, at 8:53 AM, Dag-Erling Smørgrav wrote:
> Marcel Moolenaar writes:
>> Can check if you have /usr/local/lib/liblzma on your other machines. I
>> have this nagging feeling that you're picking up a library outside of
>> your object tree.
>
> That's what I'm working my way towards,
Marcel Moolenaar writes:
> Can check if you have /usr/local/lib/liblzma on your other machines. I
> have this nagging feeling that you're picking up a library outside of
> your object tree.
That's what I'm working my way towards, Marcel. Can you wait until
Anton has answered my questions.
DES
-
Anton Shterenlikht writes:
> Dag-Erling Smørgrav writes:
> > I expect this to produce the same error as before; if not, there is
> > something seriously wrong.
> the error is different...
>
> echo fsck_ffs: /usr/lib/libc.a /usr/lib/libufs.a >> .depend
> cc -O1 -I/usr/src/sbin/fsck_ffs -I/usr/src
On Thu, Jun 24, 2010 at 08:16:52AM -0700, Marcel Moolenaar wrote:
> Sorry for the top post:
>
> Anton,
>
> Can check if you have /usr/local/lib/liblzma on your other machines. I have
> this nagging feeling that you're picking up a library outside of your object
> tree.
Marcel
On as28 and as22
Sorry for the top post:
Anton,
Can check if you have /usr/local/lib/liblzma on your other machines. I have
this nagging feeling that you're picking up a library outside of your object
tree.
Also: can you send the contents of /etc/make.conf
Thx
--
Marcel (Mobile)
On Jun 24, 2010, at 1:36 A
On Thu, Jun 24, 2010 at 02:58:12PM +0200, Dag-Erling Smørgrav wrote:
> Anton Shterenlikht writes:
> > *startfile_prefix_spec:
> > /usr/obj/usr/src/tmp/usr/lib/
>
> OK
>
> % cd /usr/src
> % make buildenv
> % cd rescue/rescue
> % make
>
> I expect this to produce the same error as before; if not,
On Thu, Jun 24, 2010 at 11:30:28AM +0200, Dimitry Andric wrote:
> On 2010-06-24 10:26, Anton Shterenlikht wrote:
> > I got a clean copy of r209203, and got the same error on buildworld:
> >
> > cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo
> > date.lo dd.lo df.lo echo.lo
Anton Shterenlikht writes:
> *startfile_prefix_spec:
> /usr/obj/usr/src/tmp/usr/lib/
OK
% cd /usr/src
% make buildenv
% cd rescue/rescue
% make
I expect this to produce the same error as before; if not, there is
something seriously wrong.
Now copy the last command make tried to run (cc -static
Anton Shterenlikht writes:
> Dag-Erling Smørgrav writes:
> > Anton Shterenlikht writes:
> > > Did you mean /usr/local/lib/liblzma.a ?
> > No, I meant /usr/lib/liblzma.a.
> This file doesn't exist on either of my other two ia64 boxes, where
> this problem is not present.
I still meant /usr/lib/l
On Thu, Jun 24, 2010 at 11:57:26AM +0100, Anton Shterenlikht wrote:
> On Thu, Jun 24, 2010 at 11:11:22AM +0200, Dag-Erling Smørgrav wrote:
> > Anton Shterenlikht writes:
> > > # find /usr/obj/usr/src -name liblzma.a
> > > /usr/obj/usr/src/tmp/usr/lib/liblzma.a
> > > /usr/obj/usr/src/lib/liblzma/li
On Thu, Jun 24, 2010 at 12:31:48PM +0200, Dag-Erling Smørgrav wrote:
> Dag-Erling Smørgrav writes:
> > On a machine where make buildworld failed, do
> >
> > % cd /usr/src
> > % make buildenv
> > % echo $PATH
> > % which cc
> > % cc --version
> > % strings $(which cc) | grep -w tmp
>
> instead of
On Thu, Jun 24, 2010 at 11:11:22AM +0200, Dag-Erling Smørgrav wrote:
> Anton Shterenlikht writes:
> > # find /usr/obj/usr/src -name liblzma.a
> > /usr/obj/usr/src/tmp/usr/lib/liblzma.a
> > /usr/obj/usr/src/lib/liblzma/liblzma.a
> > # diff /usr/obj/usr/src/tmp/usr/lib/liblzma.a
> > /usr/obj/usr/sr
Dag-Erling Smørgrav writes:
> On a machine where make buildworld failed, do
>
> % cd /usr/src
> % make buildenv
> % echo $PATH
> % which cc
> % cc --version
> % strings $(which cc) | grep -w tmp
instead of that last line:
% cc -dumpspecs
(still in buildenv)
DES
--
Dag-Erling Smørgrav - d...@d
Anton Shterenlikht writes:
> # find /usr/obj/usr/src -name liblzma.a
> /usr/obj/usr/src/tmp/usr/lib/liblzma.a
> /usr/obj/usr/src/lib/liblzma/liblzma.a
> # diff /usr/obj/usr/src/tmp/usr/lib/liblzma.a
> /usr/obj/usr/src/lib/liblzma/liblzma.a
> #
> # nm /usr/obj/usr/src/lib/liblzma/liblzma.a | grep
On Wed, Jun 23, 2010 at 04:20:18PM +0200, Dag-Erling Smørgrav wrote:
> Anton Shterenlikht writes:
> > I think it's possible that at some point, in anger, I did "make
> > installworld" after a failed, or otherwise interrupted "make
> > buildworld". Perhaps I got an inconsistent set of binaries as a
On Mon, Jun 21, 2010 at 06:36:44PM +0200, Dag-Erling Smørgrav wrote:
> Anton Shterenlikht writes:
> > I've r209203 kernel on ia64 box.
> > Now I'm trying to rebuild world to r209240.
> > I get these errors.
>
> There is absolutely nothing between those two revisions that would
> explain the error
Anton Shterenlikht writes:
> I think it's possible that at some point, in anger, I did "make
> installworld" after a failed, or otherwise interrupted "make
> buildworld". Perhaps I got an inconsistent set of binaries as a
> result... Would that explain an error like this?
No, because at this poi
On Mon, Jun 21, 2010 at 01:27:52PM -0700, Marcel Moolenaar wrote:
>
> On Jun 21, 2010, at 8:04 AM, Anton Shterenlikht wrote:
>
> > On Mon, Jun 21, 2010 at 04:45:03PM +0200, Dag-Erling Smørgrav wrote:
> >> jhell writes:
> >>> Anton Shterenlikht writes:
> What do you mean by "updating your h
On Jun 21, 2010, at 8:04 AM, Anton Shterenlikht wrote:
> On Mon, Jun 21, 2010 at 04:45:03PM +0200, Dag-Erling Smørgrav wrote:
>> jhell writes:
>>> Anton Shterenlikht writes:
What do you mean by "updating your headers"?
>>> cd /usr/src/include && make obj && make depend && make all && make
On 06/21/2010 13:47, Dag-Erling Smørgrav wrote:
> jhell writes:
>> As to the point before you start pointing fingers as you are so gracious
>> to do lately - The steps laid out are the steps I had once took to
>> correct the similar problem. And I seem to be running on these systems
>> fairly well
jhell writes:
> As to the point before you start pointing fingers as you are so gracious
> to do lately - The steps laid out are the steps I had once took to
> correct the similar problem. And I seem to be running on these systems
> fairly well mind you.
They are still wrong, and they will not so
On 06/21/2010 12:25, Dag-Erling Smørgrav wrote:
> jhell writes:
>> Sure, the only difference here is you just seem to have added
>> cleandepend for extra added surety but is unneeded if the obj
>> directory is assumed empty.
>
> Assumption is the mother of all f***ups. The mother of your particu
Anton Shterenlikht writes:
> I've r209203 kernel on ia64 box.
> Now I'm trying to rebuild world to r209240.
> I get these errors.
There is absolutely nothing between those two revisions that would
explain the errors you're getting. Are you absolutely sure those are
the correct revision numbers?
On 06/21/2010 11:59, Anton Shterenlikht wrote:
> On Mon, Jun 21, 2010 at 04:45:03PM +0200, Dag-Erling Smørgrav wrote:
>> jhell writes:
>>> Anton Shterenlikht writes:
What do you mean by "updating your headers"?
>>> cd /usr/src/include && make obj && make depend && make all && make install
>>
Anton Shterenlikht writes:
> this failed in "make depend" step with
you can skip that step... in fact, you can skip the whole thing, since
it is completely irrelevant to your case. I'll go check the archives
for your OP and see if I can provide some more useful advice than jhell.
DES
--
Dag-E
2010/6/21 Anton Shterenlikht :
> On Mon, Jun 21, 2010 at 04:45:03PM +0200, Dag-Erling Smørgrav wrote:
>> jhell writes:
>> > Anton Shterenlikht writes:
>> > > What do you mean by "updating your headers"?
>> > cd /usr/src/include && make obj && make depend && make all && make install
>>
>> wrong.
>
jhell writes:
> Sure, the only difference here is you just seem to have added
> cleandepend for extra added surety but is unneeded if the obj
> directory is assumed empty.
Assumption is the mother of all f***ups. The mother of your particular
f***up is the assumption that all headers are in /usr
Anton Shterenlikht writes:
> Sorry, just to take one step back, why has this become necessary for
> this particular box?
I have no idea or opinion - I just responded to jhell's incorrect
instructions for "updating your headers".
> If /usr/obj is empty, and "svn up", followed by "svn diff", doesn
On Mon, Jun 21, 2010 at 04:45:03PM +0200, Dag-Erling Smørgrav wrote:
> jhell writes:
> > Anton Shterenlikht writes:
> > > What do you mean by "updating your headers"?
> > cd /usr/src/include && make obj && make depend && make all && make install
>
> wrong.
>
> % cd /usr/src
> % make obj
> % mak
On Mon, Jun 21, 2010 at 11:24:52AM -0400, jhell wrote:
> On 06/21/2010 10:45, Dag-Erling Smørgrav wrote:
> > jhell writes:
> >> Anton Shterenlikht writes:
> >>> What do you mean by "updating your headers"?
> >> cd /usr/src/include && make obj && make depend && make all && make install
> >
> > wr
On 06/21/2010 10:45, Dag-Erling Smørgrav wrote:
> jhell writes:
>> Anton Shterenlikht writes:
>>> What do you mean by "updating your headers"?
>> cd /usr/src/include && make obj && make depend && make all && make install
>
> wrong.
>
> % cd /usr/src
> % make obj
> % make cleandepend
> % make de
On Mon, Jun 21, 2010 at 04:45:03PM +0200, Dag-Erling Smørgrav wrote:
> jhell writes:
> > Anton Shterenlikht writes:
> > > What do you mean by "updating your headers"?
> > cd /usr/src/include && make obj && make depend && make all && make install
>
> wrong.
>
> % cd /usr/src
> % make obj
> % mak
jhell writes:
> Anton Shterenlikht writes:
> > What do you mean by "updating your headers"?
> cd /usr/src/include && make obj && make depend && make all && make install
wrong.
% cd /usr/src
% make obj
% make cleandepend
% make depend
% make buildincludes
% make installincludes
DES
--
Dag-Erli
On 06/18/2010 04:50, Anton Shterenlikht wrote:
>
> sorry, I probably didn't get you.
>
> I tried
>
> make -DALWAYS_CHECK_MAKE buildworld
>
> and got the same erorr.
>
> What do you mean by "updating your headers"?
cd /usr/src/include && make obj && make depend && make all && make instal
On Thu, Jun 17, 2010 at 08:13:46AM -0400, jhell wrote:
> On 06/17/2010 06:15, Anton Shterenlikht wrote:
> > I've r209203 kernel on ia64 box.
> > Now I'm trying to rebuild world to r209240.
> > I get these errors.
> >
> > Please advise
> >
>
> grep -rn lzma_physmem /usr/include ?
> /usr/include/l
On 06/17/2010 06:15, Anton Shterenlikht wrote:
> I've r209203 kernel on ia64 box.
> Now I'm trying to rebuild world to r209240.
> I get these errors.
>
> Please advise
>
grep -rn lzma_physmem /usr/include ?
/usr/include/lzma/hardware.h:51:extern LZMA_API(uint64_t)
lzma_physmem(void) lzma_nothrow
I've r209203 kernel on ia64 box.
Now I'm trying to rebuild world to r209240.
I get these errors.
Please advise
many thanks
anton
crunchide -k _crunched_vi_stub vi.lo
ld -dc -r -o id.lo id_stub.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/id/id.o
crunchide -k _crunched_id_stub id.lo
ld -dc
59 matches
Mail list logo