Joshua Gatcomb writes:
: I build parrot on Cygwin circa 5x a week. Anytime it fails to build, I
: perform the following:
:
: 1. make realclean
: 2. svn up
: 3. perl Configure.pl
: 4. PATH=/home/me/parrot/blib/lib:/bin
: 5. make
Joy! Looks like t/stm/queue is wedged.
Thanks,
Greg
All:
I build parrot on Cygwin circa 5x a week. Anytime it fails to build, I
perform the following:
1. make realclean
2. svn up
3. perl Configure.pl
4. PATH=/home/me/parrot/blib/lib:/bin
5. make
In the very few instances it still fails, I isolate the build that it
started failing and report
On 05/06/07, Greg Bacon <[EMAIL PROTECTED]> wrote:
In message <[EMAIL PROTECTED]>,
"Paul Cochrane via RT" writes:
: cygwin is building as of r18821. Is this ticket required anymore?
I'm still seeing a failure in r18824:
[...]
make[1]: Entering directory `/usr/src/parrot/src/dynoplibs'
mak
In message <[EMAIL PROTECTED]>,
"Paul Cochrane via RT" writes:
: cygwin is building as of r18821. Is this ticket required anymore?
I'm still seeing a failure in r18824:
[...]
make[1]: Entering directory `/usr/src/parrot/src/dynoplibs'
make[1]: Leaving directory `/usr/src/parrot/src/dynoplib
cygwin is building as of r18821. Is this ticket required anymore?
Paul
In message <[EMAIL PROTECTED]>,
"Nick Glencross via RT" writes:
: Even with r11320, the extend tests are failing with linkage errors on
: cygwin. I note that extend.h does not have PARROT_APIs in it. Should
: it by right? (It's possible that extend.o is linked with directly)
I'm seeing the sa
Even with r11320, the extend tests are failing with linkage errors on
cygwin. I note that extend.h does not have PARROT_APIs in it. Should
it by right? (It's possible that extend.o is linked with directly)
I'm tempted as a short term fix to remove the sym_import/export
(cygwin) hints. Would anyone
I have committed a fix in r11320 so that the build doesn't pick up
system-wide libparrots, which has certainly been the cause of some
linkage problems over the last few days.
[As background, since my previous email didn't make it into RT, the
circumstances for this are:
* A system-wide libparro
On Mon, Jan 23, 2006 at 12:13:50AM +, Nick Glencross wrote:
> Nick Glencross wrote:
>
> >There seem to be a few recent events which can now trigger a newish
> >problem:
> >
>
>
> >The real problem is that -L/usr/local/lib is brought in from parrot,
> >so we have a few choices:
> >
> > *
Nick Glencross wrote:
There seem to be a few recent events which can now trigger a newish
problem:
The real problem is that -L/usr/local/lib is brought in from parrot,
so we have a few choices:
* Just remove -Ls brought in from 'lddflags', which seems safe to
me, or
* remove the
Jonathan Worthington wrote:
"Greg Bacon" <[EMAIL PROTECTED]> wrote:
I'm still seeing a link failure with r11221.
Discovered I have cygwin on this PC, went to investigate
and..the link failure is gone as well as the
auto-import warnings. Sadly, there's a new problem that I really have
n
In message <[EMAIL PROTECTED]>,
"Jonathan Worthington via RT" writes:
: "Greg Bacon" <[EMAIL PROTECTED]> wrote:
:
: > I'm still seeing a link failure with r11221.
:
: Discovered I have cygwin on this PC, went to investigate and..the link failure is gone as well as the auto-import warnings.
In message <[EMAIL PROTECTED]>,
Larry Wall writes:
: Looks like the same problem we were having before. If we have to have
: -L/usr/local/lib in there, it should probably come after your personal
: -L/home/gbacon/src/parrot/blib/lib so that -lparrot prefers the one
: you just built. You ran
"Greg Bacon" <[EMAIL PROTECTED]> wrote:
I'm still seeing a link failure with r11221.
Discovered I have cygwin on this PC, went to investigate and...happens>...the link failure is gone as well as the auto-import warnings.
Sadly, there's a new problem that I really have no idea about (aside from
On Tue, Jan 17, 2006 at 08:28:37AM -0600, Greg Bacon wrote:
: I'm still seeing a link failure with r11221.
:
: A confusing bit: I stopped the stripping of libparrot.dll, and nm
: seems to see the symbols that the linker's complaining about:
:
: [...]
: Compiling with:
: xx.c
: gcc -I./include -pi
I'm still seeing a link failure with r11221.
A confusing bit: I stopped the stripping of libparrot.dll, and nm
seems to see the symbols that the linker's complaining about:
[...]
Compiling with:
xx.c
gcc -I./include -pipe -I/usr/local/include -g -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wi
On 1/13/06, Jonathan Worthington <[EMAIL PROTECTED]> wrote:
> "Greg Bacon" <[EMAIL PROTECTED]> wrote:
> > Not quite. At r11144 on Cygwin, I see
> >
> > [...]
> > gcc -o miniparrot.exe -s -L/usr/local/lib compilers/imcc/main.o \
> > -L/home/gbacon/src/parrot/blib/lib -lparrot -lcrypt src/null_con
"Greg Bacon" <[EMAIL PROTECTED]> wrote:
Not quite. At r11144 on Cygwin, I see
[...]
gcc -o miniparrot.exe -s -L/usr/local/lib compilers/imcc/main.o \
-L/home/gbacon/src/parrot/blib/lib -lparrot -lcrypt src/null_config.o
compilers/imcc/main.o: In function `imcc_version':
/home/gbacon/src/parro
In message <[EMAIL PROTECTED]>,
"Jonathan Worthington" writes:
: Ugh. I'm currently doing a lot of stuff to get rid of .def files and
: replace them with decorations in the code instead. You may have got
: caught up in this (or maybe the changes have hurt cygwin in a way I
: didn't anticipate)
"Greg Bacon (via RT)" <[EMAIL PROTECTED]> wrote:
[...]
/usr/bin/perl tools/build/parrot_config_c.pl --mini > \
src/null_config.c
src/null_config.c
gcc -o miniparrot.exe -s -L/usr/local/lib compilers/imcc/main.o \
-L/home/gbacon/src/parrot/blib/lib -lparrot -lcrypt src/null_config.o
compilers/
# New Ticket Created by Greg Bacon
# Please include the string: [perl #38217]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38217 >
[...]
/usr/bin/perl tools/build/parrot_config_c.pl --mini > \
src/null_config.c
src/null_
21 matches
Mail list logo
