On 19 Mar 2013, at 17:31, "Dave McGuire" <mcguire at neurotica.com> wrote:
On 03/19/2013 05:27 PM, Cory Smelosky wrote:
I have done this and the result is less errors, but I still get some:
(I did try with the cp as well. No change)
bash-3.2$ unzip -aaqq master
bash-3.2$ cd simh-master
bash-3.2$ /opt/csw/bin/gmake vax GCC=/opt/solarisstudio12.3/bin/CC
Change GCC=/opt/solarisstudio12.3/bin/CC to GCC=/opt/solarisstudio12.3/bin/cc
The simh code base is C not C++.
Ahh. That's an odd way to differentiate between a C and C++ compiler...
It's pretty standard, actually. It's just not the way GCC does it.
I'm used to either Unices that don't differentiate that way, or predate C++. ;)
And now my issues are only with libpcap Does solaris 10 bundle its own? If so, where's it located?
Not that I'm aware of. And if it doesn't, that'd be refreshing,
because Sun got into a really bad habit of bundling non-operating-system
components with the operating system, all very outdated and compiled to
be put in weird places in the filesystem.
Looks like I just need to find the magic version then. 1.2.1 and one version prior seemed to have issues.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 03/19/2013 05:27 PM, Cory Smelosky wrote:
I have done this and the result is less errors, but I still get some:
(I did try with the cp as well. No change)
bash-3.2$ unzip -aaqq master
bash-3.2$ cd simh-master
bash-3.2$ /opt/csw/bin/gmake vax GCC=/opt/solarisstudio12.3/bin/CC
Change GCC=/opt/solarisstudio12.3/bin/CC to GCC=/opt/solarisstudio12.3/bin/cc
The simh code base is C not C++.
Ahh. That's an odd way to differentiate between a C and C++ compiler...
It's pretty standard, actually. It's just not the way GCC does it.
I'm used to either Unices that don't differentiate that way, or predate C++. ;)
And now my issues are only with libpcap Does solaris 10 bundle its own? If so, where's it located?
Not that I'm aware of. And if it doesn't, that'd be refreshing,
because Sun got into a really bad habit of bundling non-operating-system
components with the operating system, all very outdated and compiled to
be put in weird places in the filesystem.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 19 Mar 2013, at 17:08, "Cory Smelosky" <b4 at gewt.net> wrote:
On 19 Mar 2013, at 17:04, "Dave McGuire" <mcguire at neurotica.com> wrote:
On 03/19/2013 04:58 PM, Cory Smelosky wrote:
I have done this and the result is less errors, but I still get some:
(I did try with the cp as well. No change)
bash-3.2$ unzip -aaqq master
bash-3.2$ cd simh-master
bash-3.2$ /opt/csw/bin/gmake vax GCC=/opt/solarisstudio12.3/bin/CC
Change GCC=/opt/solarisstudio12.3/bin/CC to GCC=/opt/solarisstudio12.3/bin/cc
The simh code base is C not C++.
Ahh. That's an odd way to differentiate between a C and C++ compiler...
It's pretty standard, actually. It's just not the way GCC does it.
I'm used to either Unices that don't differentiate that way, or predate C++. ;)
And now my issues are only with libpcap Does solaris 10 bundle its own? If so, where's it located?
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 03/19/2013 05:07 PM, Gregg Levine wrote:
Yes indeed. Never mind the fact that the tools share an origin with
both Solaris and BSD and of course Linux.
Sun's C compiler does *not* trace its origins to Linux.
Now Dave I can see you from your windows, as I type this. Please stop
staring. Yes I'm the one in the older yellow car with the young lady.
If you're peeking in my windows, you can see that I'm sitting at my
desk writing software in R while buck naked.
Who's the hottie?
Also you didn't release the 32 Gigabytes that they need, so they are
going to request an extra 64 instead.
And they'll probably get it!
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 19 Mar 2013, at 17:04, "Dave McGuire" <mcguire at neurotica.com> wrote:
On 03/19/2013 04:58 PM, Cory Smelosky wrote:
I have done this and the result is less errors, but I still get some:
(I did try with the cp as well. No change)
bash-3.2$ unzip -aaqq master
bash-3.2$ cd simh-master
bash-3.2$ /opt/csw/bin/gmake vax GCC=/opt/solarisstudio12.3/bin/CC
Change GCC=/opt/solarisstudio12.3/bin/CC to GCC=/opt/solarisstudio12.3/bin/cc
The simh code base is C not C++.
Ahh. That's an odd way to differentiate between a C and C++ compiler...
It's pretty standard, actually. It's just not the way GCC does it.
I'm used to either Unices that don't differentiate that way, or predate C++. ;)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On Tue, Mar 19, 2013 at 5:04 PM, Dave McGuire <mcguire at neurotica.com> wrote:
On 03/19/2013 04:58 PM, Cory Smelosky wrote:
I have done this and the result is less errors, but I still get some:
(I did try with the cp as well. No change)
bash-3.2$ unzip -aaqq master
bash-3.2$ cd simh-master
bash-3.2$ /opt/csw/bin/gmake vax GCC=/opt/solarisstudio12.3/bin/CC
Change GCC=/opt/solarisstudio12.3/bin/CC to GCC=/opt/solarisstudio12.3/bin/cc
The simh code base is C not C++.
Ahh. That's an odd way to differentiate between a C and C++ compiler...
It's pretty standard, actually. It's just not the way GCC does it.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Hello!
Yes indeed. Never mind the fact that the tools share an origin with
both Solaris and BSD and of course Linux.
Now Dave I can see you from your windows, as I type this. Please stop
staring. Yes I'm the one in the older yellow car with the young lady.
Also you didn't release the 32 Gigabytes that they need, so they are
going to request an extra 64 instead.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On 2013-03-19 21:58, Cory Smelosky wrote:
On 19 Mar 2013, at 16:52, "Mark Pizzolato - Info Comm" <Mark at infocomm.com> wrote:
On Tuesday, March 19, 2013 at 1:12 PM, Cory Smelosky wrote:
I have done this and the result is less errors, but I still get some:
(I did try with the cp as well. No change)
bash-3.2$ unzip -aaqq master
bash-3.2$ cd simh-master
bash-3.2$ /opt/csw/bin/gmake vax GCC=/opt/solarisstudio12.3/bin/CC
Change GCC=/opt/solarisstudio12.3/bin/CC to GCC=/opt/solarisstudio12.3/bin/cc
The simh code base is C not C++.
Ahh. That's an odd way to differentiate between a C and C++ compiler...
I seem to remember that this was a rather common convention a while back. Not that I necessarily think it was a good one.
Johnny
On 03/19/2013 05:03 PM, Mark Pizzolato - Info Comm wrote:
I do know that on Dave's system I was using 'cc' instead of 'CC', and
the latest code compiles now without any issues.
Nice work! Thank you for your efforts.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 03/19/2013 04:58 PM, Cory Smelosky wrote:
I have done this and the result is less errors, but I still get some:
(I did try with the cp as well. No change)
bash-3.2$ unzip -aaqq master
bash-3.2$ cd simh-master
bash-3.2$ /opt/csw/bin/gmake vax GCC=/opt/solarisstudio12.3/bin/CC
Change GCC=/opt/solarisstudio12.3/bin/CC to GCC=/opt/solarisstudio12.3/bin/cc
The simh code base is C not C++.
Ahh. That's an odd way to differentiate between a C and C++ compiler...
It's pretty standard, actually. It's just not the way GCC does it.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On Tuesday, March 19, 2013 at 1:58 PM, Cory Smelosky wrote:
On 19 Mar 2013, at 16:52, "Mark Pizzolato - Info Comm"
<Mark at infocomm.com> wrote:
On Tuesday, March 19, 2013 at 1:12 PM, Cory Smelosky wrote:
I have done this and the result is less errors, but I still get some:
(I did try with the cp as well. No change)
bash-3.2$ unzip -aaqq master
bash-3.2$ cd simh-master
bash-3.2$ /opt/csw/bin/gmake vax GCC=/opt/solarisstudio12.3/bin/CC
Change GCC=/opt/solarisstudio12.3/bin/CC to
GCC=/opt/solarisstudio12.3/bin/cc
The simh code base is C not C++.
Ahh. That's an...odd way to differentiate between a C and C++ compiler...
I'm just guessing that is what is going on.
I do know that on Dave's system I was using 'cc' instead of 'CC', and the latest code compiles now without any issues.
- Mark
