Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

Subject: Re: [OMPI users] flex.exe
From: Shiqing Fan (fan_at_[hidden])
Date: 2010-01-22 08:07:15


Yes, that should work but only with newer version of flex, I didn't
think about it before. But the windows flex.exe should still be
available for svn checkout build.

Thanks,
Shiqing

Jeff Squyres (jsquyres) wrote:
>
> What prevents us from generating the code during make dist time and
> therefore not shipping flex.exe?
>
> -jms
> Sent from my PDA. No type good.
>
> ----- Original Message -----
> From: Shiqing Fan <fan_at_[hidden]>
> To: Open MPI Users <users_at_[hidden]>
> Cc: Jeff Squyres (jsquyres)
> Sent: Fri Jan 22 03:56:52 2010
> Subject: Re: [OMPI users] flex.exe
>
> Hi,
>
> No, that's not true, we did ship the flex-generated code a time ago, but
> as that part of code changes sometimes, we decided to generate it during
> compilation time, and the flex.exe came with the first support of
> Windows (CMake).
>
>
> Regards,
> Shiqing
>
> Jeff Squyres wrote:
> > Don't we ship the flex-generated code in the tarball anyway? If so,
> why do we ship flex.exe?
> >
> > On Jan 21, 2010, at 12:14 PM, Barrett, Brian W wrote:
> >
> >
> >> I have to agree with the two requests here. Having either a windows
> tarball or a windows build tools tarball doesn't seem too burdensom,
> and could even be done automatically at make dist time.
> >>
> >> Brian
> >>
> >>
> >> ----- Original Message -----
> >> From: users-bounces_at_[hidden] <users-bounces_at_[hidden]>
> >> To: users_at_[hidden] <users_at_[hidden]>
> >> Sent: Thu Jan 21 10:05:03 2010
> >> Subject: Re: [OMPI users] flex.exe
> >>
> >> Am Donnerstag, den 21.01.2010, 11:52 -0500 schrieb Michael Di Domenico:
> >>
> >>> openmpi-1.4.1/contrib/platform/win32/bin/flex.exe
> >>>
> >>> I understand this file might be required for building on windows,
> >>> since I'm not I can just delete the file without issue.
> >>>
> >>> However, for those of us under import restrictions, where binaries are
> >>> not allowed in, this file causes me to open the tarball and delete the
> >>> file (not a big deal, i know, i know).
> >>>
> >>> But, can I put up a vote for a pure source only tree?
> >>>
> >> I'm very much in favor of that since we can't ship this binary in
> >> Debian. We'd have to delete it from the tarball and repack it with
> every
> >> release which is quite cumbersome. If these tools could be shipped in a
> >> separate tarball that would be great!
> >>
> >> Best regards
> >> Manuel
> >>
> >> _______________________________________________
> >> users mailing list
> >> users_at_[hidden]
> >> http://www.open-mpi.org/mailman/listinfo.cgi/users
> >>
> >>
> >> _______________________________________________
> >> users mailing list
> >> users_at_[hidden]
> >> http://www.open-mpi.org/mailman/listinfo.cgi/users
> >>
> >>
> >
> >
> >
>
>
> --
> --------------------------------------------------------------
> Shiqing Fan http://www.hlrs.de/people/fan
> High Performance Computing Tel.: +49 711 685 87234
> Center Stuttgart (HLRS) Fax.: +49 711 685 65832
> Address:Allmandring 30 email: fan_at_[hidden]
> 70569 Stuttgart
>

-- 
--------------------------------------------------------------
Shiqing Fan                          http://www.hlrs.de/people/fan
High Performance Computing           Tel.: +49 711 685 87234
  Center Stuttgart (HLRS)            Fax.: +49 711 685 65832
Address:Allmandring 30               email: fan_at_[hidden]    
70569 Stuttgart