On Fri 01 Oct 2010 at 23:42:30 PDT Chetan Shukla wrote:
Hi,
Could someone please outline the steps needed in porting a general
application from Linux to FreeBSD.
As others have already pointed out, there are no shortcuts to the
righthand side of the learning curve.
For most apps, the usual "co
On Sat, Oct 2, 2010 at 2:42 AM, Chetan Shukla wrote:
> Hi,
> Could someone please outline the steps needed in porting a general
> application from
> Linux to FreeBSD.
>
>
> Thanks & Regards,
> Chetan
You may want to have a look at http://wiki.freebsd.org/AvoidingLinuxisms
If you ask a more speci
On 02/10/2010 08:42, Chetan Shukla wrote:
> Hi,
> Could someone please outline the steps needed in porting a general
> application from
> Linux to FreeBSD.
If the thing is not tightly coupled to the kernel, the general
compile guide to the software you try to compile will suffice
most of the time
> On 02/10/2010 07:42:30, Chetan Shukla wrote:
>
> > Could someone please outline the steps needed in porting a general appl=
> ication from
> > Linux to FreeBSD.
>
> Step 1) Spend time (probably several years) achieving a reasonable level
> of expertise in the languages and concepts involved.
.
Or you could simply start at step 3, then for every problem you have in step
4, Google it. For the problems you cannot fix that way, ask (smart)
questions on the appropriate FreeBSD mailing lists, until the application
compiles. Then continue to step 5.
Note: the learning curve will be steep, take
On 02/10/2010 07:42:30, Chetan Shukla wrote:
> Could someone please outline the steps needed in porting a general
> application from
> Linux to FreeBSD.
Step 1) Spend time (probably several years) achieving a reasonable level
of expertise in the languages and concepts involved.
Step 2) During t
Hi,
Could someone please outline the steps needed in porting a general application
from
Linux to FreeBSD.
Thanks & Regards,
Chetan
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for
the use of the individual to whom it is addressed.
Am 08.06.2009, 21:15 Uhr, schrieb Peter Jeremy
:
On 2009-Jun-08 11:33:27 -0400, Robert Huff wrote:
Alexander Leidinger writes:
> Right: I re-ran under bash, and got the same problems.
> Looking at configure.ac, I see:
>
> AC_PATH_PROG(YACC,byacc,no)
> if test "x$YACC" == "xno"
Th
Alexander Leidinger writes:
> >Quick checking suggests libttf is a Linux-ism, replaced by
> > libfreetype. Is this correct, and if so can I just (temporarily)
> > make the change in the list of libraries?
>
> Why not just try it?
>
> Note, there is/was freetype1 and freetype2...
Quoting Robert Huff (from Tue, 9 Jun 2009
08:34:46 -0400):
Alexander Leidinger writes:
>> Obvious question but if you edited configure.ac, you did remember to
>> rerun autoconf afterwards didn't you?
>
> Uh ... no. (When I said "complete novice", wasn't kidding. :-)
Not knowing
Robert Huff wrote:
Alexander Leidinger writes:
>> Obvious question but if you edited configure.ac, you did remember to
>> rerun autoconf afterwards didn't you?
>
> Uh ... no. (When I said "complete novice", wasn't kidding. :-)
Not knowing C/++ when you want to port a C/C++ progra
Alexander Leidinger writes:
> >> Obvious question but if you edited configure.ac, you did remember to
> >> rerun autoconf afterwards didn't you?
> >
> >Uh ... no. (When I said "complete novice", wasn't kidding. :-)
>
> Not knowing C/++ when you want to port a C/C++ program makes it
Quoting Robert Huff (from Mon, 8 Jun 2009
16:36:58 -0400):
Peter Jeremy writes:
>> > for ac_remove_CFLAG in "-O1" "-O2" "-O3" ; do
>> > CFLAGS=${CFLAGS//${ac_remove_CFLAG}/}
>> > CPPFLAGS=${CPPFLAGS//${ac_remove_CFLAG}/}
>> > CXXFLAGS=${CXXFLAGS//${ac_remove
Robert Huff wrote:
Robert Huff writes:
Done. Merrily compiling away.
New problem.
One of the files has:
#ifdef LINUX
#include
#endif
What is the FreeBSD magic tag corresponding to "LINUX"?
"__FREEBSD__"?
Robert Huff
Robert Huff writes:
> Done. Merrily compiling away.
New problem.
One of the files has:
#ifdef LINUX
#include
#endif
What is the FreeBSD magic tag corresponding to "LINUX"?
"__FREEBSD__"?
Robert Huff
__
Lowell Gilbert writes:
> > /usr/include/malloc.h:3:2: error: #error " has been replaced by
> "
>
> Whichever file is being compiled has a line that should be changed from
> #include
> to
> #include
Done. Merrily compiling away.
_
Robert Huff writes:
> Peter Jeremy writes:
>
>
>> >> > for ac_remove_CFLAG in "-O1" "-O2" "-O3" ; do
>> >> > CFLAGS=${CFLAGS//${ac_remove_CFLAG}/}
>> >> > CPPFLAGS=${CPPFLAGS//${ac_remove_CFLAG}/}
>> >> > CXXFLAGS=${CXXFLAGS//${ac_remove_CFLAG}/}
>> >> > done
>> >>
Peter Jeremy writes:
> >> > for ac_remove_CFLAG in "-O1" "-O2" "-O3" ; do
> >> >CFLAGS=${CFLAGS//${ac_remove_CFLAG}/}
> >> >CPPFLAGS=${CPPFLAGS//${ac_remove_CFLAG}/}
> >> >CXXFLAGS=${CXXFLAGS//${ac_remove_CFLAG}/}
> >> > done
> >>
> >> Quick try:
> >> CFLA
On 2009-Jun-08 11:33:27 -0400, Robert Huff wrote:
>Alexander Leidinger writes:
>> > Right: I re-ran under bash, and got the same problems.
>> > Looking at configure.ac, I see:
>> >
>> > AC_PATH_PROG(YACC,byacc,no)
>> > if test "x$YACC" == "xno"
>>
>> This should be a "=", not a "==".
>
Alexander Leidinger writes:
> >Right: I re-ran under bash, and got the same problems.
> >Looking at configure.ac, I see:
> >
> > AC_PATH_PROG(YACC,byacc,no)
> > if test "x$YACC" == "xno"
>
> This should be a "=", not a "==".
Same result.
> >Relevant bit is:
> >
> >
Quoting Robert Huff (from Mon, 8 Jun 2009
09:53:29 -0400):
Alexander Leidinger writes:
> First problem:
Looks like bash-isms in configure.
for (i = 0; i < 10; i++) hit_forehead_with_desk();
I had already figured out replacing "make" with "gmake"; this
should have be
Alexander Leidinger writes:
> >First problem:
>
> Looks like bash-isms in configure.
for (i = 0; i < 10; i++) hit_forehead_with_desk();
I had already figured out replacing "make" with "gmake"; this
should have been obvious.
>
> >When following the instructions he
Quoting Robert Huff (from Mon, 8 Jun 2009
08:07:08 -0400):
First problem:
Looks like bash-isms in configure.
When following the instructions here
"http://ctp2.darkdust.net/anonsvn/branches/linux/doc/README.linux"; I
get to step 2 ("configure") and get this:
appending conf
On 2009-Jun-08 01:01:32 -0400, Robert Huff wrote:
> Is there anyone out there with experience porting from Linux to
>FreeBSD and/or writing code for both who can spare a few cycles to
>help a complete novice figure out what's different (and how to fix
>it)?
That's an extremely open-ended qu
Quoting Robert Huff (from Mon, 8 Jun 2009
01:01:32 -0400):
Is there anyone out there with experience porting from Linux to
FreeBSD and/or writing code for both who can spare a few cycles to
help a complete novice figure out what's different (and how to fix
it)?
Have a look at http:
Is there anyone out there with experience porting from Linux to
FreeBSD and/or writing code for both who can spare a few cycles to
help a complete novice figure out what's different (and how to fix
it)?
Respectfully,
Robert Huff
26 matches
Mail list logo
