05-12-2008
Can't help you with the actual problem, but the error message certainly comes from gcc-4.0 so you definitely have that installed. It basically means the source code contains an invalid C++ template construct.
Their trac returns no matches on asio::time_traits so if it's really a bug, it appears that they are not yet aware of it.
If you file a bug, the first thing they will want to know is which version you tried to build, and whether you get the same error with the latest development sources.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hey everyone
I'm new to UNIX due to the new Mac OS X operating system and would like some help. I'm trying to send an email via the UNIX-Shell-Terminal i Mac OS X, (it's called darwin)
How do I do that? When I enter the Command mail I can send messages to root and with the command -forward... (4 Replies)
Discussion started by: onkel
4 Replies
2. UNIX for Dummies Questions & Answers
Quick question:
When I load up Terminal or X-Windows on my Mac, and the prompt comes up...what folder am I starting in? (2 Replies)
Discussion started by: liquidcross
2 Replies
3. Shell Programming and Scripting
Hey
First of all: I'm on a Mac. I'm quite new to this, so forgive me if i sound like a newb :-)
I wish to install the Deluge BitTorrent client. First of all I installed Macports and made it run smooth. But then I ran into a problem when I should install Deluge. I can post the log, and maybe... (4 Replies)
Discussion started by: Sixmax
4 Replies
4. OS X (Apple)
Hi everyone. I'm new to using the Terminal and was just wondering if anyone had a link to perhaps a list of commands. And tips on some useful websites to visit or books to read.
Oh and is there a way to delete just part of the Terminal's history? If so what is the command?
Thanks :) (2 Replies)
Discussion started by: xsemperidem5
2 Replies
5. UNIX for Dummies Questions & Answers
I finally got how to su - in my mac from the terminal. Now I would like to be able to add new users. useradd -m -d ..... doesn't seem to work. (1 Reply)
Discussion started by: bigmac18
1 Replies
6. Shell Programming and Scripting
Hi,
I am new for SVN. Earlier I have been using CVS. When I checkout the code from SVN using Eclipse, the size of the source code checked out is 612MB. But when I try to checkout from terminal, from my 5.8 branch , the checked out source code's size is only 312.1 MB.
Can anyone tell me... (0 Replies)
Discussion started by: Afreen
0 Replies
7. UNIX for Advanced & Expert Users
Is there a trick to closing a mac terminal with a command? I would think you could just type exit into your terminal but that doesn't work. I also tried quit and close just for the hell of it and that didn't work either. Does anyone know what the command is? (1 Reply)
Discussion started by: cokedude
1 Replies
8. OS X (Apple)
So found this C code online and need to compile it in Terminal on Mac.
Here is the code:
#include <stdio.h>
#include <math.h>
int option;
char q;
int number;
int currentsum;
int value;
void calc()
{
printf("\t\t\t\t\tBegin\n"); // says begin in top middle of screen
... (3 Replies)
Discussion started by: 1negroup
3 Replies
9. Open Source
Does anyone know the differences in commands when it come to Linux and Mac OS X? I'm wanting to know if I use "this" command in Linux and It doesn't work in Mac then what command is equivalent to the one in Linux. Example Ctrl+Alt+f2 switches to (tty2) so what equivalent switches to ttys2 on Mac? (13 Replies)
Discussion started by: 1negroup
13 Replies
LEARN ABOUT MOJAVE
cpanplus::hacking
CPANPLUS::Hacking(3pm) Perl Programmers Reference Guide CPANPLUS::Hacking(3pm)
NAME
CPANPLUS::Hacking - developing CPANPLUS
DESCRIPTION
This document attempts to describe how to develop with the CPANPLUS environment most easily, how certain things work and why.
This is basically a quick-start guide to people who want to add features or patches to CPANPLUS.
OBTAINING CPANPLUS
Checkout CPANPLUS from its GIT repository at <https://github.com/jib/cpanplus-devel> .
INSTALLING CPANPLUS
CPANPLUS follows the standard perl module installation process:
perl Makefile.PL
make
make test
make install
CONFIGURING CPANPLUS
When running "perl Makefile.PL" you will be prompted to configure. If you have already done so, and merely wish to update the "Makefile",
simply run:
perl Makefile.PL JFDI=1
This will keep your configuration intact. Note however, if there are changes to the default configuration file "Config.pm-orig", you should
either delete your current config file and reconfigure, or patch your config file from the new entries in "Config.pm-orig".
RUNNING CPANPLUS FROM DEVELOPMENT ENVIRONMENT
If you'd rather not install the development version to your "site_perl" directory, that's no problem. You can set your "PERL5LIB"
environment variable to CPANPLUS' "lib" directory, and you can run it from there.
RUNNING CPANPLUS TESTS
Tests are what tells us if CPANPLUS is working. If a test is not working, try to run it explicitly like this:
perl -I/path/to/cpanplus/lib t/XX_name_of_test.t 1
The extra '1' makes sure that all the messages and errors (they might be errors we're testing for!) are being printed rather than kept
quiet. This is a great way to find out the context of any failures that may occur.
If you believe this test failure proves a bug in CPANPLUS, the long output of the test file is something we'd like to see alongside your
bug report.
FINDING BUGS
Sometimes you might find bugs in CPANPLUS' behaviour. If you encounter these in a development snapshot, we'd appreciate a complete patch
(as described below in the "SENDING PATCHES" section.
If it's way over your head, then of course reporting the bug is always better than not reporting it at all. Before you do so though, make
sure you have the latest development snapshot, and the bug still persists there. If so, report the bug to this address:
bug-cpanplus@rt.cpan.org
A good "patch" would have the following characteristics:
Problem description
Describe clearly what the bug is you found, and what it should have done instead.
Program demonstrating the bug
Show us how to reproduce the bug, in a simple of a program as possible
[OPTIONAL] A patch to the test suite to test for the bug
Amend our test suite by making sure this bug will be found in this, and future versions of CPANPLUS (see "SUPPLYING PATCHES")
[OPTIONAL] A patch to the code + tests + documentation
Fix the bug, update the docs & tests. That way your bug will be gone forever :)
SUPPLYING PATCHES
Patches are a good thing, and they are welcome. Especially if they fix bugs you've found along the way, or that others have reported.
We prefer patches in the following format:
o In "diff -u" or "diff -c" format
o From the root of the snapshot
o Including patches for code + tests + docs
o Sent per mail to bug-cpanplus@rt.cpan.org
o With subject containing "[PATCH]" + description of the patch
You will always be informed if a patch is applied or rejected, and in case of rejection why that is (perhaps you can tweak the patch to
have it accepted after all).
perl v5.18.2 2014-01-06 CPANPLUS::Hacking(3pm)