Search found 165 matches
- Mar 25, 2015 15:29
- Forum: General
- Topic: RTLIB on OSX compile error, .section on darwin
- Replies: 13
- Views: 2706
Re: RTLIB on OSX compile error, .section on darwin
Only newer versions do. XCode 3.2.x comes with GCC 4.2. But nethertheless, good C code should compile on any standard conformant C compiler. Unfortunately FB's rtlib contains some code which only compiles with GCC. Ideally fbc should compile on Mac using the native tools (clang) and using the nativ...
- Mar 25, 2015 4:05
- Forum: General
- Topic: RTLIB on OSX compile error, .section on darwin
- Replies: 13
- Views: 2706
Re: RTLIB on OSX compile error, .section on darwin
Nice to see that someone else is working on a darwin build too :-) I've worked on darwin builds in the last few days for my automated build system. Finally I'd like to cross compile from linux, but for now I've built a x86 version of fbc for darwin on an old OS X (10.6.8). I had to apply some patch...
- Mar 24, 2015 12:52
- Forum: General
- Topic: RTLIB on OSX compile error, .section on darwin
- Replies: 13
- Views: 2706
Re: RTLIB on OSX compile error, .section on darwin
I think the rtlib's Darwin port is incomplete, for example: fb_hGetExePath() exists for linux, win32, dos, *bsd, but not darwin. That will probably need to be implemented first. I have wondered, why don't we move to higher level compiler independent C/C++ code in -gen gcc instead of relying on rtli...
- Mar 24, 2015 9:14
- Forum: General
- Topic: RTLIB on OSX compile error, .section on darwin
- Replies: 13
- Views: 2706
Re: RTLIB on OSX compile error, .section on darwin
I installed GCC49 (4.9.2) from homebrew. Hi, fbrt0.c: If the Darwin/MacOSX-specific changes work for you, I can add them to Git. Although, maybe it's time we start using __attribute__((constructor|destructor)) directly. (This does work on MacOSX right?) No way to know it works until FBC is compiled ...
- Mar 23, 2015 7:07
- Forum: General
- Topic: RTLIB on OSX compile error, .section on darwin
- Replies: 13
- Views: 2706
indirect goto in function with no address-of-label expressio
I carried on with trying to compile the FreeBASIC compiler, as libraries are basically 'done'. But there are new set of errors, probably clang specific.... I gave the following command gcc -o fbc -std=c11 -nostdinc -Wall -Wno-unused-label -Wno-unused-function -Wno-unused-variable -Wno-main -fno-stri...
- Mar 23, 2015 6:47
- Forum: General
- Topic: RTLIB on OSX compile error, .section on darwin
- Replies: 13
- Views: 2706
rtlib fix and libgfx compile error
I applied following fix to fbrt0.c to make it work: #ifdef HOST_DARWIN -static void * priorityhDoInit __attribute__((section(".ctors.65435,"), used)) = fb_hDoInit; -static void * priorityhDoExit __attribute__((section(".dtors.65435,"), used)) = fb_hDoExit; +static void * priority...
- Mar 23, 2015 4:04
- Forum: General
- Topic: RTLIB on OSX compile error, .section on darwin
- Replies: 13
- Views: 2706
RTLIB on OSX compile error, .section on darwin
I was following- http://www.freebasic.net/wiki/wikka.php?wakka=DevBootstrap To get Darwin x86_64 FreeBASIC 1.02.0 from latest sources in github. I have a working 1.02.0 on x86_64 linux (ubuntu 14.04) platform. Did this on ubuntu first: fbc -e -m fbc src/compiler/*.bas -r -target darwin -arch x86_64 ...
- Jan 05, 2015 21:54
- Forum: Libraries Questions
- Topic: FastCGI library support in 64bit FB?
- Replies: 4
- Views: 2164
Re: FastCGI library support in 64bit FB?
thank you :)
- Jan 02, 2015 5:41
- Forum: Libraries Questions
- Topic: FastCGI library support in 64bit FB?
- Replies: 4
- Views: 2164
Re: FastCGI library support in 64bit FB?
Can x86 headers be used instead??
- Dec 31, 2014 17:40
- Forum: Libraries Questions
- Topic: FastCGI library support in 64bit FB?
- Replies: 4
- Views: 2164
FastCGI library support in 64bit FB?
I tried to compile example [ur=https://github.com/freebasic/fbc/blob/master/examples/manual/libraries/fastcgi.basl]fastcgi program[/url] on ubuntu 14.10 x86_64 and I get the following error: harshvardhan@bhagavati:~/Desktop$ fbc test.bas test.bas(9) error 23: File not found, "fastcgi/fcgi_stdio...
- Nov 13, 2014 16:54
- Forum: General
- Topic: Issues Compiling for OS X Mavericks
- Replies: 5
- Views: 1808
Re: Issues Compiling for OS X Mavericks
There was a method in which you actually compile FBC on linux x86_64 to get the .C output and then compile it on the target system? I once read a wiki article on it, but can't find it now. Can somebody give me the link?
- Nov 04, 2014 16:08
- Forum: General
- Topic: Issues Compiling for OS X Mavericks
- Replies: 5
- Views: 1808
Re: Issues Compiling for OS X Mavericks
Since it looks like it's a standalone build, it will probably need those files in the lib/darwin/ directory. Try to find where they're installed on your system; perhaps one of these commands will help you: gcc -print-file-name=crt1.o locate crt1.o then copy them into the lib/darwin/ directory of th...
- Nov 04, 2014 13:35
- Forum: General
- Topic: Issues Compiling for OS X Mavericks
- Replies: 5
- Views: 1808
crt1.o problems
I replaced the select...case by if..then..else and now the code compiled very well but during linking there was an error. It was not able to find crt1.o, gcrt1.o and libsupc++.a I assume it isn't able to find 32 bit libraries of them? A test done by me gave following result: harshvardhan$ /Users/har...
- Nov 04, 2014 12:39
- Forum: General
- Topic: Issues Compiling for OS X Mavericks
- Replies: 5
- Views: 1808
Issues Compiling for OS X Mavericks
I am trying to compile latest FBC 1.0 using old FreeBASIC 0.22.0 which was available. But I encounter the following issue. Any solution other than using if...then...else instead? Warning 1053: Common constant converted to public: _ENVFBC src/compiler/obj/hlp.o FreeBASIC Compiler - Version 0.22.0 (10...
- Sep 14, 2014 7:13
- Forum: Windows
- Topic: CPUDETECT.S, error building rtlib on windows
- Replies: 22
- Views: 6621
Re: CPUDETECT.S, error building rtlib on windows
There would really be no need of translating the C code into FBC, just this is needed to be done: 1. Understading C build-in/factory types. 2. Recognizing declared functions, variables, etc. 3. Then just use the C header directly using C compiler. Theortically, this is a simple solution to use the C...