[erlang-questions] Errors when generating tests for CosNotifications on windows.

Wed May 4 15:02:33 CEST 2011

So here is the promised update.

Changing to a path that did not truncate does not work. My guess is that
because cosNotifications is truncated it fails to find the file.

I have tried several of the compilers that are bootstrapped, built or
downloaded from the erlang.org site.

If I use any bootsrapped, self built or downloaded version of erlc I get the
above error.

If I use the version under otp/bin/win32 I get a message telling me that
erlcexec.exe can't be found, I tried scanning my computer for it but I
simply dont have it. Where is erlexec supposed to reside?

On Wed, May 4, 2011 at 8:56 AM, Fredrik Andersson <sir.sedrik@REDACTED>wrote:

> The path is not longer than 256 chars. I am using the one built and
> installed from source to generate the tests.
>
> I downloaded the latest version of cygwin when I started on this so it is
> not older than a couple of weeks. The installer is reporting 2.738 back to
> me.
>
> I currently have a new run going from a directory that has no seperate path
> longer than 8 chars to avoid the truncating in paths. Will let you know how
> it goes.
>
>
> On Wed, May 4, 2011 at 12:35 AM, OvermindDL1 <overminddl1@REDACTED>wrote:
>
>> On May 3, 2011 7:36 AM, "Niclas Eklund" <nick@REDACTED> wrote:
>> >
>> >
>> > Hello!
>> >
>> > As you've probably guessed we don't encounter this problem. ;-) But then
>> the test suites are only built once (not a Windows machine) and then re-used
>> by different plattforms. Speed things up.
>> >
>> > Since there is a 256 chars limit (Windows paths and command line), this
>> might be it. I suppose that a faulty setting of one of the Erlang related
>> environment variables (e.g. ERL_TOP) could cause problems as well. Perhaps
>> you can e-mail them to me?
>>
>> As I recall Windows has a limit if 4096 per complete path if using the NT
>> api for note.  512 if 8.3 format is enabled in the registry.
>>
>> >
>> > Due to the fact that CosNotification depends on several other
>> Cos-services, more IDL files needs to be included compared with, for
>> example, CosTime.
>> >
>> > Best Regards,
>> >
>> > Niclas @ Erlang/OTP
>> >
>> >
>> > On Thu, 21 Apr 2011, Fredrik Andersson wrote:
>> >
>> >> On Thu, Apr 21, 2011 at 11:04 AM, Alexander Krasnukhin <
>> >> the.malkolm@REDACTED> wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> It is just a guess and probably sounds stupid but could you try to
>> compile
>> >>> within the folder with smaller path length?
>> >>>
>> >>
>> >> I tried moving the otp folder to / and it had no difference, I can make
>> them
>> >> all compile if I cp the idl files to the test folder of cosNotification
>> but
>> >> that seems to be a suboptimal way of doing things.
>> >>
>> >>
>> >>>
>> >>> On Thu, Apr 21, 2011 at 10:57 AM, Fredrik Andersson <
>> sir.sedrik@REDACTED>wrote:
>> >>>
>> >>>> Hi all
>> >>>>
>> >>>> I want to run the test suites on my windows build but I am running
>> into
>> >>>> trouble when generating the tests for CosNotification. I can
>> reproduce the
>> >>>> error by building the tests inside of otp/lib/CosNotification/test
>> using
>> >>>> make tests.
>> >>>>
>> >>>> Can anyone help?
>> >>>>
>> >>>> The following is the error I get. I have verified that the idl files
>> are
>> >>>> present in the src directory.
>> >>>>
>> >>>> erlc +debug_info -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/lib/cosNotification/ebin -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/lib/cosNotification/src -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/lib/cosTime/ebin -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/lib/cosTime/include -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/lib/orber/ebin -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/lib/ic/ebin -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/lib/cosNotification/include
>> >>>> -I/home/ESLbingen/bingen/tmp/otp/lib/cosEvent/src
>> >>>> -I/home/ESLbingen/bingen/tmp/otp/lib/cosNotification/include  -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/lib/orber/include -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/internal_tools/test_server/ebin -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/lib/cosNotification/ebin -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/lib/cosNotification/test/idl_output
>> -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/lib/cosTime/ebin -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/lib/cosTime/include -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/lib/cosNotification/include -pa
>> >>>> /home/ESLbingen/bingen/tmp/otp/lib/ic/ebin
>> >>>> -I/home/ESLbingen/bingen/tmp/otp/lib/cosTime/ebin
>> >>>> -I/home/ESLbingen/bingen/tmp/otp/lib/cosTime/include
>> >>>> -I/home/ESLbingen/bingen/tmp/otp/lib/orber/include
>> >>>> -I/home/ESLbingen/bingen/tmp/otp/lib/cosNotification/src
>> >>>> -I/home/ESLbingen/bingen/tmp/otp/lib/cosNotification/include
>> >>>> -I/home/ESLbingen/bingen/tmp/otp/lib/cosNotification
>> >>>> -I/home/ESLbingen/bingen/tmp/otp/lib/cosNotification/test/idl_output
>> >>>> -I/home/ESLbingen/bingen/tmp/otp/lib/test_server/include -oidl_output
>> \
>> >>>>                +'{cfgfile,"notify_test_server.cfg"}'
>> >>>> notify_test_server.idl
>> >>>> []: warning: unrecognised option: debug_info
>> >>>> Erlang IDL compiler version 4.2.26
>> >>>>
>> "c:/cygwin/home/ESLBIN~1/bingen/tmp/otp/lib/COSNOT~1/test/notify_test_server.idl":
>> >>>> preprocessor error:
>> >>>>
>> c:/cygwin/home/ESLBIN~1/bingen/tmp/otp/lib/COSNOT~1/test/notify_test_server.idl:23:
>> >>>> CosNotification.idl: No such file or directory
>> >>>>
>> "c:/cygwin/home/ESLBIN~1/bingen/tmp/otp/lib/COSNOT~1/test/notify_test_server.idl":
>> >>>> preprocessor error:
>> >>>>
>> c:/cygwin/home/ESLBIN~1/bingen/tmp/otp/lib/COSNOT~1/test/notify_test_server.idl:24:
>> >>>> CosNotifyComm.idl: No such file or directory
>> >>>>
>> "c:/cygwin/home/ESLBIN~1/bingen/tmp/otp/lib/COSNOT~1/test/notify_test_server.idl":
>> >>>> 2 errors found
>> >>>>
>> >>>>
>> >>>> _______________________________________________
>> >>>> erlang-questions mailing list
>> >>>> erlang-questions@REDACTED
>> >>>> http://erlang.org/mailman/listinfo/erlang-questions
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> Regards,
>> >>> Alexander
>> >>>
>> >>>
>> >>
>> >
>> >
>> > _______________________________________________
>> > erlang-questions mailing list
>> > erlang-questions@REDACTED
>> > http://erlang.org/mailman/listinfo/erlang-questions
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20110504/21a7835a/attachment.htm>