DragonFlyBSD

On Mon, Jul 27, 2009 at 08:31:28AM +0100, Robin Carey wrote:

OpenSSL that's broken. It's g++ that's broken. *
Matt told me the compiler tools have not changed, and
[2]Avalon.dragonflybsd.org and [3]Leaf.dragonflybsd.org report they have
the same version of g++. *

Robin,

avalon was upgraded to master today. Can you please let us know whether
avalon's g++ still works?

--Peter

Hi Peter,

I just checked Avalon just now, and it would appear Avalon's g++ doesn't
work anymore.
But it was working before. But now it doesn't.

2009/7/27 Peter Avalos (via DragonFly issue tracker) <
bugs@crater.dragonflybsd.org>

Peter Avalos <pavalos@theshell.com> added the comment:

On Mon, Jul 27, 2009 at 08:31:28AM +0100, Robin Carey wrote:

OpenSSL that's broken. It's g++ that's broken. *
Matt told me the compiler tools have not changed, and
[2]Avalon.dragonflybsd.org <http://avalon.dragonflybsd.org/> and [3]

Leaf.dragonflybsd.org <http://leaf.dragonflybsd.org/> report they have

the same version of g++. *

Robin,

avalon was upgraded to master today. Can you please let us know whether
avalon's g++ still works?

--Peter

----------
status: unread -> chatting

_____________________________________________
DragonFly issue tracker <bugs@lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue1439>
_____________________________________________

Robin Carey wrote:

I just checked Avalon just now, and it would appear Avalon's g++ doesn't work
anymore.
But it was working before. But now it doesn't.

Can you try compiling with the environment variable CCVER set to gcc34?
We've imported a new version of openssl, which I more suspect to be
the cause.

Also, is this wrong data always the same or is it random?

cheers
simon

Hi,

I'll try gcc34.
As I said in more original post to bugs@, at first I thought it was OpenSSL,
but I eliminated that to be the cause of the problem by trying the version
of OpenSSL on Leaf, that was installed on Avalon (0.9.8j). I tried that
version of OpenSSL on Leaf and the problem stayed. So I then knew it wasn't
OpenSSL.

The wrong data seems to be the same, but there is more than one problem, and
with regard to the only problem I have examined so far (by debugging), the
wrong data seems to stay the same.

2009/7/27 Simon 'corecode' Schubert <corecode@fs.ei.tum.de>

Robin Carey wrote:

I just checked Avalon just now, and it would appear Avalon's g++ doesn't
work anymore.
But it was working before. But now it doesn't.

Can you try compiling with the environment variable CCVER set to gcc34?
We've imported a new version of openssl, which I more suspect to be the
cause.

Also, is this wrong data always the same or is it random?

cheers
simon

--
<3 the future ++ RENT this banner advert ++ ASCII Ribbon /"\
rock the past ++ space for low CHF NOW!1 ++ Campaign \ /
Party Enjoy Relax | http://dragonflybsd.org Against HTML \
Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \

Hi,

I had a look around on Leaf and Avalon, and gcc34 doesn't seem to be
installed, therefore I wouldn't be able to use it.
Anyway, C12 is C++ code - not C code, so the compiler it needs is g++.

2009/7/27 Simon 'corecode' Schubert (via DragonFly issue tracker) <
bugs@crater.dragonflybsd.org>

Simon 'corecode' Schubert <corecode@fs.ei.tum.de> added the comment:

Robin Carey wrote:

I just checked Avalon just now, and it would appear Avalon's g++ doesn't

work

anymore.
But it was working before. But now it doesn't.

Can you try compiling with the environment variable CCVER set to gcc34?
We've imported a new version of openssl, which I more suspect to be
the cause.

Also, is this wrong data always the same or is it random?

cheers
simon

_____________________________________________
DragonFly issue tracker <bugs@lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue1439>
_____________________________________________

Robin Carey wrote:

Hi,

I had a look around on Leaf and Avalon, and gcc34 doesn't seem to be
installed, therefore I wouldn't be able to use it.

Yes, just set the CCVER environment variable:

leaf:~ % env CCVER=gcc34 c++ -v
Using built-in specs.
Configured with: DragonFly/i386 system compiler
Thread model: posix
gcc version 3.4.6 [DragonFly] (propolice, visibility)

i.e. use setenv CCVER gcc34, or export CCVER=gcc34, depending on your shell.

cheers
simon

Hi Simon,

I did as you requested and there are still problems.
If there is a problem with the libraries the compiler is using, changing the
compiler to gcc-v3.4 won't stop that problem from manifesting, surely .... ?

I mean, does setting CCVER to gcc34 change the libraries the compiler is
using ?
Or does the compiler use the same libraries ? If it uses the same libraries
and there is a problem with the libraries then that would explain why I'm
still having run-time problems.

As I said before in my original post, I have thoroughly tested C12 on LEAF
before the upgrade happened and it was working fine.

2009/7/27 Simon 'corecode' Schubert <corecode@fs.ei.tum.de>

Robin Carey wrote:

Hi,

I had a look around on Leaf and Avalon, and gcc34 doesn't seem to be
installed, therefore I wouldn't be able to use it.

Yes, just set the CCVER environment variable:

leaf:~ % env CCVER=gcc34 c++ -v
Using built-in specs.
Configured with: DragonFly/i386 system compiler
Thread model: posix
gcc version 3.4.6 [DragonFly] (propolice, visibility)

i.e. use setenv CCVER gcc34, or export CCVER=gcc34, depending on your
shell.

cheers
simon

--
<3 the future ++ RENT this banner advert ++ ASCII Ribbon /"\
rock the past ++ space for low CHF NOW!1 ++ Campaign \ /
Party Enjoy Relax | http://dragonflybsd.org Against HTML \
Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \

Robin Carey wrote:

Hi Simon,

I did as you requested and there are still problems.
If there is a problem with the libraries the compiler is using, changing the
compiler to gcc-v3.4 won't stop that problem from manifesting, surely .... ?

That is true. I'm trying to find out whether the compiler produces bad
output for your code, or whether it is a function of the libraries
installed on the system.

So it seems that the problem lies in the libraries, but you said you had
tried it with the new openssl, which worked?

cheers
simon

Hi Simon,

When I first compiled C12 on the newly upgraded Leaf, I was using the system
version of OpenSSL which I think is 0.9.8k .....
And I thought OH the problem must be OpenSSL.
So I compiled the older version of OpenSSL which was on Avalon, on
Leaf, (which at that time Avalon had not been upgraded and my C12 software
worked OK), and that version was 0.9.8j.

But I was still having problems on leaf with the older version of OpenSSL.
Hence I am saying the problem isn't OpenSSL, so it must be g++.

To answer your question: No it didn't work Ok with the new version of
OpenSSL (which is the system version on Leaf).

2009/7/27 Simon 'corecode' Schubert <corecode@fs.ei.tum.de>

Robin Carey wrote:

Hi Simon,

I did as you requested and there are still problems.
If there is a problem with the libraries the compiler is using, changing
the
compiler to gcc-v3.4 won't stop that problem from manifesting, surely ....
?

That is true. I'm trying to find out whether the compiler produces bad
output for your code, or whether it is a function of the libraries installed
on the system.

So it seems that the problem lies in the libraries, but you said you had
tried it with the new openssl, which worked?

cheers
simon

--
<3 the future ++ RENT this banner advert ++ ASCII Ribbon /"\
rock the past ++ space for low CHF NOW!1 ++ Campaign \ /
Party Enjoy Relax | http://dragonflybsd.org Against HTML \
Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \

Dear DragonFlyBSD bugs,

This issue can now be closed.
Simon Schubert found a bug in my code that was causing the problem.
The problem in my code has now been fixed.

So to sum up:

Sorry if I caused anybody any trouble.
There are no problems with g++ or OpenSSL - it was a bug in my Caesarion
software.

Thanks Simon !!!!

cheers,
robin

2009/7/27 Peter Avalos (via DragonFly issue tracker) <
bugs@crater.dragonflybsd.org>

Peter Avalos <pavalos@theshell.com> added the comment:

On Mon, Jul 27, 2009 at 08:31:28AM +0100, Robin Carey wrote:

OpenSSL that's broken. It's g++ that's broken. *
Matt told me the compiler tools have not changed, and
[2]Avalon.dragonflybsd.org <http://avalon.dragonflybsd.org/> and [3]

Leaf.dragonflybsd.org <http://leaf.dragonflybsd.org/> report they have

the same version of g++. *

Robin,

avalon was upgraded to master today. Can you please let us know whether
avalon's g++ still works?

--Peter

----------
status: unread -> chatting

_____________________________________________
DragonFly issue tracker <bugs@lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue1439>
_____________________________________________

Excellent! A resolution to the problem is always a good thing, even
if it turned out to be a coding error.

-Matt