* Warning: C compiler not invoked (1)

727 views
Skip to first unread message

mvukovic

unread,
Feb 20, 2009, 3:52:26 AM2/20/09
to multisoft FlagShip
Hello. I'm trying to compile some program with FS6 and I get this
error:

$ FlagShip pdft.prg test_pdf.prg -o test

FlagShip PRO (unlimited users)
-- FS compiler phase:
365 Pass1: pdft.prg
25 Pass1: test_pdf.prg

** Warning: C compiler not invoked (1).

It doesn't show any other message about in what line is the error or
anything like that.
Any ideas?
Thanks

Paul Berger

unread,
Feb 20, 2009, 6:05:47 AM2/20/09
to multisoft FlagShip
If your system is Linux with kernel 2.6.x (check by "uname -a"):

1) compile both programs separately by e.g. "FlagShip -c [-na] [-v]
test_pdf.prg pdft.prg"
but do not use the -q switch. You will see the problematic statement
number just above the warning, e.g.
-- FS compiler phase:
365 Pass1: pdft.prg
25 Pass1: test_pdf.prg
** Warning: C compiler not invoked (1).

2) if the displayed statement (+/-1) in your source (here line#25 of
test_pdf.prg) is a continuation, it is kernel stack overflow. In
kernels 2.6.x this default value was decreased, compared to previous
releases, see Kernel Release Notes and "man ulimit". You may:
a) increase the limit by "ulimit -s 20000"
b) or globally in /etc/security/limits.conf or /etc/sysconfig/ulimit
(depends on Linux distribution)
c) split the continuation statement

3) otherwise contact 'support at flagship dot de' and provide (in
binary attachment or in .tar.gz/.tgz archive) the .prg source causing
your problem. Specify also used VFS version ("FlagShip -version") and
your compiler switches. Refer to http://www.fship.com/support.html for
further details.

Paul

Angelos Christodoulou

unread,
Feb 20, 2009, 7:45:16 AM2/20/09
to multisoft...@googlegroups.com

Is this the print to pdf program that we supplied?

Is so - please remind me the date on the .prg + I will look @ it over the weekend. Is it possibly that we had done something in FSTools and you are not running the tools? Paul Berger may be able to answer that, ie. does the compiler behave as such if a call to a FSTools function is made and it is not included in the installation…?

 

Regards

 

Angelos Christodoulou

Cell:  +27 82 491 0964

Tel:   +27 33 343 6000

Fax:  +27 33 343 6001

Web: www.accpick.co.za

 

No virus found in this incoming message.

Checked by AVG.

Version: 7.5.552 / Virus Database: 270.11.1/1961 - Release Date: 19/02/2009 06:45 PM

 


No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.552 / Virus Database: 270.11.1/1961 - Release Date: 19/02/2009 06:45 PM

mvukovic

unread,
Mar 12, 2009, 12:17:02 PM3/12/09
to multisoft FlagShip
The date on the file test_pdf.prg is "16/Oct/2008 15:21"

I've tried what Paul suggested (uname -s 20000) and now I got this
error:

$ FlagShip test_pdf.prg pdft.prg -o test_pdf

FlagShip PRO (unlimited users)
-- FS compiler phase:
90 Pass2: test_pdf.prg
2752 Pass2: pdft.prg
-- C compiler and linker phase:
/home/faster/tmp/ccx4wou1.o: In function `_bb_pdffilepri':
pdft.c:(.text+0x4709a): undefined reference to `_bb_dirname'
pdft.c:(.text+0x4717c): undefined reference to `_bb_dirchange'
pdft.c:(.text+0x47421): undefined reference to `_bb_dirname'
pdft.c:(.text+0x47665): undefined reference to `_bb_dirchange'
collect2: ld returned 1 exit status

** Warning: C compiler or linker error (256).
Object file and executable not created or is invalid!

I don't think I have FSUtils, but, how can I check if I do?
Thank you!

Martín.

Paul Berger

unread,
Mar 12, 2009, 12:43:38 PM3/12/09
to multisoft FlagShip
This linker message says, the above listed functions dirname() and
dirchange() are not linked with your application. These are available
in FS2 Toolbox, see also the on-line manual fsman section FS2.

On Linux, you may check your installation in the log file
/var/log/FlagShip.log, type "less /var/log/FlagShip.log" and
check your reply for the question

Do you have also Activation key for VFS/FS2 Toolbox (y/N) ?

Paul

Paul

unread,
Dec 4, 2015, 10:46:32 AM12/4/15
to multisoft...@googlegroups.com, multisoft...@googlegroups.com, martin...@gmail.com
On Linux with newer kernel, the stack setting was decreased by default (check by "ulimit -s").
This may cause stack problem during the compilation, i.e. the message "Warning: C compiler not invoked" is displayed w/o further warnings
(for example w/o message displaying an incorrect syntax etc). If so, simply increase the default stack by e.g. "ulimit -s 20000" and invoke FlagShip... anew.
See also my previous posting here.

Paul
Reply all
Reply to author
Forward
0 new messages