Re: [OctDev] Trying to compile from source and running into an issue

On Tue, Sep 16, 2008 at 11:46 PM, Joseph Norris <[EMAIL PROTECTED]> wrote: > Just about there and then: > > -lreadline -lncurses -ldl -lz -lm -L/export/apps/octave/lib/ > -L/usr/lib/gcc/x86_64-redhat-linux/3.4.6 > -L/usr/lib/gcc/x86_64-redhat-linux/3.4.6/../../../../lib64 > -L/usr/lib/gcc/x86_64-

Re: [OctDev] Trying to compile from source and running into an issue

Just about there and then: -lreadline -lncurses -ldl -lz -lm -L/export/apps/octave/lib/ -L/usr/lib/gcc/x86_64-redhat-linux/3.4.6 -L/usr/lib/gcc/x86_64-redhat-linux/3.4.6/../../../../lib64 -L/usr/lib/gcc/x86_64-redhat-linux/3.4.6/../../.. -L/lib/../lib64 -L/usr/lib/../lib64 -lz -lfrtbegin -l

Re: [OctDev] Trying to compile from source and running into an issue

Well almost: /x86_64-redhat-linux/3.4.6/../../.. -L/lib/../lib64 -L/usr/lib/../lib64 -lz -lfrtbegin -lg2c -lm /usr/bin/ld: /export/apps/octave/lib//libcolamd.a(colamd.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /export/ap

Re: [OctDev] Trying to compile from source and running into an issue

On Tue, Sep 16, 2008 at 7:04 PM, Joseph Norris <[EMAIL PROTECTED]> wrote: > Hello, > > I got all of the libraries in place - did the configure then make and I > get to this: > > /usr/bin/ld: > /usr/lib/gcc/x86_64-redhat-linux/3.4.6/../../../../lib64/libf77blas.a(sgbmv.o): > relocation R_X86_64_32 a

[OctDev] Trying to compile from source and running into an issue

Hello, I got all of the libraries in place - did the configure then make and I get to this: /usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/3.4.6/../../../../lib64/libf77blas.a(sgbmv.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with

[OctDev] Silent uninstall of windows octave 3.0.1 ?

Hi all, I have just been setting up Octave for one of our computer labs, and I can get in installed without any user input, but the nsis uninstaller pops up two dialog boxes, even when it is invoked with /S. Does anyone have a nice workaround ? Can I ask nicely that the windows packagers look at

Re: [OctDev] Broken Release Process [was: Re: Displaying an animation / "movie"]

Am Dienstag, den 16.09.2008, 11:32 +0200 schrieb [EMAIL PROTECTED]: > Quoting Thomas Weber <[EMAIL PROTECTED]>: > > Eh, I'm thinking more of: > > 1) Maintainer commits a "Release PACKAGE" message, with PACKAGE the > > package's name. A commit hook in the version control system checks each > > commi

Re: [OctDev] Broken Release Process [was: Re: Displaying an animation / "movie"]

Quoting Thomas Weber <[EMAIL PROTECTED]>: > Eh, I'm thinking more of: > 1) Maintainer commits a "Release PACKAGE" message, with PACKAGE the > package's name. A commit hook in the version control system checks each > commit message for such a phrase and triggers a package build *on the > server* and

Re: [OctDev] Broken Release Process [was: Re: Displaying an animation / "movie"]

Am Dienstag, den 16.09.2008, 10:54 +0200 schrieb [EMAIL PROTECTED]: > Moving this to Octave-Forge mailing list from [EMAIL PROTECTED] > > Quoting Thomas Weber <[EMAIL PROTECTED]>: > > I don't intend to add any more octave-forge packages to Debian until > > octave-forge's release process is fixed (

[OctDev] Broken Release Process [was: Re: Displaying an animation / "movie"]

Moving this to Octave-Forge mailing list from [EMAIL PROTECTED] Quoting Thomas Weber <[EMAIL PROTECTED]>: > I don't intend to add any more octave-forge packages to Debian until > octave-forge's release process is fixed (and yes, it currently is > broken). > > By "fixed" I mean that: > 1) Packages