Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2011-07

old fpmake files

12 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Mattias Gaertner

Hi,

When I do a 'make clean' in my fpc trunk directory I get:

make[2]: Entering directory `/home/mattias/...fpc/packages/fcl-web' ./fpmake distclean ...
Invalid command-line argument at position 1: distclean Usage: ...

The packages/fcl-web/fpmake is an old executable.

Is this normal?
What is the correct way to clean up the fpc trunk?

Mattias

Reply by email

Jonas Maebe
to Mattias Gaertner
Mattias Gaertner wrote 11 lines
When I do a 'make clean' in my fpc trunk directory I get: make[2]: Entering directory `/home/mattias/...fpc/packages/fcl-web' ./fpmake distclean ... Invalid command-line argument at position 1: distclean Usage: ... The packages/fcl-web/fpmake is an old executable. Is this normal? What is the correct way to clean up the fpc trunk?

To be safe, you should always make distclean before updating from svn (even without fpmake, since directories or units may get moved, which then won't be cleaned anymore after the update). Now, for a while make distclean didn't work properly either for fpmake-based directories, but that should have been fixed in the mean time.

I don't think you have another choice to fix your current checkout than by manually deleting all fpmake executables (find . -name fpmake -print0 | xargs -0 rm).

Jonas

Reply by email

Mattias Gaertner
to Jonas Maebe
Show quoted text 17 lines
On 17 Jul 2011, at 11:40, Mattias Gaertner wrote: > When I do a 'make clean' in my fpc trunk directory I get: > > make[2]: Entering directory `/home/mattias/...fpc/packages/fcl-web' > ./fpmake distclean ... > Invalid command-line argument at position 1: distclean > Usage: ... > > The packages/fcl-web/fpmake is an old executable. > > Is this normal? > What is the correct way to clean up the fpc trunk? To be safe, you should always make distclean before updating from svn (even without fpmake, since directories or units may get moved, which then won't be cleaned anymore after the update). Now, for a while make distclean didn't work properly either for fpmake-based directories, but that should have been fixed in the mean time.

Thanks.

I don't think you have another choice to fix your current checkout than by manually deleting all fpmake executables (find . -name fpmake -print0 | xargs -0 rm).

I did something similar.

Mattias

Reply by email

Marcos Douglas
to Jonas Maebe: To be safe, you should always make distclean before updating from svn (even without…
Jonas Maebe wrote 5 lines
To be safe, you should always make distclean before updating from svn (even without fpmake, since directories or units may get moved, which then won't be cleaned anymore after the update). Now, for a while make distclean didn't work properly either for fpmake-based directories, but that should have been fixed in the mean time. I don't think you have another choice to fix your current checkout than by manually deleting all fpmake executables (find  . -name fpmake -print0 | xargs -0 rm).

I never used distclean before updating from SVN and a never got problems. I use WinXP and TortoiseSVN.

Marcos Douglas

Reply by email

Jonas Maebe
to Marcos Douglas
Marcos Douglas wrote 5 lines
On Sun, Jul 17, 2011 at 6:48 AM, Jonas Maebe wrote: > > To be safe, you should always make distclean before updating from svn (even without fpmake, since directories or units may get moved, which then won't be cleaned anymore after the update). I never used distclean before updating from SVN and a never got problems.

Then you got lucky (just like people can get lucky for a long time by compiling svn trunk with previous svn trunk compilers instead of starting with the latest release). Your checkout will however probably contain a lot of outdated compiled units and directories that have been removed from svn (but which weren't deleted in your local copy because they still contained "units" directories).

I use WinXP and TortoiseSVN.

That doesn't matter.

Jonas

Reply by email

Marcos Douglas
to Jonas Maebe
Jonas Maebe wrote 11 lines
On 17 Jul 2011, at 16:43, Marcos Douglas wrote: > On Sun, Jul 17, 2011 at 6:48 AM, Jonas Maebe wrote: >> >> To be safe, you should always make distclean before updating from svn (even without fpmake, since directories or units may get moved, which then won't be cleaned anymore after the update). > > I never used distclean before updating from SVN and a never got problems. Then you got lucky (just like people can get lucky for a long time by compiling svn trunk with previous svn trunk compilers instead of starting with the latest release). Your checkout will however probably contain a lot of outdated compiled units and directories that have been removed from svn (but which weren't deleted in your local copy because they still contained "units" directories).

I use fixes_2_4, not trunk. But what you said doesn't matter what source we use, right?
I always used these scripts to compile:
http://wiki.lazarus.freepascal.org/Installing_Lazarus#Compiling.2Finstalling_FPC_and_Lazarus_from_Sources_of_SVN_.28Win32.29

The Tortoise deletes many files when I'm updating the sources. I thought everything was working as it should.

I can use this command? make distclean clean all

Marcos Douglas

Reply by email

Jonas Maebe
to Marcos Douglas
Marcos Douglas wrote 6 lines
I use fixes_2_4, not trunk. But what you said doesn't matter what source we use, right? I always used these scripts to compile: http://wiki.lazarus.freepascal.org/Installing_Lazarus#Compiling.2Finstalling_FPC_and_Lazarus_from_Sources_of_SVN_.28Win32.29 The Tortoise deletes many files when I'm updating the sources.

Maybe it's set up to delete all files that are not in the repository, although I believe that is not standard svn client functionality (for a good reason: a developer would not want svn to delete all files he has been working on just because he did an update). It would definitely be a different operation than plain "update".

I thought everything was working as it should. I can use this command? make distclean clean all

The "make distclean" should be performed before updating from svn. The "make all" is for afterwards. Additionally, a "make distclean" already includes "make clean".

Jonas

Reply by email

Marcos Douglas
to Jonas Maebe
Jonas Maebe wrote 19 lines
On 17 Jul 2011, at 17:46, Marcos Douglas wrote: > I use fixes_2_4, not trunk. But what you said doesn't matter what > source we use, right? > I always used these scripts to compile: > http://wiki.lazarus.freepascal.org/Installing_Lazarus#Compiling.2Finstalling_FPC_and_Lazarus_from_Sources_of_SVN_.28Win32.29 > > The Tortoise deletes many files when I'm updating the sources. Maybe it's set up to delete all files that are not in the repository, although I believe that is not standard svn client functionality (for a good reason: a developer would not want svn to delete all files he has been working on just because he did an update). It would definitely be a different operation than plain "update". > I > thought everything was working as it should. > > I can use this command? make distclean clean all The "make distclean" should be performed before updating from svn. The "make all" is for afterwards. Additionally, a "make distclean" already includes "make clean".

Ok.
Now I will use make distclean before update.
I change the wiki below. Can you take a look if all is OK, please? http://wiki.lazarus.freepascal.org/Installing_Lazarus#STEP_.232:_Create_a_BAT_file_to_compile_FPC

Thanks,
Marcos Douglas

Reply by email

waldo kitty
to Marcos Douglas: I never used distclean before updating from SVN and a never got problems. I use WinXP and…
Marcos Douglas wrote 8 lines
On Sun, Jul 17, 2011 at 6:48 AM, Jonas Maebe wrote: > > To be safe, you should always make distclean before updating from svn (even without fpmake, since directories or units may get moved, which then won't be cleaned anymore after the update). Now, for a while make distclean didn't work properly either for fpmake-based directories, but that should have been fixed in the mean time. > > I don't think you have another choice to fix your current checkout than by manually deleting all fpmake executables (find . -name fpmake -print0 | xargs -0 rm). I never used distclean before updating from SVN and a never got problems. I use WinXP and TortoiseSVN.

me either... should we be? how bad could this get??

Reply by email

Jonas Maebe
to waldo kitty
waldo kitty wrote 7 lines
On 7/17/2011 10:43, Marcos Douglas wrote: > On Sun, Jul 17, 2011 at 6:48 AM, Jonas Maebe wrote: >> > I never used distclean before updating from SVN and a never got problems. > I use WinXP and TortoiseSVN. me either... should we be? how bad could this get??

See the first message in this thread for an example.

Jonas

Reply by email

waldo kitty
to Jonas Maebe
Jonas Maebe wrote 12 lines
On 19 Jul 2011, at 00:16, waldo kitty wrote: > On 7/17/2011 10:43, Marcos Douglas wrote: >> On Sun, Jul 17, 2011 at 6:48 AM, Jonas Maebe wrote: >>> >> I never used distclean before updating from SVN and a never got problems. >> I use WinXP and TortoiseSVN. > > me either... should we be? how bad could this get?? See the first message in this thread for an example.

well, i did but my eyes must be frosted... i'll look again and try to follow up with the wiki thing 'cause that is the same process that i use as well...

Reply by email

Marcos Douglas
to Jonas Maebe: Maybe it's set up to delete all files that are not in the repository, although I believe…
Jonas Maebe wrote 18 lines
On 17 Jul 2011, at 17:46, Marcos Douglas wrote: > I use fixes_2_4, not trunk. But what you said doesn't matter what > source we use, right? > I always used these scripts to compile: > http://wiki.lazarus.freepascal.org/Installing_Lazarus#Compiling.2Finstalling_FPC_and_Lazarus_from_Sources_of_SVN_.28Win32.29 > > The Tortoise deletes many files when I'm updating the sources. Maybe it's set up to delete all files that are not in the repository, although I believe that is not standard svn client functionality (for a good reason: a developer would not want svn to delete all files he has been working on just because he did an update). It would definitely be a different operation than plain "update". > I > thought everything was working as it should. > > I can use this command? make distclean clean all The "make distclean" should be performed before updating from svn. The "make all" is for afterwards. Additionally, a "make distclean" already includes "make clean".

Can I use 'make distclean' after compiling the FPC to prepare it for a future update from SVN?

Like this:
set myversion=2.4.5
set mypath=c:\freepascal\fpc\%myversion%
set mybinutils=c:\freepascal\binutils
set PATH=%mybinutils%\i386-win32;%mypath%\bin\i386-win32;%PATH% cd %mypath%
make all install INSTALL_PREFIX=%mypath% PP=%mybinutils%\ppc386.exe make distclean

BTW, what about Lazarus? I ever update it, from SVN, and compile it using the IDE menu.

Marcos Douglas

Reply by email