Hello list. How ftp://ftp.freepascal.org/pub/fpc/dist/2.6.2/bootstrap like lists are built? I missed at least i386-linux and i386-win32 binaries. Just to know how I will update my drafts.
Joao Morais
Mailing lists / fpc-pascal / 2013-03
Bootstrap binaries
7 messages · 5 people ·
- Joao Morais 2
- Reinier Olislagers 2
- Andreas Schneider 1
- Marco van de Voort 1
- Sven Barth 1
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Joao Morais wrote 5 lines
Hello list. How ftp://ftp.freepascal.org/pub/fpc/dist/2.6.2/bootstrap
like lists are built? I missed at least i386-linux and i386-win32
binaries. Just to know how I will update my drafts.
Joao Morais
I guess bootstrap isn't necessary when the full compiler is available. Which it is for i386-linux and i386-win32 (see directory above).
Best Regards,
Andreas
"Andreas Schneider" wrote 11 lines
On Monday, March 4, 2013, at 01:59 Joao Morais wrote:
> Hello list. How ftp://ftp.freepascal.org/pub/fpc/dist/2.6.2/bootstrap
> like lists are built? I missed at least i386-linux and i386-win32
> binaries. Just to know how I will update my drafts.
> Joao Morais
I guess bootstrap isn't necessary when the full compiler is available.
Which it is for i386-linux and i386-win32 (see directory above).
It should be available as one might want to compile trunk without having a prebuilt compiler installed.
Regards,
Sven
Hello list. How ftp://ftp.freepascal.org/pub/fpc/dist/2.6.2/bootstrap like lists are…
In our previous episode, Joao Morais said:
How ftp://ftp.freepascal.org/pub/fpc/dist/2.6.2/bootstrap like lists are built? I missed at least i386-linux and i386-win32 binaries.
They are simply the compiler binary extracted from the release in a bzipped format.
It's mainly a facility for source based package systems like the *bsd ports, where the enduser routinely bootstraps compiler + source too. (if that is sane, is a different question, specially in FPC's case which won't reuse global CFLAGS, but tradition...)
That's why you see all BSD binaries uploaded, and other majority platforms are missing.
Win32/64 in particular is useless, since there you need the binutils in the release package anyway.
Marco van de Voort wrote 18 lines
In our previous episode, Joao Morais said:
> How ftp://ftp.freepascal.org/pub/fpc/dist/2.6.2/bootstrap
> like lists are built? I missed at least i386-linux and i386-win32
> binaries.
They are simply the compiler binary extracted from the release in a bzipped
format.
It's mainly a facility for source based package systems like the *bsd ports,
where the enduser routinely bootstraps compiler + source too.
(if that is sane, is a different question, specially in FPC's case which won't
reuse global CFLAGS, but tradition...)
That's why you see all BSD binaries uploaded, and other majority platforms
are missing.
Win32/64 in particular is useless, since there you need the binutils in the
release package anyway.
Well, Ludo Brands and I *did* build a tool that gets the binutils[1] if they're not there and proceeds to build fpc+Lazarus afer svn checkout for Linux and Windows (and perhaps it still works on OSX, haven't tested for a long while).
I would be *very* happy with the win32 and 64 builds.
[1] and an svn executable on Windows etc...
Reinier Olislagers wrote 18 lines
On 4-3-2013 10:19, Marco van de Voort wrote:
> It's mainly a facility for source based package systems like the *bsd ports,
> where the enduser routinely bootstraps compiler + source too.
> (if that is sane, is a different question, specially in FPC's case which won't
> reuse global CFLAGS, but tradition...)
>
> That's why you see all BSD binaries uploaded, and other majority platforms
> are missing.
>
> Win32/64 in particular is useless, since there you need the binutils in the
> release package anyway.
Well, Ludo Brands and I *did* build a tool that gets the binutils[1] if
they're not there and proceeds to build fpc+Lazarus afer svn checkout
for Linux and Windows (and perhaps it still works on OSX, haven't tested
for a long while).
I would be *very* happy with the win32 and 64 builds.
... of the bootstrap compilers of course. Likewise for Linux x64 and x86.
In our previous episode, Joao Morais said: They are simply the compiler binary extracted…
Marco van de Voort wrote 7 lines
In our previous episode, Joao Morais said:
> How ftp://ftp.freepascal.org/pub/fpc/dist/2.6.2/bootstrap
> like lists are built? I missed at least i386-linux and i386-win32
> binaries.
They are simply the compiler binary extracted from the release in a bzipped
format.
Which is a big plus compared with ~50MB packages. Such packages help in creating a maintainable snapshot environment from scratch.
Win32/64 in particular is useless, since there you need the binutils in the release package anyway.
Because of that I also maintain a checkout of fpcbuild/install/binwXX of the current release under Windows.
Btw the win binaries are harder to take, since they are installers and afaics the compiler cannot be extracted without executing the installation process.
Joao Morais