10:46 a.m.
>>>> "Matthew" == Matthew Persico
<persicom(a)acedsl.com> writes:
Matthew> Matthew Persico wrote:
>>
>> Adrian Aichner wrote:
>> >
>> > >>>> "Matthew" ==
Matthew Persico <persicom(a)acedsl.com> writes:
>> >
>> > Matthew,
>> >
>> > have you tried
>> > nmake -f xemacs.mak distclean
>> > before building
>> > nmake -f xemacs.mak [all|install]
>> > ?
>>
>> The build failure was in a just-expanded distibution, so that shouldn't
>> have been a problem, but I will try it just in case.
>> The other thing I'm going to do is rebuild xpm from the sources. I have
>> the pre-compiled win32 libraries installed for xplm,png, tiff, etc.
>> Maybe it won't help, but I'm the type of guy that the first thing I
do
>> after installing a linux distro is trash the RPMs of perl and rebuild
>> it. Source is king.
>>
>> Will advise when complete.
Matthew> COMPLETE! But who the hell screwed up the references to
Matthew, don't you think you're a bit offensive in your choice of
language?
What is your current directory when you run
nmake ... -f ...xemacs.mak?
What is the exact command line you use?
When I try to reproduce this, nmake fails very early[1], not being able
to find ..\version.sh.
Why doesn't this happen for you?
Matthew> i.exe? How difficult could it be to replace
Matthew> XEMACS=.. with the real damn path so that no references
Matthew> are relative and dependent on where you've cd'ed to?
Too difficult for you to send a patch, maybe?
Adrian
Matthew> --
Matthew> Matthew O. Persico
Matthew> "If you were supposed to understand it,
Matthew> we wouldn't call it code." - FedEx
Matthew> ____________NetZero Free Internet Access and Email_________
Matthew> Download Now http://www.netzero.net/download/index.html
Matthew> Request a CDROM 1-800-333-3633
Matthew> ___________________________________________________________
Footnotes:
[1] cd d:\tmp\21.2\xemacs\
nmake -n -f d:\tmp\21.2\xemacs\nt\xemacs.mak all
Compilation started at Sat Oct 07 10:12:35 2000 +0200 (W. Europe Daylight Time)
Microsoft (R) Program Maintenance Utility Version 6.00.8168.0
Copyright (C) Microsoft Corp 1988-1998. All rights reserved.
d:\tmp\21.2\xemacs\nt\xemacs.mak(46) : fatal error U1052: file '..\version.sh' not
found
Stop.
Compilation exited abnormally with code 2 at Sat Oct 07 10:12:35
--
Adrian Aichner <adrian(a)xemacs.org>, http://www.xemacs.org
2:31 a.m.
New subject: Failure to build 21.2.b36 in W2K
Adrian Aichner wrote:
Matthew> COMPLETE! But who the hell screwed up the references to
Matthew, don't you think you're a bit offensive in your choice of
language?
Yep. uncalled for. I think someone else complained about same thing with
less offensiveness a week earlier.
What is your current directory when you run
nmake ... -f ...xemacs.mak?
nt subdirectory
What is the exact command line you use?
nmake install -f xemacs.mak
Matthew> i.exe? How difficult could it be to replace
Matthew> XEMACS=.. with the real damn path so that no references
Matthew> are relative and dependent on where you've cd'ed to?
Too difficult for you to send a patch, maybe?
Ohh, I must have been in a seriously bad mood that night, but for other
reasons. Time to start saving to draft and re-reading the next day
before hitting the send button.
Actually, I was thinking that a patch would be either:
1)The config script has a macro FULL_XEMACS_SRC path
2)Have the makefile figure it out.
One problem I'm having is trying to figure out the equivilent of 'pwd'
in NT or how to fake it.
The true crux of the problem is that you need to quote programs with
spaces in the name or path. When the macro $(FOO) is "..\With
Space\i.exe", then adding judicical ..\ (like so: ..\$(FOO)) won't
work; you get ..\"..\With Space\i.exe".
Come to think of it, FULL_XEMACS_SRC may not work either. If the
definition is like "C:\With Spaces\xemacs". then you have the same
problem adding subdirs to the front as adding ..\ to the rear - they get
added outside the quotes.
So, to answer my own question, it can be very difficult to replace
XEMACS=..
Any one have any crow? Or an old hat they don't need? I just got rather
hungry.
:=(
--
Matthew O. Persico
"If you were supposed to understand it,
we wouldn't call it code." - FedEx
____________NetZero Free Internet Access and Email_________
Download Now http://www.netzero.net/download/index.html
Request a CDROM 1-800-333-3633
___________________________________________________________
1:08 p.m.
New subject: Failure to build 21.2.b36 in W2K
>>>> "Matthew" == Matthew Persico
<persicom(a)acedsl.com> writes:
Matthew> Adrian Aichner wrote:
>
Matthew> COMPLETE! But who the hell screwed up the
references to
>
>> Matthew, don't you think you're a bit
offensive in your choice of
>> language?
Matthew> Yep. uncalled for. I think someone else complained about same thing with
Matthew> less offensiveness a week earlier.
>> What is your current directory when you run
>> nmake ... -f ...xemacs.mak?
>
Matthew> nt subdirectory
Hmmh? Why do you get a problem when running nmake from the nt
directory. I am lost.
> What is the exact command line you use?
Matthew> nmake install -f xemacs.mak
Matthew> i.exe? How difficult could it be to replace
Matthew> XEMACS=.. with the real damn path so that no references
Matthew> are relative and dependent on where you've cd'ed to?
>
>> Too difficult for you to send a patch,
maybe?
>
Matthew> Ohh, I must have been in a seriously bad mood that night, but for other
Matthew> reasons. Time to start saving to draft and re-reading the next day
Matthew> before hitting the send button.
Matthew> Actually, I was thinking that a patch would be either:
Matthew> 1)The config script has a macro FULL_XEMACS_SRC path
Matthew> 2)Have the makefile figure it out.
Matthew> One problem I'm having is trying to figure out the equivilent of
'pwd'
Matthew> in NT or how to fake it.
Matthew> The true crux of the problem is that you need to quote programs with
Matthew> spaces in the name or path. When the macro $(FOO) is "..\With
Matthew> Space\i.exe", then adding judicical ..\ (like so: ..\$(FOO))
won't
Matthew> work; you get ..\"..\With Space\i.exe".
Matthew> Come to think of it, FULL_XEMACS_SRC may not work either. If the
Matthew> definition is like "C:\With Spaces\xemacs". then you have the
same
Matthew> problem adding subdirs to the front as adding ..\ to the rear - they get
Matthew> added outside the quotes.
Matthew> So, to answer my own question, it can be very difficult to replace
Matthew> XEMACS=..
:-)
Matthew> Any one have any crow? Or an old hat they don't need? I just got
rather
Matthew> hungry.
For now I have commited a patch which allows building from the nt
directory only.
http://www.xemacs.org/list-archives/xemacs-patches/200010/msg00027.html
Otherwise nmake fails and tells user to run it from the directory
where xemacs.mak is located.
Is that acceptable?
Best regards,
Adrian
Matthew> :=(
Matthew> --
Matthew> Matthew O. Persico
Matthew> "If you were supposed to understand it,
Matthew> we wouldn't call it code." - FedEx
Matthew> ____________NetZero Free Internet Access and Email_________
Matthew> Download Now http://www.netzero.net/download/index.html
Matthew> Request a CDROM 1-800-333-3633
Matthew> ___________________________________________________________
--
Adrian Aichner <adrian(a)xemacs.org>, http://www.xemacs.org
3:37 a.m.
New subject: Failure to build 21.2.b36 in W2K
Adrian Aichner wrote:
> Matthew> COMPLETE! But who the hell screwed up the
references to
> Matthew, don't you think you're a bit offensive
in your choice of
> language?
What is your current directory when you run
nmake ... -f ...xemacs.mak?
^^^^
Now look who's talking dirty !
--peter(a)access.com.au -- Peter G. Martin,
Tech writer, Perl Thingy-er, pmartin1(a)bigpond.net.au
8809
days inactive
8812
days old
3 comments
3 participants
participants (3)
-
Adrian Aichner -
Matthew O. Persico -
Peter G. Martin