Re: question on the 'configure' script when using a cross compiler

2009-09-28 Thread Kenton Varda
The configure script is generated by autoconf based on configure.ac.  If you
can't trace your problems back to something wrong in configure.ac (or in the
m4 subdirectory) then you will probably need to talk to the autoconf
maintainers instead.
That said, cross compiling is supported, and I've used it in particular to
compile Windows binaries on Mac.  What command-line arguments are you
passing to configure?  You should at least be passing the --host flag to set
the platform for which you are compiling, and --with-protoc to provide a
protoc binary to use during the build since obviously the one you are
building can't be executed locally.

On Mon, Sep 28, 2009 at 7:11 AM, Thomas Jagodits  wrote:

>  Hello,
>
>
>
> The following questions surfaced while using the configure script for
> protobuf  while doing cross compilation for the TI DSP C6455 Code Composer.
>
>
>
> a)  The output of that TI cross compiler only generates files that
> have obj as suffix (conftest.obj).
>
> This section of the ‘configure’ script always returns an empty ac_file and
> makes the program exit with an error.
>
> for ac_file in $ac_files ''
>
> do
>
>   test -f "$ac_file" || continue
>
>   case $ac_file in
>
> *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg |
> *.map | *.inf | *.o | *.obj )
>
> ;;
>
> b)  Similarly this check on line 2977 also fails, it may need a
> condition for cross compiler.
>
> echo $ECHO_N "checking for suffix of executables... $ECHO_C" >&6; }
>
> if { (ac_try="$ac_link"
>
> case "(($ac_try" in
>
>
>
>
>
> Is there anything specific that needs to be done for cross compilation?
> ‘cross_compiling’ is being set to true and all the paths to the cross
> compiler environment are proper.
>
> Please indicate if the corresponding config.log should be forwarded.
>
>
>
> Thanks,
>
> Thomas Jagodits
>
> Hughes network Systems
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to protobuf@googlegroups.com
To unsubscribe from this group, send email to 
protobuf+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/protobuf?hl=en
-~--~~~~--~~--~--~---



question on the 'configure' script when using a cross compiler

2009-09-28 Thread Thomas Jagodits
Hello,

The following questions surfaced while using the configure script for protobuf  
while doing cross compilation for the TI DSP C6455 Code Composer.


a)  The output of that TI cross compiler only generates files that have obj 
as suffix (conftest.obj).

This section of the 'configure' script always returns an empty ac_file and 
makes the program exit with an error.

for ac_file in $ac_files ''

do

  test -f "$ac_file" || continue

  case $ac_file in

*.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | 
*.inf | *.o | *.obj )

;;

b)  Similarly this check on line 2977 also fails, it may need a condition 
for cross compiler.

echo $ECHO_N "checking for suffix of executables... $ECHO_C" >&6; }

if { (ac_try="$ac_link"

case "(($ac_try" in





Is there anything specific that needs to be done for cross compilation? 
'cross_compiling' is being set to true and all the paths to the cross compiler 
environment are proper.

Please indicate if the corresponding config.log should be forwarded.



Thanks,

Thomas Jagodits

Hughes network Systems

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to protobuf@googlegroups.com
To unsubscribe from this group, send email to 
protobuf+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/protobuf?hl=en
-~--~~~~--~~--~--~---