Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Compilation problem
30 views
Skip to first unread message
vrs
May 16, 2012, 10:42:00 AM5/16/12
to
Hi,
I used to create my systems with xharbour in a machine with windowsxp
sp3. And always works pretty well.
Now i change to Windows7 32 bits and every time i try to generate an
exec, the message like below appears:
Type: C >>>xhb.exe -o"FTIMPNOT.c" -m -n -p -q -gc0 -B -DHB_MULTI_GT -
I"H:\CLIPPER5\INCLUDE" -I"\SIC3\STD" -I"\SIC3\STDC" -I"\SIC3\FT2" -
I"\SIC3\CO2" -I"C:\xHB1\include" -I"C:\xHB1\include\w32" "F:\clientes
\OMEGA\SIC\FTIMPNOT.PRG"<<<
Type: C >>>Couldn't build: FTIMPNOT.obj<<<
Type: C >>>TMAKEOBJECT<<<
Type: C >>>TMAKEOBJECT:REFRESH<<<
Type: N >>> 1278<<<
My xharbour is: xHarbour Compiler build 0.99.70 (SimpLex) 1999-2006,
http://www.xharbour.org http://www.harbour-project.org/
Thanks in advance.
I used to create my systems with xharbour in a machine with windowsxp
sp3. And always works pretty well.
Now i change to Windows7 32 bits and every time i try to generate an
exec, the message like below appears:
Type: C >>>xhb.exe -o"FTIMPNOT.c" -m -n -p -q -gc0 -B -DHB_MULTI_GT -
I"H:\CLIPPER5\INCLUDE" -I"\SIC3\STD" -I"\SIC3\STDC" -I"\SIC3\FT2" -
I"\SIC3\CO2" -I"C:\xHB1\include" -I"C:\xHB1\include\w32" "F:\clientes
\OMEGA\SIC\FTIMPNOT.PRG"<<<
Type: C >>>Couldn't build: FTIMPNOT.obj<<<
Type: C >>>TMAKEOBJECT<<<
Type: C >>>TMAKEOBJECT:REFRESH<<<
Type: N >>> 1278<<<
My xharbour is: xHarbour Compiler build 0.99.70 (SimpLex) 1999-2006,
http://www.xharbour.org http://www.harbour-project.org/
Thanks in advance.
cul...@gmail.com
May 16, 2012, 1:10:36 PM5/16/12
to
First
disable UAC, and better is use windows xp with this version
Regards
Luiz
disable UAC, and better is use windows xp with this version
Regards
Luiz
dlzc
May 16, 2012, 3:34:20 PM5/16/12
to
Dear vrs:
What are your permissions to the drive and directory that you are building this in?
What is the availability of the path F:\clientes\OMEGA\SIC\?
What is the availability of the path H:\CLIPPER5\INCLUDE?
You have an potentially incomplete paths in \SIC3\STD, \SIC3\STDC, \SIC3\FT2, and \SIC3\CO2. What drive and path are you in when you invoke this? Does this drive have a directory at the root called \SIC3?
Windoze Vi$ta and higher started enforcing directory permissions. You are guaranteed little whining from the OpSys if you stay working in your local drive \Users\"UserName", but beyond this, your hands are dragged across all the terrain than previous Windoze version used to simply pave over (if possible).
But what you have it seems to me, is an OpSys that does not have the long history of use, with "drive appendages" the WinXP session had built up over time.
David A. Smith
What is the availability of the path F:\clientes\OMEGA\SIC\?
What is the availability of the path H:\CLIPPER5\INCLUDE?
You have an potentially incomplete paths in \SIC3\STD, \SIC3\STDC, \SIC3\FT2, and \SIC3\CO2. What drive and path are you in when you invoke this? Does this drive have a directory at the root called \SIC3?
Windoze Vi$ta and higher started enforcing directory permissions. You are guaranteed little whining from the OpSys if you stay working in your local drive \Users\"UserName", but beyond this, your hands are dragged across all the terrain than previous Windoze version used to simply pave over (if possible).
But what you have it seems to me, is an OpSys that does not have the long history of use, with "drive appendages" the WinXP session had built up over time.
David A. Smith
vrs
May 18, 2012, 3:04:41 PM5/18/12
to
On 16 maio, 16:34, dlzc <dl...@cox.net> wrote:
> Dear vrs:
>
>
>
>
>
>
>
>
>
> On Wednesday, May 16, 2012 7:42:00 AM UTC-7, vrs wrote:
> > Hi,
>
> > I used to create my systems with xharbour in a
> > machine with windowsxp sp3. And always works
> > pretty well.
> > Now i change to Windows7 32 bits and every time
> > i try to generate an exec, the message like
> > below appears:
> > Type: C >>>xhb.exe -o"FTIMPNOT.c" -m -n -p -q -gc0 -B -DHB_MULTI_GT -
> > I"H:\CLIPPER5\INCLUDE" -I"\SIC3\STD" -I"\SIC3\STDC" -I"\SIC3\FT2" -
> > I"\SIC3\CO2" -I"C:\xHB1\include" -I"C:\xHB1\include\w32" "F:\clientes
> > \OMEGA\SIC\FTIMPNOT.PRG"<<<
>
> > Type: C >>>Couldn't build: FTIMPNOT.obj<<<
> > Type: C >>>TMAKEOBJECT<<<
> > Type: C >>>TMAKEOBJECT:REFRESH<<<
> > Type: N >>> 1278<<<
>
> > My xharbour is: xHarbour Compiler build 0.99.70
> > (SimpLex) 1999-2006,
> >http://www.xharbour.orghttp://www.harbour-project.org/
> Dear vrs:
>
>
>
>
>
>
>
>
>
> On Wednesday, May 16, 2012 7:42:00 AM UTC-7, vrs wrote:
> > Hi,
>
> > I used to create my systems with xharbour in a
> > machine with windowsxp sp3. And always works
> > pretty well.
> > Now i change to Windows7 32 bits and every time
> > i try to generate an exec, the message like
> > below appears:
> > Type: C >>>xhb.exe -o"FTIMPNOT.c" -m -n -p -q -gc0 -B -DHB_MULTI_GT -
> > I"H:\CLIPPER5\INCLUDE" -I"\SIC3\STD" -I"\SIC3\STDC" -I"\SIC3\FT2" -
> > I"\SIC3\CO2" -I"C:\xHB1\include" -I"C:\xHB1\include\w32" "F:\clientes
> > \OMEGA\SIC\FTIMPNOT.PRG"<<<
>
> > Type: C >>>Couldn't build: FTIMPNOT.obj<<<
> > Type: C >>>TMAKEOBJECT<<<
> > Type: C >>>TMAKEOBJECT:REFRESH<<<
> > Type: N >>> 1278<<<
>
> > My xharbour is: xHarbour Compiler build 0.99.70
> > (SimpLex) 1999-2006,
>
> > Thanks in advance.
>
> What are your permissions to the drive and directory that you are building this in?
>
> What is the availability of the path F:\clientes\OMEGA\SIC\?
>
> What is the availability of the path H:\CLIPPER5\INCLUDE?
>
> You have an potentially incomplete paths in \SIC3\STD, \SIC3\STDC, \SIC3\FT2, and \SIC3\CO2. What drive and path are you in when you invoke this? Does this drive have a directory at the root called \SIC3?
>
> Windoze Vi$ta and higher started enforcing directory permissions. You are guaranteed little whining from the OpSys if you stay working in your local drive \Users\"UserName", but beyond this, your hands are dragged across all the terrain than previous Windoze version used to simply pave over (if possible).
>
> But what you have it seems to me, is an OpSys that does not have the long history of use, with "drive appendages" the WinXP session had built up over time.
>
> David A. Smith
Hi,
> > Thanks in advance.
>
> What are your permissions to the drive and directory that you are building this in?
>
> What is the availability of the path F:\clientes\OMEGA\SIC\?
>
> What is the availability of the path H:\CLIPPER5\INCLUDE?
>
> You have an potentially incomplete paths in \SIC3\STD, \SIC3\STDC, \SIC3\FT2, and \SIC3\CO2. What drive and path are you in when you invoke this? Does this drive have a directory at the root called \SIC3?
>
> Windoze Vi$ta and higher started enforcing directory permissions. You are guaranteed little whining from the OpSys if you stay working in your local drive \Users\"UserName", but beyond this, your hands are dragged across all the terrain than previous Windoze version used to simply pave over (if possible).
>
> But what you have it seems to me, is an OpSys that does not have the long history of use, with "drive appendages" the WinXP session had built up over time.
>
> David A. Smith
I tried both solutions. It doesn´t work...
Disabled UAC and gave pmissions to all involved paths to the user( My
user is an administrator).
Then I tried to use the compiling and linking process via command line
and works fine.(xhb.exe e xlink.exe). The xbuild.exe has the same
problem of xbuildw.exe
Temporarily, I installed the xharbour free 1.2.1(using bcc58.and
ilink32)...and rebuilt the systems as needed.
Thanks,
Vilson
dlzc
May 18, 2012, 4:53:27 PM5/18/12
to
Dear vrs:
On Friday, May 18, 2012 12:04:41 PM UTC-7, vrs wrote:
> On 16 maio, 16:34, dlzc <dl...@cox.net> wrote:
...
> Disabled UAC and gave pmissions to all involved
> paths to the user( My user is an administrator).
This does not mean that applications will not trigger the UAC warning screen, and the EXE will not execute until you give the process explicit permission. However stupid that decision was on M$ part...
> Temporarily, I installed the xharbour free 1.2.1
>(using bcc58.and ilink32)...and rebuilt the
> systems as needed.
OK, so are your needs met? If not, please give us the entire error message as to why an application did not compile, and maybe we can help you.
David A. Smith
On Friday, May 18, 2012 12:04:41 PM UTC-7, vrs wrote:
> On 16 maio, 16:34, dlzc <dl...@cox.net> wrote:
> > What are your permissions to the drive and
> > directory that you are building this in?
> >
> > What is the availability of the path
> > F:\clientes\OMEGA\SIC\?
> >
> > What is the availability of the path
> > H:\CLIPPER5\INCLUDE?
> >
> > You have an potentially incomplete paths in
> > \SIC3\STD, \SIC3\STDC, \SIC3\FT2, and
> > \SIC3\CO2. What drive and path are you in
> > when you invoke this? Does this drive have
> > a directory at the root called \SIC3?
> >
> > Windoze Vi$ta and higher started enforcing
> > directory permissions. You are guaranteed
> > little whining from the OpSys if you stay
> > working in your local drive \Users\"UserName",
> > but beyond this, your hands are dragged
> > across all the terrain than previous Windoze
> > version used to simply pave over (if possible).
> >
> > But what you have it seems to me, is an
> > OpSys that does not have the long history
> > of use, with "drive appendages" the WinXP
> > session had built up over time.
>
> > directory that you are building this in?
> >
> > What is the availability of the path
> > F:\clientes\OMEGA\SIC\?
> >
> > What is the availability of the path
> > H:\CLIPPER5\INCLUDE?
> >
> > You have an potentially incomplete paths in
> > \SIC3\STD, \SIC3\STDC, \SIC3\FT2, and
> > \SIC3\CO2. What drive and path are you in
> > when you invoke this? Does this drive have
> > a directory at the root called \SIC3?
> >
> > Windoze Vi$ta and higher started enforcing
> > directory permissions. You are guaranteed
> > little whining from the OpSys if you stay
> > working in your local drive \Users\"UserName",
> > but beyond this, your hands are dragged
> > across all the terrain than previous Windoze
> > version used to simply pave over (if possible).
> >
> > But what you have it seems to me, is an
> > OpSys that does not have the long history
> > of use, with "drive appendages" the WinXP
> > session had built up over time.
>
> I tried both solutions. It doesn´t work...
I didn't provide a solution, I asked questions, to which you provided no answers.
> Disabled UAC and gave pmissions to all involved
> paths to the user( My user is an administrator).
> Temporarily, I installed the xharbour free 1.2.1
>(using bcc58.and ilink32)...and rebuilt the
> systems as needed.
David A. Smith
vrs
May 18, 2012, 5:05:33 PM5/18/12
to
Till now, everything is working fine with this new version and I think
I´ll adopt it.
Thanks a lot.
Regards
Vilson
vrs
May 18, 2012, 5:00:56 PM5/18/12
to
On 18 maio, 17:53, dlzc <dl...@cox.net> wrote:
accomplished.
Thanks a lot.
Regards,
Vilson
0 new messages