octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #33018] ./configure considered broken


From: Reginald Beardsley
Subject: [Octave-bug-tracker] [bug #33018] ./configure considered broken
Date: Sun, 10 Apr 2011 23:31:39 +0000
User-agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.8) Gecko/20101031 Firefox/3.6.8

Follow-up Comment #27, bug #33018 (project octave):

John,

It's not reproducible and I'd deleted the work area I used.  I've been
building other stuff, so configure sees a different environment.  Strangely
tar-1.26 still has the problem.

The assembler emits a message about the temporary .s file:

 ".align test amount has a negative value"

It's not a message I've ever seen before and I'm not interested enough to
chase it down.  I've gotten very used to certain releases of Gnu software
don't work.  I have no reason to prefer an uncompilable tar-1.26 over a
compilable tar-1.25.  If that changes I'll look into it.

As far as I'm concerned, at this time the mktime.c error is just background
noise.  I don't care about stuff like that after spending 50+ hours battling
autoconf & frenemies.   Once I can compile the whole thing, I'm quite happy to
do it all over again and document what the fixes were.  So far I'm not even
close because Octave wants to create a shared library the same way it creates
an executable.  That's wrong by inspection, but despite an absurd amount of
work, I can't find why because the instructions get rewritten on the fly more
times than I can count.

Just for reference I took a job once taking over support for 1.25 million
lines of X/Motif code that some other people had written.  Two of them still
worked for the company.  It took me 6 weeks to track down all the undefined
references and write working Makefiles for all of it.  I had to run find & nm
across pretty much the entire filesystem.  I rather suspect that if you build
out a new system and try to build Octave, you'll find it doesn't work the way
it does on your regular system.  Hopefully I'm wrong, but I can't see any way
that the arguments passed to libtool to create a shared library can be correct
on any system.  Every time that it tried to create a shared library it tried
to include a very large pile of redundant objects.  We know it's not libtool,
because the problem is not w/ libtool, but the arguments passed to it.

I want to take a break from this for a week or so.  I'll let you know when I
look into it again.

Regards,
Reg


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?33018>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]