Re: [blfs-dev] Samba 4.7.4 and glibc 2.27 fails to compile

[DJ Lucas]

On February 28, 2018 12:46:11 PM CST, Tim Tassonis  wrote:
>
>
>On February 28, 2018 19:42:25 Pierre Labastie 
>wrote:
>
>>
>> On 28/02/2018 19:11, Tim Tassonis wrote:
>> >
>>> Hi all
>> >
>> >
>> >
>> >
>>> samba 4.7.4 fails to compile at my place due to the removal of the
>rpc stuff
>>> in glibc 2.27:
>> >
>> >
>>> [1292/3607] Compiling
>default/source3/librpc/gen_ndr/ndr_open_files.c
>>> In file included from ../source3/include/includes.h:113:0,
>> > from
>default/source3/librpc/gen_ndr/ndr_open_files.c:3:
>>> /usr/include/rpcsvc/yp_prot.h:10:10: fatal error: rpc/rpc.h: No such
>file or
>>> directory
>> > #include 
>> >  ^~~
>>> compilation terminated.
>>> Waf: Leaving directory `/lgl-bld/samba-4.7.4/bin'
>>> Build failed:  -> task failed (err #1):
>> >{task: cc ndr_open_files.c -> ndr_open_files_3.o}
>>> make: *** [Makefile:8: all] Error 1
>> >
>> >
>> >
>> >
>>> A quick search on digital information highway confirms that samba
>4.7.4 does
>>> not properly detect the new tircp/rpcsvc-proto libnsl stuff and has
>fixed this
>>> in 4.7.5.
>> >
>> >
>> >
>> >
>>> I can confirm that samba 4.7.5 builds with latest blfs svn (r19898).
>>
>>
>>
>> Samba is scheduled to be updated to 4.7.5 before 8.2 release. OTOH, I
>had no
>> error building samba, because libnsl was not installed (while
>libtirpc was):
>> the error you see seems to imply that libnsl was installed:
>> ---
>> /usr/include/rpcsvc/yp_prot.h:10:10: fatal error: rpc/rpc.h: No such
>file or
>> directory
>> ---
>> At least, this shows that libnsl should be listed somewhere among
>samba deps...
>
>Yes, I had to install libnsl in order to build exim, so that explains
>my 
>breakage.
>
>Bye
>Tim
>>
>>
>>
>> Pierre
>> --
>> http://lists.linuxfromscratch.org/listinfo/blfs-dev
>> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
>> Unsubscribe: See the above information page
>
>
>
>-- 
>http://lists.linuxfromscratch.org/listinfo/blfs-dev
>FAQ: http://www.linuxfromscratch.org/blfs/faq.html
>Unsubscribe: See the above information page

I ran into it too, without libnsl. CFLAGS="-I/usr/include/tirpc -ltirpc" 
./configure is good enough to get around it.

--DJ

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Archive mod_dnssd? And others

[Pierre Labastie]

On 28/02/2018 22:07, Bruce Dubbs wrote:
> Douglas R. Reno wrote:
> 
>>     Here are some more candidates for archiving:
> 
>>     3. general/genlib/gcab.xml
>>
>>     The only reference is to the archived appstream-glib-new.xml.
> 
>> gcab can be used on its own. Its the only utility that we have that allows
>> the extraction of the extremely common Windows .CAB files. i would advise
>> against archiving that one.
> 
> A couple of questions:  Why is this in a library chapter and why is it marked
> systemd only?
> 

Not an answer to the above, but just FYI, the current version is 1.1, see
https://github.com/GNOME/gcab

Pierre
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Building apache-ant-1.10.2

[John Burrell]

On 28 February 2018 at 14:55, Bruce Dubbs  wrote:

> DJ Lucas wrote:
>
>> On February 28, 2018 12:25:54 PM CST, John Burrell 
>> wrote:
>>
>>> When executing this line:
>>>
>>> bootstrap/bin/ant -f fetch.xml -Ddest=system || true
>>>
>>> to download the runtime dependencies, the build fails with this
>>> message:
>>>
>>>
>>> BUILD FAILED
>>> /usr/src/java/apache-ant/apache-ant-1.10.2/fetch.xml:332: The following
>>> error occurred while executing this line:
>>> /usr/src/java/apache-ant/apache-ant-1.10.2/fetch.xml:122: Unable to
>>> resolve
>>> artifact: Missing:
>>> --
>>> 1) javax.media:jai-core:jar:1.1.3
>>>
>>>   Try downloading the file manually from the project website.
>>>
>>>   Then, install it using the command:
>>>mvn install:install-file -DgroupId=javax.media -DartifactId=jai-core
>>> -Dversion=1.1.3 -Dpackaging=jar -Dfile=/path/to/file
>>>
>>> Alternatively, if you host your own repository you can deploy the file
>>> there:
>>>  mvn deploy:deploy-file -DgroupId=javax.media -DartifactId=jai-core
>>> -Dversion=1.1.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
>>> -DrepositoryId=[id]
>>>
>>>   Path to dependency:
>>>   1) org.apache.maven:super-pom:pom:2.0
>>>   2) javax.media:jai-core:jar:1.1.3
>>>
>>> --
>>> 1 required artifact is missing.
>>>
>>> for artifact:
>>>   org.apache.maven:super-pom:pom:2.0
>>>
>>> from the specified remote repositories:
>>>   central (http://repo1.maven.org/maven2)
>>>
>>> Presumably this is why you had to download jai-core-1.1.3.jar in the
>>> first
>>> place. And I assume the same reason for jai-codec-1.1.3.jar.
>>>
>>> This failure is a pain because it stops my script. I think it would be
>>> worth a note in the book mentioning this build failure and assuring LFS
>>> devotees that all runtime dependencies have in fact been downloaded.
>>>
>>> jb.
>>>
>>
>> Are you using "bash -e" in your script? I'll update the command
>> explanation, but "|| true" should be a good indicator. For your script,
>> wrap in [ ].
>>
>
> In many of my scripts I run checks in a subshell.  For example:
>
> (make check || true ) &&
> ...
>
> That allows the script to continue even if there are problems with the
> checks.  Of course all output is logged and review of the log is important
> to see if there are new issues with a new build.
>
> Thanks, that's a useful trick to know. I use set -e the first time through
the script to catch any errors but with a case such as apache-ant where the
Build error is to be ignored, then launching a sub-shell is a good next
step because one knows immediately to check the logs for any further errors.

jb.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Archive mod_dnssd? And others

[Bruce Dubbs]

Douglas R. Reno wrote:


Here are some more candidates for archiving:



3. general/genlib/gcab.xml

The only reference is to the archived appstream-glib-new.xml.


gcab can be used on its own. Its the only utility that we have that allows 
the extraction of the extremely common Windows .CAB files. i would advise 
against archiving that one.


A couple of questions:  Why is this in a library chapter and why is it 
marked systemd only?


  -- Bruce




--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Building apache-ant-1.10.2

[Bruce Dubbs]

DJ Lucas wrote:

On February 28, 2018 12:25:54 PM CST, John Burrell  
wrote:

When executing this line:

bootstrap/bin/ant -f fetch.xml -Ddest=system || true

to download the runtime dependencies, the build fails with this
message:


BUILD FAILED
/usr/src/java/apache-ant/apache-ant-1.10.2/fetch.xml:332: The following
error occurred while executing this line:
/usr/src/java/apache-ant/apache-ant-1.10.2/fetch.xml:122: Unable to
resolve
artifact: Missing:
--
1) javax.media:jai-core:jar:1.1.3

  Try downloading the file manually from the project website.

  Then, install it using the command:
   mvn install:install-file -DgroupId=javax.media -DartifactId=jai-core
-Dversion=1.1.3 -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file
there:
 mvn deploy:deploy-file -DgroupId=javax.media -DartifactId=jai-core
-Dversion=1.1.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]

  Path to dependency:
  1) org.apache.maven:super-pom:pom:2.0
  2) javax.media:jai-core:jar:1.1.3

--
1 required artifact is missing.

for artifact:
  org.apache.maven:super-pom:pom:2.0

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

Presumably this is why you had to download jai-core-1.1.3.jar in the
first
place. And I assume the same reason for jai-codec-1.1.3.jar.

This failure is a pain because it stops my script. I think it would be
worth a note in the book mentioning this build failure and assuring LFS
devotees that all runtime dependencies have in fact been downloaded.

jb.


Are you using "bash -e" in your script? I'll update the command explanation, but "|| 
true" should be a good indicator. For your script, wrap in [ ].


In many of my scripts I run checks in a subshell.  For example:

(make check || true ) &&
...

That allows the script to continue even if there are problems with the 
checks.  Of course all output is logged and review of the log is important 
to see if there are new issues with a new build.



  -- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Building apache-ant-1.10.2

[DJ Lucas]

On February 28, 2018 12:25:54 PM CST, John Burrell  
wrote:
>When executing this line:
>
>bootstrap/bin/ant -f fetch.xml -Ddest=system || true
>
>to download the runtime dependencies, the build fails with this
>message:
>
>
>BUILD FAILED
>/usr/src/java/apache-ant/apache-ant-1.10.2/fetch.xml:332: The following
>error occurred while executing this line:
>/usr/src/java/apache-ant/apache-ant-1.10.2/fetch.xml:122: Unable to
>resolve
>artifact: Missing:
>--
>1) javax.media:jai-core:jar:1.1.3
>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>   mvn install:install-file -DgroupId=javax.media -DartifactId=jai-core
>-Dversion=1.1.3 -Dpackaging=jar -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
>there:
> mvn deploy:deploy-file -DgroupId=javax.media -DartifactId=jai-core
>-Dversion=1.1.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
>-DrepositoryId=[id]
>
>  Path to dependency:
>  1) org.apache.maven:super-pom:pom:2.0
>  2) javax.media:jai-core:jar:1.1.3
>
>--
>1 required artifact is missing.
>
>for artifact:
>  org.apache.maven:super-pom:pom:2.0
>
>from the specified remote repositories:
>  central (http://repo1.maven.org/maven2)
>
>Presumably this is why you had to download jai-core-1.1.3.jar in the
>first
>place. And I assume the same reason for jai-codec-1.1.3.jar.
>
>This failure is a pain because it stops my script. I think it would be
>worth a note in the book mentioning this build failure and assuring LFS
>devotees that all runtime dependencies have in fact been downloaded.
>
>jb.

Are you using "bash -e" in your script? I'll update the command explanation, 
but "|| true" should be a good indicator. For your script, wrap in [ ].

--DJ

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Samba 4.7.4 and glibc 2.27 fails to compile

[Tim Tassonis]

On February 28, 2018 19:42:25 Pierre Labastie  wrote:



On 28/02/2018 19:11, Tim Tassonis wrote:
>

Hi all

>
>
>
>

samba 4.7.4 fails to compile at my place due to the removal of the rpc stuff
in glibc 2.27:

>
>

[1292/3607] Compiling default/source3/librpc/gen_ndr/ndr_open_files.c
In file included from ../source3/include/includes.h:113:0,

> from default/source3/librpc/gen_ndr/ndr_open_files.c:3:

/usr/include/rpcsvc/yp_prot.h:10:10: fatal error: rpc/rpc.h: No such file or
directory

> #include 
>  ^~~

compilation terminated.
Waf: Leaving directory `/lgl-bld/samba-4.7.4/bin'
Build failed:  -> task failed (err #1):

>{task: cc ndr_open_files.c -> ndr_open_files_3.o}

make: *** [Makefile:8: all] Error 1

>
>
>
>

A quick search on digital information highway confirms that samba 4.7.4 does
not properly detect the new tircp/rpcsvc-proto libnsl stuff and has fixed this
in 4.7.5.

>
>
>
>

I can confirm that samba 4.7.5 builds with latest blfs svn (r19898).




Samba is scheduled to be updated to 4.7.5 before 8.2 release. OTOH, I had no
error building samba, because libnsl was not installed (while libtirpc was):
the error you see seems to imply that libnsl was installed:
---
/usr/include/rpcsvc/yp_prot.h:10:10: fatal error: rpc/rpc.h: No such file or
directory
---
At least, this shows that libnsl should be listed somewhere among samba deps...


Yes, I had to install libnsl in order to build exim, so that explains my 
breakage.


Bye
Tim




Pierre
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page




--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Samba 4.7.4 and glibc 2.27 fails to compile

[Pierre Labastie]

On 28/02/2018 19:11, Tim Tassonis wrote:
> Hi all
> 
> 
> samba 4.7.4 fails to compile at my place due to the removal of the rpc stuff
> in glibc 2.27:
> 
> [1292/3607] Compiling default/source3/librpc/gen_ndr/ndr_open_files.c
> In file included from ../source3/include/includes.h:113:0,
>  from default/source3/librpc/gen_ndr/ndr_open_files.c:3:
> /usr/include/rpcsvc/yp_prot.h:10:10: fatal error: rpc/rpc.h: No such file or
> directory
>  #include 
>   ^~~
> compilation terminated.
> Waf: Leaving directory `/lgl-bld/samba-4.7.4/bin'
> Build failed:  -> task failed (err #1):
> {task: cc ndr_open_files.c -> ndr_open_files_3.o}
> make: *** [Makefile:8: all] Error 1
> 
> 
> A quick search on digital information highway confirms that samba 4.7.4 does
> not properly detect the new tircp/rpcsvc-proto libnsl stuff and has fixed this
> in 4.7.5.
> 
> 
> I can confirm that samba 4.7.5 builds with latest blfs svn (r19898).
> 

Samba is scheduled to be updated to 4.7.5 before 8.2 release. OTOH, I had no
error building samba, because libnsl was not installed (while libtirpc was):
the error you see seems to imply that libnsl was installed:
---
/usr/include/rpcsvc/yp_prot.h:10:10: fatal error: rpc/rpc.h: No such file or
directory
---
At least, this shows that libnsl should be listed somewhere among samba deps...

Pierre
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Minor suggestion for librsvg-2.42.2

[Ryan Marsaw]

On Wed, 28 Feb 2018, Tim Tassonis wrote:


Hi all

I just installed adwaita-icon-themes, resulting in an error due to rsvg 
being installed, but gdk-pixbuf-query-loaders not being run. As I am 
doing a DESTDIR install, it might be that this was run at
make install of rsvg, but maybe there could be a remark on the rsvg page 
to run


gdk-pixbuf-query-loaders --update-cache

as root after make install. This fixed by adwaita-icon-theme error.


Bye
Tim
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page



Running "gdk-pixbuf-query-loaders --update-cache" is already mentioned
on the gdk-pixbuf page of BLFS.  It's pretty much required if using the
DESTDIR method of installing.  It's also needed if building gdk-pixbuf
using the Meson build system, as I discovered when I switched from using
the autotools method.

Regards,

Ryan

--
Ryan Marsaw
rmar...@personainternet.com
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-dev] Building apache-ant-1.10.2

[John Burrell]

When executing this line:

bootstrap/bin/ant -f fetch.xml -Ddest=system || true

to download the runtime dependencies, the build fails with this message:


BUILD FAILED
/usr/src/java/apache-ant/apache-ant-1.10.2/fetch.xml:332: The following
error occurred while executing this line:
/usr/src/java/apache-ant/apache-ant-1.10.2/fetch.xml:122: Unable to resolve
artifact: Missing:
--
1) javax.media:jai-core:jar:1.1.3

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=javax.media -DartifactId=jai-core
-Dversion=1.1.3 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
  mvn deploy:deploy-file -DgroupId=javax.media -DartifactId=jai-core
-Dversion=1.1.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]

  Path to dependency:
  1) org.apache.maven:super-pom:pom:2.0
  2) javax.media:jai-core:jar:1.1.3

--
1 required artifact is missing.

for artifact:
  org.apache.maven:super-pom:pom:2.0

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

Presumably this is why you had to download jai-core-1.1.3.jar in the first
place. And I assume the same reason for jai-codec-1.1.3.jar.

This failure is a pain because it stops my script. I think it would be
worth a note in the book mentioning this build failure and assuring LFS
devotees that all runtime dependencies have in fact been downloaded.

jb.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-dev] Samba 4.7.4 and glibc 2.27 fails to compile

[Tim Tassonis]

Hi all


samba 4.7.4 fails to compile at my place due to the removal of the rpc 
stuff in glibc 2.27:


[1292/3607] Compiling default/source3/librpc/gen_ndr/ndr_open_files.c
In file included from ../source3/include/includes.h:113:0,
 from default/source3/librpc/gen_ndr/ndr_open_files.c:3:
/usr/include/rpcsvc/yp_prot.h:10:10: fatal error: rpc/rpc.h: No such 
file or directory

 #include 
  ^~~
compilation terminated.
Waf: Leaving directory `/lgl-bld/samba-4.7.4/bin'
Build failed:  -> task failed (err #1):
{task: cc ndr_open_files.c -> ndr_open_files_3.o}
make: *** [Makefile:8: all] Error 1


A quick search on digital information highway confirms that samba 4.7.4 
does not properly detect the new tircp/rpcsvc-proto libnsl stuff and has 
fixed this in 4.7.5.



I can confirm that samba 4.7.5 builds with latest blfs svn (r19898).

Bye
Tim
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-dev] Minor suggestion for librsvg-2.42.2

[Tim Tassonis]

Hi all

I just installed adwaita-icon-themes, resulting in an error due to rsvg 
being installed, but gdk-pixbuf-query-loaders not being run. As I am 
doing a DESTDIR install, it might be that this was run at
make install of rsvg, but maybe there could be a remark on the rsvg page 
to run


gdk-pixbuf-query-loaders --update-cache

as root after make install. This fixed by adwaita-icon-theme error.


Bye
Tim
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Archive mod_dnssd? And others

[Richard Melville]

On 28 February 2018 at 12:25, Bruce Dubbs  wrote:

> Bruce Dubbs wrote:
>
>> The only reference to it that I can find is
>>
>> 1.  archive/gnome/gnome-user-share.xml:  
>
> Here are some more candidates for archiving:
>
> 2. general/prog/jinja2.xml
>
> The only place this is locates is in systemd python modules.  I see
> nothing that references it.
>
> I don't use jinja2 as I'm not a web developer, but I know many who do.
Here's a link:-

http://jinja.pocoo.org/docs/2.10/

Richard
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Archive mod_dnssd? And others

[Douglas R. Reno]

On Feb 28, 2018 7:08 AM, "Pierre Labastie"  wrote:

On 28/02/2018 13:25, Bruce Dubbs wrote:

> Bruce Dubbs wrote:
>
>> The only reference to it that I can find is
>>
>> 1.  archive/gnome/gnome-user-share.xml:  
>
> Here are some more candidates for archiving:
>
> 2. general/prog/jinja2.xml
>
> The only place this is locates is in systemd python modules.  I see
> nothing that references it.
>
> 3. general/genlib/gcab.xml
>
> The only reference is to the archived appstream-glib-new.xml.
>
>-- Bruce
>

Should be asked on support? As far as I am concerned, I've nothing against
archiving those (and quite a few others, but it's another story...)

Pierre

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


gcab can be used on its own. Its the only utility that we have that allows
the extraction of the extremely common Windows .CAB files. i would advise
against archiving that one.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Archive mod_dnssd? And others

[Pierre Labastie]

On 28/02/2018 13:25, Bruce Dubbs wrote:

Bruce Dubbs wrote:

The only reference to it that I can find is


1.  archive/gnome/gnome-user-share.xml:  

Here are some more candidates for archiving:

2. general/prog/jinja2.xml

The only place this is locates is in systemd python modules.  I see 
nothing that references it.


3. general/genlib/gcab.xml

The only reference is to the archived appstream-glib-new.xml.

   -- Bruce


Should be asked on support? As far as I am concerned, I've nothing 
against archiving those (and quite a few others, but it's another story...)


Pierre
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Archive mod_dnssd? And others

[Bruce Dubbs]

Bruce Dubbs wrote:

The only reference to it that I can find is


1.  archive/gnome/gnome-user-share.xml:  

Here are some more candidates for archiving:

2. general/prog/jinja2.xml

The only place this is locates is in systemd python modules.  I see 
nothing that references it.


3. general/genlib/gcab.xml

The only reference is to the archived appstream-glib-new.xml.

  -- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page