On Sat, Feb 28, 2009 at 10:24:56AM +0100, Ed Schouten wrote:
> * per...@pluto.rain.com wrote:
> > So perhaps one solution would be to compile libmp with -ffreestanding?
>
> And all applications that use .
which is a nonsense... plea
* per...@pluto.rain.com wrote:
> So perhaps one solution would be to compile libmp with -ffreestanding?
And all applications that use .
--
Ed Schouten
WWW: http://80386.nl/
pgpwD14uSm0Hj.pgp
Description: PGP signature
; ... it's invalid code to have a function named pow()
> > > in a hosted environment which is not /The/ pow().
> > ^^^
> >
> > I don't suppose LLVM supports a commmand-line switch to use
> > embedded mode instead of hosted?
>
On Thu, Feb 26, 2009 at 11:46:22PM -0800, per...@pluto.rain.com wrote:
> > >> By default, LLVM has a built-in prototype of pow(), similar to
> > >> GCC. Unlike GCC, LLVM raises a compiler error by default ...
>
> > ... it's invalid code to have a function named pow()
> > in a hosted environment wh
> >> By default, LLVM has a built-in prototype of pow(), similar to
> >> GCC. Unlike GCC, LLVM raises a compiler error by default ...
> ... it's invalid code to have a function named pow()
> in a hosted environment which is not /The/ pow().
^^^
I don't suppose LLVM supports
David Schultz schrieb:
On Thu, Feb 26, 2009, Christoph Mallon wrote:
David Schultz schrieb:
As for gcc's math builtins, most of them are buggy. They fail to
respect the dynamic rounding mode, fail to generate exceptions
where appropriate, fail to respect FENV_ACCESS and other pragmas,
etc. Also
On Thu, Feb 26, 2009, Christoph Mallon wrote:
> David Schultz schrieb:
> >As for gcc's math builtins, most of them are buggy. They fail to
> >respect the dynamic rounding mode, fail to generate exceptions
> >where appropriate, fail to respect FENV_ACCESS and other pragmas,
> >etc. Also, the complex
;t compile, because a library they depend (libmp)on has a function
called pow(). By default, LLVM has a built-in prototype of pow(),
similar to GCC. Unlike GCC, LLVM raises a compiler error by default. The
manual page also mentions this issue.
I think most apps that used to use libmp have trans
et)
> >>won't compile, because a library they depend (libmp)on has a function
> >>called pow(). By default, LLVM has a built-in prototype of pow(),
> >>similar to GCC. Unlike GCC, LLVM raises a compiler error by default. The
> >>manual page also mentions this
On Thu, 26 Feb 2009, Ed Schouten wrote:
* Daniel Eischen wrote:
Well, as long as you're in there, maybe you should add
symbol versioning anyway, even after a library version
bump. Seems like it would be easy since there aren't
that many symbols.
I assume I should just mark all symbols with
Christoph Mallon schrieb:
David Schultz schrieb:
On Thu, Feb 26, 2009, Ed Schouten wrote:
One of the reasons why we can't compile the base system yet, is because
some applications in the base system (keyserv, newkey, chkey, libtelnet)
won't compile, because a library they depend (li
David Schultz schrieb:
On Thu, Feb 26, 2009, Ed Schouten wrote:
One of the reasons why we can't compile the base system yet, is because
some applications in the base system (keyserv, newkey, chkey, libtelnet)
won't compile, because a library they depend (libmp)on has a function
called
On Thu, Feb 26, 2009, Ed Schouten wrote:
> One of the reasons why we can't compile the base system yet, is because
> some applications in the base system (keyserv, newkey, chkey, libtelnet)
> won't compile, because a library they depend (libmp)on has a function
> called pow()
* Daniel Eischen wrote:
> Well, as long as you're in there, maybe you should add
> symbol versioning anyway, even after a library version
> bump. Seems like it would be easy since there aren't
> that many symbols.
I assume I should just mark all symbols with version FBSD_1.1? If so,
the followin
On Thu, 26 Feb 2009, Ed Schouten wrote:
* Daniel Eischen wrote:
Why don't you add symbol versioning to libmp, so that old
binaries will still work, but new ones will get the new
symbols by default. Hmm, will that work without bumping
SHLIB_MAJOR? You might want to play around with i
* Daniel Eischen wrote:
> Why don't you add symbol versioning to libmp, so that old
> binaries will still work, but new ones will get the new
> symbols by default. Hmm, will that work without bumping
> SHLIB_MAJOR? You might want to play around with it and
> see.
Well,
some applications in the base system (keyserv, newkey, chkey, libtelnet)
won't compile, because a library they depend (libmp)on has a function
called pow(). By default, LLVM has a built-in prototype of pow(),
similar to GCC. Unlike GCC, LLVM raises a compiler error by default. The
manual page als
yserv, newkey, chkey, libtelnet)
won't compile, because a library they depend (libmp)on has a function
called pow(). By default, LLVM has a built-in prototype of pow(),
similar to GCC. Unlike GCC, LLVM raises a compiler error by default. The
manual page also mentions this issue.
After some talking
On Mon, Aug 06, 2001 at 05:18:49PM +, Eugene L. Vorokov wrote:
> > > Hmm yes, it's there. But the snapshot I installed first doesn't
> > > have it (why ?). When I installed it manually prior to compiling libs,
> > > libmp compiles fine ... Btw, is
> > Hmm yes, it's there. But the snapshot I installed first doesn't
> > have it (why ?). When I installed it manually prior to compiling libs,
> > libmp compiles fine ... Btw, is there any guide of what is the proper
> > order of compiling things after cvsup
x27;s there. But the snapshot I installed first doesn't
> have it (why ?). When I installed it manually prior to compiling libs,
> libmp compiles fine ... Btw, is there any guide of what is the proper
> order of compiling things after cvsup ?
Yep, the src/UPDATING file.
What do you mean,
openssl/ and src/secure/lib/openssl/ bits.
> Also, make sure that NOSECURE is NOT turned on in your make.conf.
>
> Hope that helps..
Hmm yes, it's there. But the snapshot I installed first doesn't
have it (why ?). When I installed it manually prior to compiling libs,
libmp co
ever, when doing make in the lib directory,
> > it stops on libmp. The problem is that libmp uses include files from
> > openssl/, and they are not present in my system, as I can see they
> > don't come with freebsd. Of course I know how to install libssl, but
> > is there
On Mon, Aug 06, 2001 at 12:33:40PM +, Eugene L. Vorokov wrote:
> Hello,
>
> I cvsup'ed 5.0-CURRENT yesterday, successfully compiled the kernel and
> tried to compile the rest. However, when doing make in the lib directory,
> it stops on libmp. The problem is that libm
Hello,
I cvsup'ed 5.0-CURRENT yesterday, successfully compiled the kernel and
tried to compile the rest. However, when doing make in the lib directory,
it stops on libmp. The problem is that libmp uses include files from
openssl/, and they are not present in my system, as I can see they
25 matches
Mail list logo
