* Build Bug in wip-peg
@ 2011-09-03 20:38 Noah Lavine
2011-09-04 10:14 ` Andy Wingo
0 siblings, 1 reply; 3+ messages in thread
From: Noah Lavine @ 2011-09-03 20:38 UTC (permalink / raw)
To: guile-devel
Hello all,
It's been a while, but I just got the wip-peg branch from the main
repository and tried to build it. After doing "make clean && make", I
get this error:
Undefined symbols:
"_rpl_open", referenced from:
_scm_open_file in libguile_2.0_la-fports.o
_scm_load_objcode in libguile_2.0_la-objcodes.o
_scm_copy_file in filesys.o
_scm_copy_file in filesys.o
_scm_open_fdes in filesys.o
ld: symbol(s) not found
However, I do not get an error when I build the master branch. Since
wip-peg is based on the stable branch, I assume that some build change
between stable and master made it work on my system. Can anyone
suggest what that might be?
Noah
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Build Bug in wip-peg
2011-09-03 20:38 Build Bug in wip-peg Noah Lavine
@ 2011-09-04 10:14 ` Andy Wingo
[not found] ` <CA+U71=MxJPZ0ogJHCRSRV=vC3Vc03d9+4cmm7EyNZy=zAn8EpA@mail.gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Andy Wingo @ 2011-09-04 10:14 UTC (permalink / raw)
To: Noah Lavine; +Cc: guile-devel
On Sat 03 Sep 2011 22:38, Noah Lavine <noah.b.lavine@gmail.com> writes:
> It's been a while, but I just got the wip-peg branch from the main
> repository and tried to build it. After doing "make clean && make", I
> get this error:
>
> Undefined symbols:
> "_rpl_open", referenced from:
> _scm_open_file in libguile_2.0_la-fports.o
> _scm_load_objcode in libguile_2.0_la-objcodes.o
> _scm_copy_file in filesys.o
> _scm_copy_file in filesys.o
> _scm_open_fdes in filesys.o
> ld: symbol(s) not found
>
> However, I do not get an error when I build the master branch. Since
> wip-peg is based on the stable branch, I assume that some build change
> between stable and master made it work on my system. Can anyone
> suggest what that might be?
wip-peg is based on stable-2.0, not master. Perhaps it was something
fixed later in stable-2.0. Does the problem persist if you "git merge
origin/stable-2.0"? If not, then we should probably rebase the branch
again.
It will be great when we finally merge this branch :-)
Andy
--
http://wingolog.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Build Bug in wip-peg
[not found] ` <87fwkaukoo.fsf@pobox.com>
@ 2011-09-06 14:28 ` Noah Lavine
0 siblings, 0 replies; 3+ messages in thread
From: Noah Lavine @ 2011-09-06 14:28 UTC (permalink / raw)
To: Andy Wingo, guile-devel
Oh yes, good idea. I didn't realize I had hit reply instead of reply-all.
I'm replying to the list now so at least it will get a copy of the emails. :-)
On Tue, Sep 6, 2011 at 4:41 AM, Andy Wingo <wingo@pobox.com> wrote:
> Hi Noah,
>
> Let's try to keep the list in the loop on future mails. My inbox is a
> bit lossy :)
>
> Cheers,
>
> Andy
>
> On Tue 06 Sep 2011 04:25, Noah Lavine <noah.b.lavine@gmail.com> writes:
>
>> I have fixed this. There is currently a branch on Savannah called
>> "wip-peg-fixed" which has all of the peg changes rebased on top of
>> stable-2.0. It builds fine on my machine and runs the peg test suite
>> with all passes. (I couldn't overwrite wip-peg without pulling and
>> merging, and I was afraid I would mess up my changes, so I used a
>> different name.)
>>
>> When I was trying to fix the compilation bug, I realized that for some
>> reason wip-peg did not have the most recent version of the peg code. I
>> don't know why that would happen, so I decided the safest thing to do
>> was take my local branch of up-to-date peg code and rebase on top of
>> stable-2.0, which is what I did. It now works.
>>
>> The next step, I think, is fixing the S-expression representation of
>> some parts of the grammar. Then, finally, I think it might be ready to
>> use. :-)
>>
>> Noah
>>
>> On Sun, Sep 4, 2011 at 10:50 AM, Noah Lavine <noah.b.lavine@gmail.com> wrote:
>>> No, that eliminates the problem.
>>>
>>> There's still a bug in compiling the peg code, but I have a fix for
>>> that too. Currently there is something odd going on with the peg test
>>> suite, which I will look at, and then we can finally fix the
>>> S-expression representation of the PEG grammars :-).
>>>
>>> Noah
>>>
>>> On Sun, Sep 4, 2011 at 6:14 AM, Andy Wingo <wingo@pobox.com> wrote:
>>>> On Sat 03 Sep 2011 22:38, Noah Lavine <noah.b.lavine@gmail.com> writes:
>>>>
>>>>> It's been a while, but I just got the wip-peg branch from the main
>>>>> repository and tried to build it. After doing "make clean && make", I
>>>>> get this error:
>>>>>
>>>>> Undefined symbols:
>>>>> "_rpl_open", referenced from:
>>>>> _scm_open_file in libguile_2.0_la-fports.o
>>>>> _scm_load_objcode in libguile_2.0_la-objcodes.o
>>>>> _scm_copy_file in filesys.o
>>>>> _scm_copy_file in filesys.o
>>>>> _scm_open_fdes in filesys.o
>>>>> ld: symbol(s) not found
>>>>>
>>>>> However, I do not get an error when I build the master branch. Since
>>>>> wip-peg is based on the stable branch, I assume that some build change
>>>>> between stable and master made it work on my system. Can anyone
>>>>> suggest what that might be?
>>>>
>>>> wip-peg is based on stable-2.0, not master. Perhaps it was something
>>>> fixed later in stable-2.0. Does the problem persist if you "git merge
>>>> origin/stable-2.0"? If not, then we should probably rebase the branch
>>>> again.
>>>>
>>>> It will be great when we finally merge this branch :-)
>>>>
>>>> Andy
>>>> --
>>>> http://wingolog.org/
>>>>
>>>
>
> --
> http://wingolog.org/
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-09-06 14:28 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-03 20:38 Build Bug in wip-peg Noah Lavine
2011-09-04 10:14 ` Andy Wingo
[not found] ` <CA+U71=MxJPZ0ogJHCRSRV=vC3Vc03d9+4cmm7EyNZy=zAn8EpA@mail.gmail.com>
[not found] ` <CA+U71=POU8xPA73z=SOMTeW8EH1LZnngBV7rX_9W3D3jVKoyWw@mail.gmail.com>
[not found] ` <87fwkaukoo.fsf@pobox.com>
2011-09-06 14:28 ` Noah Lavine
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).