[Devel] Re: approaching testing phase for 1.2.0

Bogdan-Andrei Iancu bogdan at voice-system.ro
Mon Feb 12 19:20:34 CET 2007


Hi Ovidiu,

the suggested fix is on the cvs - please test and let me know if there 
are any other issues.
Could you also please take a look on the 1653550 ?

regards,
bogdan

Ovidiu Sas wrote:
> Hi Bogdan,
>
> I think this is a viable solution.
> And thank you for you time.  I know that this is not a big issue for
> most of the openser users, but it will make openser portable to
> several platforms.
>
>
> Regards,
> Ovidiu Sas
>
> On 2/9/07, Bogdan-Andrei Iancu <bogdan at voice-system.ro> wrote:
>> Hi Ovidiu,
>>
>> as posted on the tracker, the pache you provided break compiling on the
>> normal systems as the include files from installed libs are not
>> foundable anymore.
>>
>> I understand the problem and I guess a proper fix will be to introduce a
>> new makefile variable $SYSBASE. this will be by default "/usr/"; if you
>> do cross-compiling, you will override it to "/my/staging/base/" . The
>> Makefiles will be update from :
>>
>> # mysql.h locations (freebsd,openbsd  solaris)
>> DEFS +=-I$(LOCALBASE)/include -I$(LOCALBASE)/include/mysql \
>>         -I$(LOCALBASE)/mysql/include/mysql 
>> -I$(LOCALBASE)/mysql/include \
>>         -I/usr/include/mysql
>>
>> # libmysqlclient locations on RH/Suse, Solaris /OpenBSD, FreeBSD
>> # (Debian does the right thing and puts it in /usr/lib)
>> LIBS=-L/usr/lib/mysql -L$(LOCALBASE)/lib -L$(LOCALBASE)/lib/mysql \
>>         -L$(LOCALBASE)/mysql/lib/mysql/ \
>>         -L$(LOCALBASE)/mysql/lib \
>>         -L/usr/lib64/mysql \
>>         -lm -lmysqlclient -lz
>>
>> to:
>>
>> # mysql.h locations (freebsd,openbsd  solaris)
>> DEFS +=-I$(LOCALBASE)/include -I$(LOCALBASE)/include/mysql \
>>         -I$(LOCALBASE)/mysql/include/mysql 
>> -I$(LOCALBASE)/mysql/include \
>>         -I$(SYSBASE)/include/mysql
>>
>> # libmysqlclient locations on RH/Suse, Solaris /OpenBSD, FreeBSD
>> # (Debian does the right thing and puts it in /usr/lib)
>> LIBS=-L/usr/lib/mysql -L$(LOCALBASE)/lib -L$(LOCALBASE)/lib/mysql \
>>         -L$(LOCALBASE)/mysql/lib/mysql/ \
>>         -L$(LOCALBASE)/mysql/lib \
>>         -L$(SYSBASE)/lib64/mysql \
>>         -lm -lmysqlclient -lz
>>
>> probably LOCALBASE will have also to be computed base on SYSBASE.
>>
>> what do you think about this?
>>
>> regards,
>> bogdan
>>
>>
>> Ovidiu Sas wrote:
>> > Hi Bogdan,
>> >
>> > It is a check against bogus includes while doing cross-compilation.
>> > When cross-compiling, includes should be picked from a staging
>> > directory and not from the build machine.  This will ensure that the
>> > package will be compiled with the right headers (from the staging
>> > directory) and not with headers from the build machine.
>> >
>> > The "default" openser modules are compiling ok.  Only a few modules
>> > are exhibiting this issue.
>> >
>> > For your reference:
>> > 
>> http://swik.net/OpenEmbedded/OpenEmbedded+News/The+Q%2FA+team+strikes+back!/gml3 
>>
>> >
>> >
>> >
>> > Regards,
>> > Ovidiu Sas
>> >
>> > On 2/2/07, Bogdan-Andrei Iancu <bogdan at voice-system.ro> wrote:
>> >> Hi Ovidiu,
>> >>
>> >> first of all, do you have any idea why gcc does not like the
>> >> /usr/include dir in INCLUDEPATH ? any reason?
>> >>
>> >> regards,
>> >> bogdan
>> >>
>> >>
>> >> Ovidiu Sas wrote:
>> >>
>> >> > Hi Bogdan,
>> >> >
>> >> > Speaking of builds, while cross compiling, the new gcc compiler
>> >> > doesn't like /usr/include in INCLUDEPATH:
>> >> >
>> >> > make[2]: Entering directory
>> >> >
>> >> 
>> `/home/admin/slug-optware-slugosbe-dev/optware/builds/openser/modules/pa' 
>>
>> >>
>> >> > CROSS COMPILE Badness: /usr/include in INCLUDEPATH:
>> >> /usr/include/libxml2
>> >> > cc1: internal compiler error: Aborted
>> >> > Please submit a full bug report,
>> >> > with preprocessed source if appropriate.
>> >> > See <URL:http://gcc.gnu.org/bugs.html> for instructions.
>> >> >
>> >> >
>> >> > There are a few modules affected by this.  Is is possible to fix 
>> the
>> >> > Makefile for this modules.  Here's a dirty patch that I made to
>> >> > circumvent this problem, but I wonder if we prepend $(LOCALBASE) in
>> >> > front of each include, will this work ok for other platforms?
>> >> >
>> >> 




More information about the Devel mailing list